[00:22] ErKa (keryell@wireless-tcc-users-915.sc11.org) joined #fai. [01:24] ErKa (keryell@wireless-tcc-users-915.sc11.org) left irc: Read error: Operation timed out [01:27] ErKa (keryell@wireless-tcc-users-915.sc11.org) joined #fai. [03:39] ErKa (keryell@wireless-tcc-users-915.sc11.org) left irc: Ping timeout: 480 seconds [03:42] jonas (~jonas@115.78.133.75) joined #fai. [03:43] Nick change: jonas -> Guest17233 [03:43] Nick change: Guest17233 -> jonas [04:53] sneumann__ (~sneumann@pD9554DE6.dip.t-dialin.net) joined #fai. [05:07] sneumann__ (~sneumann@pD9554DE6.dip.t-dialin.net) left irc: Ping timeout: 480 seconds [06:25] sneumann__ (~sneumann@router-sub.ipb-halle.de) joined #fai. [06:46] ErKa (~keryell@71-37-54-135.tukw.qwest.net) joined #fai. [07:16] ErKa (~keryell@71-37-54-135.tukw.qwest.net) left irc: Ping timeout: 480 seconds [07:33] and1bm (~andi@HSI-KBW-095-208-066-227.hsi5.kabel-badenwuerttemberg.de) joined #fai. [08:29] shod (~shod@ip-109-47-246-97.web.vodafone.de) joined #fai. [08:31] Mrfai (~lange@malzmuehle.informatik.uni-koeln.de) joined #fai. [08:46] verwilst (~verwilst@d5152FEFB.static.telenet.be) joined #fai. [08:48] Mrfai (~lange@malzmuehle.informatik.uni-koeln.de) left irc: Read error: Operation timed out [08:57] Mrfai (~lange@malzmuehle.informatik.uni-koeln.de) joined #fai. [10:13] shod (~shod@ip-109-47-246-97.web.vodafone.de) left irc: Quit: Leaving. [10:14] shod (~shod@ip-109-47-246-97.web.vodafone.de) joined #fai. [10:22] shod (~shod@ip-109-47-246-97.web.vodafone.de) left irc: Ping timeout: 480 seconds [12:48] and1bm (~andi@HSI-KBW-095-208-066-227.hsi5.kabel-badenwuerttemberg.de) left irc: Quit: Konversation terminated! [13:03] carsten (~carsten@ahgate1.aei.uni-hannover.de) joined #fai. [13:06] Hi all,as just written to the fai main list, has there been some work on getting multiple NICs after PXE booting under control with IPAPPPEND 3? [13:13] at least live-boot-initramfs-tools 2.0.15-1 does not seem to address this and also the latest one from Wheezy (3.0...) not [13:14] carsten: I just send an email about this. And mika is the expert for initramfs-tools and live-boot. [13:16] i Thomas, just read it [13:16] will look into that, would be nice to get this fixed [13:16] it's becoming really annoying to us as we get more andmore different computers [13:18] We did not have that many problems with multiple NICs here (in IRC) in the past months. So I guess, it should be solvable. [13:18] But I'm sure mika will help you if there are still problems. [13:19] s/mika/mikap/ [13:19] well, i'm aware of this issue and know that people have different solutions solving this issue [13:19] ours[tm] is that we're supporting ip=... syntax as used by the kernel/nfsroot and we don't have "rotating" NICs [13:20] so the ones with working solutions should provide us (initramfs-tools/live-boot) their patches [13:21] or instead provide access to such boxes, sadly i don't have machines with such problems available those days [13:22] mikap: so far that worked well for us [13:22] so far as until what? ;) [13:23] IMO the important device name during installation is only eth0, which should be the NIC, which received the kernel and initrd. [13:23] mikap: however, now we have machines which uses a different eth0 after each reboot [13:23] carsten: what vendor is that? [13:23] supermicro [13:23] tk? ;o) [13:24] X8DT6 board with 2 82598EB 10Gb/s NICs and 2 82574L 1 b/s NICs [13:24] carsten: there's a udev rule that should care of stable NIC names IIRC. /etc/udev/rules.d/70-persistent-net.rules [13:24] Mrfai: actually that's not necessarily true, especially if booting environment is different from the one providing the deployment data (e.g. special vlan) - but that's at least what should work always ootb, yeah [13:24] yes, but udev does not run in the initd before mounting the nfsroot, right? [13:25] the only problem we really face is that PXE works, but the initrd tries the wrong NIC for mounting the nfsroot (DHCP fails/SHCP stalls) [13:26] ok, brb, meeting is over and I need to move back to my office [13:26] .quit [13:26] carsten (~carsten@ahgate1.aei.uni-hannover.de) left irc: Quit: Konversation terminated! [13:29] carsten (~carsten@ahgate1.aei.uni-hannover.de) joined #fai. [13:30] back again [13:34] Mrfai: thus I don't think udev might help much here, right? [13:37] I've looked at the script/function code. If BOOTIF is set, the initrd can detect the device name from which the kernel and initrd was loaded. So, it does not need to be eth0. It uses the MAC address to get the device name of the NIC for later nfs mount. [13:38] (Note that the grml initramfs has different code.) [13:39] Then, the installation should generate the 70persistent-net.rules file, which should care about stable device names during the next reboot. That's how I understand these things. [13:41] zeha: Mmm, initramfs-tools_0.93.4-grml02 has no BOOTIF code in it :-( [13:42] Mrfai: it's not about initramfs-tools but live-initramfs/live-boot [13:43] mikap: I don't think so. If initramfs-tools is setting DEVICE to the correct interface which received the kernel, then live-boot can just use this device name for booting the nfsroot. [13:44] Mrfai: the problem is that live-initramfs upstream re-invented networking code instead of reusing what's there [13:44] This is more flexible, than that the admin must specify a device name (which might change) [13:45] well, there's a lot of stuff going on between live-i-t and i-t, you'll have to debug it to follow the code flow [13:45] yes, that's the IPAPPEND way which is fine, though you *might* want to apply specific configuration statically to a device, that's when ip=... is nice then [13:45] Exactly, if IPAPPEND 3 is given via PXE and the kernel and initrd is loaded, I *think* the sane way is to re-use this for bringing that iface up and use for nfs mouting [13:46] the code does ip= and BOOTIF=; maybe not both at the same time [13:48] carsten: did you try those packages in your nfsroot? initramfs-tools 0.98.8, live-boot-initramfs-tools, live-boot 2.0.15-1 [13:49] I'm using thoses for squeeze. They include the BOOTIF code [13:49] the latter tow only [13:49] initramfs-tools is NOT installed [13:49] wait, sorry [13:49] ii initramfs-tools 0.98.8 [13:49] yeah all three of these [13:50] jsut started a test install and initrd is hanging again with this line in the pxeconfig line [13:50] append initrd=initrd.img-2.6.32-5-amd64 root=/dev/nfs nfsroot=/srv/fai/nfsroot boot=live console=tty0 nomodeset FAI_FLAGS=verbose,sshd,createvt,initial,reboot FAI_ACTION=install [13:50] IPAPPEND 3 [13:51] make sure your klibc-utils package is version 1.5.20-1+squeeze1 [13:52] older ipconfig versions will definitively cause issues with >1 nic [13:52] ok, that is only at 1.5.20-1 [13:53] suggestions: re-create NFSroot or safe-upgrade in chroot? [13:54] recraete nfsroot, since then a new initrd is also created and copiesd to the tftp directory. You may want to use m-f-n -k or -K [13:55] ok, that might take a while (like Thomas is warning ;)) [14:12] carsten: Wenn das alles nicht klappt, koennte dracut oder ein squashfs (gebaut mit fai-nfsroot2image) helfen. [14:17] ranulf (~ranulf@mail3.twallrafen.de) joined #fai. [14:19] Mrfai: ok, wait and see, nfsroot ready, reboot of test node [14:22] hmm, same, stops suring select-eth [14:22] during [14:22] Let me just look at the initrd if I can spot bootif in there [14:24] /quit/quit [14:24] Mrfai (~lange@malzmuehle.informatik.uni-koeln.de) left irc: Quit: leaving [14:25] darn, I scared him away ;) [14:26] hehe [15:01] ok, lenghty email to the main fai list [15:02] it seems the function configure_networking from scripts/functions is never called (at least not in my case) and thus BOOTIF is never evaluated [15:02] :( [15:17] probably. [15:18] if you have boot=live then you're after scripts/live networking code [15:34] yeah, thus Thomas was wrong :( (and without boot=live it falls into the initramfs shell) [15:35] *sigh* [16:01] mikap: I'm just wondering is there a deeper sense in having "export BOOTIF=" in "init" within the initrd? this effectively disables this feature, right? [16:03] mikap: at least it heavily confuses me - I added 'env' to 'init' and before the export the variable is set corerctly and afterwards it's empty [16:07] verwilst (~verwilst@d5152FEFB.static.telenet.be) left irc: Quit: Ex-Chat [16:09] carsten (~carsten@ahgate1.aei.uni-hannover.de) left irc: Quit: ... [16:17] jmux (~jan-marek@lhm246.muenchen.de) joined #fai. [16:41] sneumann__ (~sneumann@router-sub.ipb-halle.de) left irc: Read error: Operation timed out [17:16] and1bm (~andi@HSI-KBW-095-208-066-227.hsi5.kabel-badenwuerttemberg.de) joined #fai. [17:30] ErKa (keryell@wireless-tcc-users-915.sc11.org) joined #fai. [17:39] jmux (~jan-marek@lhm246.muenchen.de) left irc: [18:19] ErKa (keryell@wireless-tcc-users-915.sc11.org) left irc: Ping timeout: 480 seconds [19:03] jonas (~jonas@115.78.133.75) left irc: Read error: Connection reset by peer [19:03] and1bm (~andi@HSI-KBW-095-208-066-227.hsi5.kabel-badenwuerttemberg.de) left irc: Quit: Konversation terminated! [19:21] sneumann__ (~sneumann@pD9554DE6.dip.t-dialin.net) joined #fai. [20:33] ErKa (keryell@wireless-tcc-users-915.sc11.org) joined #fai. [21:45] ranulf (~ranulf@mail3.twallrafen.de) left irc: Quit: leaving [22:08] sneumann__ (~sneumann@pD9554DE6.dip.t-dialin.net) left irc: Ping timeout: 480 seconds [22:31] ErKa (keryell@wireless-tcc-users-915.sc11.org) left irc: Ping timeout: 480 seconds [00:00] --- Thu Nov 17 2011