[opensuse] Slow network initialization on boot up
I recently upgraded one of my servers to SuSE11.2 x86-64 arch and I am noticing that the network initialization seems to be happening sometime after the boot up process is complete. This is breaking the startup of a number of other services such a my Bacula backup and James email servers, though others such as Tomcat6 seem to survive it ok. I might also guess that this is breaking the automount of some of the directories from other computers on my internal network. One of the symptoms (smoking gun?) is that right after the boot up is complete and the KDE gui has come up, I cannot ping any of the other computers on my internal network for awhile. A few minutes after startup, then the pings will begin to work but until then I get an unknown host error which surprises me because all my hosts are defined in the /etc/hosts file.. Same goes for the automount, it fails during boot up, and if I do a mount -a too soon, after boot up it still fails, but if I wait a few minutes, do a mount -a, then it works.. Doing an rcnetwork status right after the KDE gui comes up clearly shows that eth1 has failed to initialize - bigbang:/etc # rcnetwork status Checking optional network interfaces: eth0 device: Intel Corporation 82573V Gigabit Ethernet Controller (Copper) (rev 03) eth0 IP address: 206.58.200.12/24 eth0 running eth1 device: Accton Technology Corporation SMC2-1211TX (rev 10) eth1 is down eth1 dead Checking mandatory network interfaces: lo lo IP address: 127.0.0.1/8 secondary lo IP address: 127.0.0.2/8 lo running Checking service network . . . . . . . . . . . running Looking at the messages log file, I think it is trying to tell me something, but I dunno what. At least here is a portion that I think is interesting - Feb 23 10:50:11 bigbang ifup: lo Feb 23 10:50:11 bigbang ifup: lo Feb 23 10:50:11 bigbang ifup: IP address: 127.0.0.1/8 Feb 23 10:50:11 bigbang ifup: Feb 23 10:50:11 bigbang ifup: Feb 23 10:50:11 bigbang ifup: IP address: 127.0.0.2/8 Feb 23 10:50:11 bigbang ifup: Feb 23 10:50:11 bigbang ifup: eth0 device: Intel Corporation 82573V Gigabit Ethernet Controller (Copper) (rev 03) Feb 23 10:50:15 bigbang kernel: [ 28.732592] e1000e 0000:04:00.0: irq 28 for MSI/MSI-X Feb 23 10:50:15 bigbang kernel: [ 28.783221] e1000e 0000:04:00.0: irq 28 for MSI/MSI-X Feb 23 10:50:15 bigbang kernel: [ 28.784009] ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 23 10:50:15 bigbang ifup: eth0 Feb 23 10:50:15 bigbang ifup: IP address: 206.58.200.12/24 Feb 23 10:50:15 bigbang ifup: Feb 23 10:50:15 bigbang nmbd[1999]: [2010/02/23 10:50:15, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:15 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:15 bigbang nmbd[1999]: [2010/02/23 10:50:15, 0] nmbd/nmbd_subnetdb.c:206(create_subnets) Feb 23 10:50:15 bigbang nmbd[1999]: create_subnets: No local IPv4 non-loopback interfaces ! Feb 23 10:50:15 bigbang nmbd[1999]: [2010/02/23 10:50:15, 0] nmbd/nmbd_subnetdb.c:207(create_subnets) Feb 23 10:50:15 bigbang nmbd[1999]: create_subnets: Waiting for an interface to appear ... Feb 23 10:50:16 bigbang kernel: [ 30.447544] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None Feb 23 10:50:16 bigbang kernel: [ 30.447555] 0000:04:00.0: eth0: 10/100 speed: disabling TSO Feb 23 10:50:16 bigbang kernel: [ 30.447961] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 23 10:50:17 bigbang checkproc: checkproc: can not get session id for process 2120! Feb 23 10:50:20 bigbang nmbd[1999]: [2010/02/23 10:50:20, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:20 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:20 bigbang kernel: [ 34.329109] CPU0 attaching NULL sched-domain. Feb 23 10:50:20 bigbang kernel: [ 34.329118] CPU1 attaching NULL sched-domain. Feb 23 10:50:20 bigbang kernel: [ 34.332231] CPU0 attaching sched-domain: Feb 23 10:50:20 bigbang kernel: [ 34.332236] domain 0: span 0-1 level CPU Feb 23 10:50:20 bigbang kernel: [ 34.332240] groups: 0 1 Feb 23 10:50:20 bigbang kernel: [ 34.332249] CPU1 attaching sched-domain: Feb 23 10:50:20 bigbang kernel: [ 34.332252] domain 0: span 0-1 level CPU Feb 23 10:50:20 bigbang kernel: [ 34.332256] groups: 1 0 Feb 23 10:50:25 bigbang nmbd[1999]: [2010/02/23 10:50:25, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:25 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:27 bigbang kernel: [ 41.033007] eth0: no IPv6 routers present Feb 23 10:50:30 bigbang nmbd[1999]: [2010/02/23 10:50:30, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:30 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:35 bigbang nmbd[1999]: [2010/02/23 10:50:35, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:35 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:39 bigbang gnome-keyring-daemon[2360]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Feb 23 10:50:40 bigbang nmbd[1999]: [2010/02/23 10:50:40, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:40 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:41 bigbang gnome-keyring-ask: could not grab keyboard: 3 Feb 23 10:50:45 bigbang python: hp-systray[2434]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting. Feb 23 10:50:45 bigbang nmbd[1999]: [2010/02/23 10:50:45, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:45 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:50 bigbang nmbd[1999]: [2010/02/23 10:50:50, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:50 bigbang nmbd[1999]: WARNING: no network interfaces found Feb 23 10:50:55 bigbang nmbd[1999]: [2010/02/23 10:50:55, 0] lib/interface.c:550(load_interfaces) Feb 23 10:50:55 bigbang nmbd[1999]: WARNING: no network interfaces found .... A whole slew of these last two messages occur here... interspersed with the following a few times - Feb 23 10:51:25 bigbang kernel: [ 98.649885] type=1503 audit(1266951085.164:13): operation="open" pid=2589 parent=2310 profile="/bin/ping" requested_mask="::r" denied_mask="::r" fsuid=1000 ouid=0 name="/srv/etc/hosts" and then this - Feb 23 10:56:34 bigbang kernel: [ 407.494160] CIFS VFS: Error connecting to socket. Aborting operation Feb 23 10:56:34 bigbang kernel: [ 407.494181] CIFS VFS: cifs_mount failed w/return code = -110 Feb 23 10:56:34 bigbang SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit. Feb 23 10:56:34 bigbang ifup: eth1 device: Accton Technology Corporation SMC2-1211TX (rev 10) Feb 23 10:56:34 bigbang kernel: [ 407.763273] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 Feb 23 10:56:34 bigbang ifup: eth1 Feb 23 10:56:34 bigbang ifup: IP address: 192.168.2.100/24 Feb 23 10:56:34 bigbang ifup: Feb 23 10:56:44 bigbang kernel: [ 417.813131] eth1: no IPv6 routers present Feb 23 10:56:49 bigbang kernel: [ 423.136027] CIFS VFS: No response to cmd 115 mid 2 Feb 23 10:56:49 bigbang kernel: [ 423.136050] CIFS VFS: Send error in SessSetup = -11 Feb 23 10:56:49 bigbang kernel: [ 423.136072] CIFS VFS: cifs_mount failed w/return code = -11 Feb 23 10:56:49 bigbang SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit. Looking in boot.msg I also see what appears to be a switch in assignments for eth0 and eth1 taking place. But again I don't know if this is relevant or not... 6>[ 8.198726] eth0: RealTek RTL8139 at 0xffffc90005318e00, 00:e0:29:70:57:84, IRQ 22 <6>[ 8.211317] parport_pc 00:08: reported by Plug and Play ACPI <6>[ 8.211379] parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,ECP] <4>[ 8.222837] e1000e 0000:04:00.0: Warning: detected DSPD enabled in EEPROM <6>[ 8.273835] 0000:04:00.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:13:20:7a:8a:fb <6>[ 8.273841] 0000:04:00.0: eth1: Intel(R) PRO/1000 Network Connection <6>[ 8.274025] 0000:04:00.0: eth1: MAC: 2, PHY: 2, PBA No: ffffff-0ff <4>[ 8.274072] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray <6>[ 8.274077] Uniform CD-ROM driver Revision: 3.20 <7>[ 8.274232] sr 2:0:1:0: Attached scsi CD-ROM sr0 <6>[ 8.360572] ppdev: user-space parallel port driver <6>[ 8.368061] eth0 renamed to eth0_rename by udevd [378] <6>[ 8.370914] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 <7>[ 8.370976] HDA Intel 0000:00:1b.0: setting latency timer to 64 <6>[ 8.407975] eth1 renamed to eth0 by udevd [374] <6>[ 8.409008] udev: renamed network interface eth1 to eth0 <6>[ 8.416287] iTCO_vendor_support: vendor-support=0 <6>[ 8.417943] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05 <6>[ 8.418080] iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0460) <6>[ 8.418158] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) <6>[ 8.423031] eth0_rename renamed to eth1 by udevd [378] <6>[ 8.423991] udev: renamed network interface eth0_rename to eth1 (Sorry about the formatting, I got a new version of Thunderbird as well and it seems to be having all sorts of troubles with formatting at the moment.. sigh) I use the traditional ifup and ifdown methods, since in the past that was the only way to have the network initialize and ready in time for the startup of other services. KNetworkManager would always wait until after the boot process was completed and again that would break the startup of some of my other services. And like I said earlier, if I wait a few minutes, then eth1 seems to magically heal itself and doing an rcnetwork status will show it is up and running just fine. I don't do anything else in the meantime, just wait.... Any ideas on what I might be doing wrong and/or how to fix? Thanks in advance for any help/advice offered... Marc Chamberlin -- Marc Chamberlin www.marcchamberlin.com A man said unto the universe - "Sir I Exist!" "However" replied the universe "I do not see where that creates in me a sense of an obligation" S Crane.
Am Dienstag, 23. Februar 2010 21:00:19 schrieb Marc Chamberlin:
Doing an rcnetwork status right after the KDE gui comes up clearly shows that eth1 has failed to initialize -
Although you do not use NetworkManager, the cause might be the same as for the issue described in http://bugzilla.novell.com/show_bug.cgi?id=551705 Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2010-02-27 at 21:51 +0100, Sven Burmeister wrote:
Am Dienstag, 23. Februar 2010 21:00:19 schrieb Marc Chamberlin:
Doing an rcnetwork status right after the KDE gui comes up clearly shows that eth1 has failed to initialize -
Although you do not use NetworkManager, the cause might be the same as for the issue described in http://bugzilla.novell.com/show_bug.cgi?id=551705
Sven
That is why i had to increase the default waiting time for device-setup ( WAIT_FOR_INTERFACES="20" ), in /etc/sysconfig/network/config, from the default 20 seconds to 60 seconds, or many otherservices that depend on a proper working network will produce undesirable results.. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Hans Witvliet
-
Marc Chamberlin
-
Sven Burmeister