Bugzilla – Bug 106040
network down right after SUSE 10.0 installation
Last modified: 2005-09-05 08:37:15 UTC
Close to the end of SUSE 10.0 installation when network settings are shown I did change my settings from DHCP to a static address. Then after finishing the installation I end up (without rebooting) in my installed SUSE 10.0. At that very point the network is not up. So the first impression I get is: network installation went wrong. Workaround A: I start the network manually. Workaround B: I use YaST2 once more to set my network parameters. Workaround C: I reboot the system. After the workarounds the network works just fine. FMF
Created attachment 46781 [details] YaST2 logs
I have been using rcnetwork reload to apply the network settings after yast has changed them. In beta 2 it stopped working for the case where the network was not up already. (This may not be exactly this bug, but anyway.) Christian, should I check with rcnetwork status and use rcnetwork start in that case? I have the impression that status is quite thorough and verbose. Does it have a lightweight variant that I could use?
'rcnetwork status -o quiet' is all i have for you. But after this final instalation dialogs, YaST script call rcnetwork stop and then bootng continues and calls network start. So what was the problem with the reload? The only problem i see is that network reload starts the network. That must not be. Then if network reload doesn't do that any longer, your relaod will have no effect. After Yast finishes it will stopped, started again and all is fine, istn't it?
I just detected that rcnetwork status is broken in beta2. I fixed that and made reload skip if network was not started.
OK. yast unnecessarily brought the interface down (incorrect attempt at locale independence) and then failed to start it again because it used reload instead of start. I have fixed both things.
(In reply to comment #5) > OK. yast unnecessarily brought the interface down (incorrect attempt at locale > independence) and then failed to start it again because it used reload instead > of start. I have fixed both things. Fixed in which milestone?
In yast2-network-2.12.12, Beta 3.
Thanks for the info and the quick fix! FMF
Martin, you had nothing to change. Keep the reload. that was fine. Why dod you try to start the network short before the boot process will do it anyway? Or, if you are right, explain me why it was wrong?
The network needs to be up because the rest of yast wants it: online update, user database in NIS or LDAP... The problem with reload was that it would be used to apply the network settings in all cases, even if nothing was running before. It used to work but now it does not. Unlike restart, reload is not specified for the case when the service is not already running.
OK, thanks. I guess i need some recreation. ;/ Service network is never up in that stage, so network start is of course right.
After installing beta3 I am sorry to tell you, that this bug is still there and did not change at all.
Might be a duplicate of bug 112909. Do you use localtime in your hardware clock or UTC?
1. I use localtime in my HW clock 2. I do not use DHCP, I gave a static address.
dhcp or static does not matter. *** This bug has been marked as a duplicate of 112909 ***
Just installed beta4. The bug is still there.
It is enough to reopen one bug, not all bugs that are marked as its duplicates. Unless you think that it is not a duplicate after all, but I believe it is not the case here. *** This bug has been marked as a duplicate of 112909 ***