http://bugzilla.novell.com/show_bug.cgi?id=518219 User zuziak@math.ku.dk added comment http://bugzilla.novell.com/show_bug.cgi?id=518219#c12 Martin Zuziak <zuziak@math.ku.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|zuziak@math.ku.dk | --- Comment #12 from Martin Zuziak <zuziak@math.ku.dk> 2009-07-10 06:18:31 MDT --- This problem is far less prevalent than I thought. I've been keeping an eye on my openSuSE 11.1 machines (about 15) and they don't show this problem. So I've only seen it on my test machine which is a virtual machine running on vmware-server (on another openSuSE 11.1). I assumed that this problem was the cause of some stale NFS locks on 11.1 clients but that seems to be caused by bug #520311 instead. Running on vmware-server makes it slow which might be what triggers this. I'm sorry I should have mentioned that, but it would be nice if it would work on virtual machines also. eth0 isn't set up as mandatory in /etc/sysconfig/network/config. I've tried doing that but it didn't help. I guess it should be mandatory automatically as a physical interface with STARTMODE='auto'. Anyway, there's only a single ethernet adapter, it has no exotic configuration. I've attached boot.msg and config, dhcp and ifcfg-eth0 from /etc/sysconfig/network.
From the log: I've inserted a loop in the nfs init script just before sm-notify runs. It logs the current hostname and sleeps for 1 second until the hostname is correct.
Jul 10 13:25:13 linux ifup: eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) Jul 10 13:25:15 linux logger: nfs: hostname is linux Jul 10 13:25:15 linux SuSEfirewall2: SuSEfirewall2 not active Jul 10 13:25:15 linux dhcpcd[2501]: eth0: setting hostname to `pc000c292d9978.math.ku.dk' Jul 10 13:25:15 linux dhcpcd[2501]: eth0: forking to background Jul 10 13:25:15 linux dhcpcd[3012]: eth0: waiting for 1800 seconds Jul 10 13:25:15 linux dhcpcd[2501]: eth0: exiting Jul 10 13:25:16 linux logger: nfs: hostname is pc000c292d9978.math.ku.dk Jul 10 13:25:17 linux sm-notify[3018]: sm-notify running as root. chown /var/lib/nfs/sm to choose different us er Even when I set eth0 as mandatory it doesn't show in the following output. Is that a problem? # /etc/init.d/rc5.d/S*network start -o debug fake CONFIG = INTERFACE = AVAILABLE_IFACES = eth0 PHYSICAL_IFACES = eth0 BONDING_IFACES = VLAN_IFACES = DIALUP_IFACES = TUNNEL_IFACES = BRIDGE_IFACES = SLAVE_IFACES = MANDATORY_DEVICES = VIRTUAL_IFACES = SKIP = start order : eth0 ; ; Setting up network interfaces: ifup eth0 -o rc eth0 returned 0 done .. still waiting for hotplug devices: SUCCESS_IFACES= eth0 MANDATORY_DEVICES= .. final SUCCESS_IFACES= eth0 MANDATORY_DEVICES= FAILED=0 ifup-route noiface -o rc Setting up service network . . . . . . . . -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.