[opensuse] Yast -> Network Device - Not Re-Starting eth0 after changes
Listmates, I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine. This is a brand new install of 11.0. The card is activated on boot using traditional ifup and the card comes up fine. The install DVD media was verified and no errors occurred during the install. I have 4 other 11.0 installs and this is the only time I have seen this behavior. However, this is the only x86_64 fixed IP install I have that is working with traditional ifup. I have my x86_64 laptop, but that is using network manager. All 32-bit installs with fixed IP's work fine. Has anyone else experienced this "feature" with a fixed IP and x86_64? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Oct 19, 2008 at 2:19 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Listmates,
I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine.
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself. I am going to test this on the SLED beta and report a bug irregardless of what I find because this should be fixed in 11.0. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Andrew Joakimsen wrote:
On Sun, Oct 19, 2008 at 2:19 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Listmates,
I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine.
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
Isn't there a problem here: - connect to host via ssh - edit network settings - stop network I'm not sure the rest of the sequence, i.e. 'start network' is done after you've sawed off the branch you're sat on. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Andrew Joakimsen wrote:
On Sun, Oct 19, 2008 at 2:19 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Listmates,
I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine.
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
Isn't there a problem here:
- connect to host via ssh - edit network settings - stop network
I'm not sure the rest of the sequence, i.e. 'start network' is done after you've sawed off the branch you're sat on.
/Per Jessen, Zürich
No Per, this has been no-problem-at-all in the past. That is what yast's scripts do. When you hit 'Finish' yast stops the network to adjust the settings and then restarts the network with the new settings. No problem, the ssh connection isn't even dropped. The problem with Yast now is when you hit "Finish", yast stops the network to adjust the settings, the FAILS to execute the code that is supposed to restart the network. I could understand the case where there are errors in the changes and the card "won't" come back up, but that isn't what we are talking about here. We are talking perfect configuration so that all that needs to be done is for yast to issue the 'ifup' call -- but just doesn't. I've been remote managing and configuring machines for 8 years, 5 of those with SuSE and this is a new feature with yast software management in 11.0. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Per Jessen wrote:
Isn't there a problem here:
- connect to host via ssh - edit network settings - stop network
I'm not sure the rest of the sequence, i.e. 'start network' is done after you've sawed off the branch you're sat on.
/Per Jessen, Zürich
No Per, this has been no-problem-at-all in the past. That is what yast's scripts do. When you hit 'Finish' yast stops the network to adjust the settings and then restarts the network with the new settings. No problem, the ssh connection isn't even dropped. The problem with Yast now is when you hit "Finish", yast stops the network to adjust the settings, the FAILS to execute the code that is supposed to restart the network.
OK, I could have sworn I'd seen that before. I also do most install and management over ssh.
I could understand the case where there are errors in the changes and the card "won't" come back up, but that isn't what we are talking about here. We are talking perfect configuration so that all that needs to be done is for yast to issue the 'ifup' call -- but just doesn't.
Then it's a plain bug, especially when it worked before. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Oct 20, 2008 at 1:53 AM, Per Jessen <per@computer.org> wrote:
Andrew Joakimsen wrote:
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
Isn't there a problem here:
- connect to host via ssh - edit network settings - stop network
I'm not sure the rest of the sequence, i.e. 'start network' is done after you've sawed off the branch you're sat on.
No, the problem is there is a bug in the software. Obviously I am not manually stopping the network and expecting it to stay up, and I can even understand if the network connection were to drop and having to re-connect via SSH. But the case is if you change network settings via SSH using YaSt2, the connection will drop and you will physically go to the machine and find eth0 not up and need to do it manually. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi! Am Mo Oktober 20 2008 schrieb Andrew Joakimsen:
On Mon, Oct 20, 2008 at 1:53 AM, Per Jessen <per@computer.org> wrote:
Andrew Joakimsen wrote:
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
Isn't there a problem here:
- connect to host via ssh - edit network settings - stop network
I'm not sure the rest of the sequence, i.e. 'start network' is done after you've sawed off the branch you're sat on.
No, the problem is there is a bug in the software. Obviously I am not manually stopping the network and expecting it to stay up, and I can even understand if the network connection were to drop and having to re-connect via SSH. But the case is if you change network settings via SSH using YaSt2, the connection will drop and you will physically go to the machine and find eth0 not up and need to do it manually.
YaST is probably killed after stopping the network as it is no longer connected to a console. Did you try running yast via nohup or in screen? Regards, Matthias -- Matthias Bach - www.marix.org GPG/PGP Key-ID: 0xF0818B12
On Mon, Oct 20, 2008 at 11:50 AM, Matthias Bach <marix@marix.org> wrote:
Am Mo Oktober 20 2008 schrieb Andrew Joakimsen:
Andrew Joakimsen wrote:
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
No, the problem is there is a bug in the software. Obviously I am not manually stopping the network and expecting it to stay up, and I can even understand if the network connection were to drop and having to re-connect via SSH. But the case is if you change network settings via SSH using YaSt2, the connection will drop and you will physically go to the machine and find eth0 not up and need to do it manually.
YaST is probably killed after stopping the network as it is no longer connected to a console. Did you try running yast via nohup or in screen?
No, but I tested on my laptop running 10.3 and I can change the hostname in YaST2 via SSH and the network, and ssh session for that matter, says up. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Andrew Joakimsen wrote:
On Mon, Oct 20, 2008 at 11:50 AM, Matthias Bach <marix@marix.org> wrote:
Am Mo Oktober 20 2008 schrieb Andrew Joakimsen:
Andrew Joakimsen wrote:
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself.
No, the problem is there is a bug in the software. Obviously I am not manually stopping the network and expecting it to stay up, and I can even understand if the network connection were to drop and having to re-connect via SSH. But the case is if you change network settings via SSH using YaSt2, the connection will drop and you will physically go to the machine and find eth0 not up and need to do it manually. YaST is probably killed after stopping the network as it is no longer connected to a console. Did you try running yast via nohup or in screen?
No, but I tested on my laptop running 10.3 and I can change the hostname in YaST2 via SSH and the network, and ssh session for that matter, says up.
Andrew, All, I filed this under https://bugzilla.novell.com/show_bug.cgi?id=437182 If you could, please add additional comments there to cover anything I missed. Thanks. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Andrew Joakimsen wrote:
On Mon, Oct 20, 2008 at 11:50 AM, Matthias Bach <marix@marix.org> wrote:
Am Mo Oktober 20 2008 schrieb Andrew Joakimsen:
Andrew Joakimsen wrote:
I don't think it is specific to 64-bit systems, but I have noticed the same behavior when changing the hostname via ssh -- it never comes back online by itself. No, the problem is there is a bug in the software. Obviously I am not manually stopping the network and expecting it to stay up, and I can even understand if the network connection were to drop and having to re-connect via SSH. But the case is if you change network settings via SSH using YaSt2, the connection will drop and you will physically go to the machine and find eth0 not up and need to do it manually. YaST is probably killed after stopping the network as it is no longer connected to a console. Did you try running yast via nohup or in screen?
No, but I tested on my laptop running 10.3 and I can change the hostname in YaST2 via SSH and the network, and ssh session for that matter, says up.
Andrew, All,
I filed this under https://bugzilla.novell.com/show_bug.cgi?id=437182 If you could, please add additional comments there to cover anything I missed. Thanks.
I'm not sure what to make of the outcome. I guess the problem is fixed for 11.1. The plan for 11.0 is a little unclear. Anyway, the bug was closed with the following discussion: ------- Comment #3 From Alexander Orlovskyy 2008-10-22 00:48:42 MDT [reply] ------- Reassign to yast2-maintainers. ------- Comment #4 From Michal Zugec 2008-10-22 08:02:02 MDT [reply] ------- This problem is fixed in openSUSE11.1 (from Beta3 above) I guess that means there will be a patch some day for 11.0. However, until then, I would avoid any remote network card reconfiguration via YAST. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
I'm not sure what to make of the outcome. I guess the problem is fixed for 11.1. The plan for 11.0 is a little unclear. Anyway, the bug was closed with the following discussion:
------- Comment #3 From Alexander Orlovskyy 2008-10-22 00:48:42 MDT [reply] -------
Reassign to yast2-maintainers.
------- Comment #4 From Michal Zugec 2008-10-22 08:02:02 MDT [reply] -------
This problem is fixed in openSUSE11.1 (from Beta3 above)
I guess that means there will be a patch some day for 11.0. However, until then, I would avoid any remote network card reconfiguration via YAST.
As a workaround in the mean time. Create a small script named 'kicketh0' with something like: #!/bin/bash sleep 300 /sbin/ifup eth0 exit 0 (make the file executable) Start the script (as root) with './kicketh0 &' Then start yast2 (ncurses) from the command line, make your changes without delay and hit "finish". If yast fails to restart your network card, wait the remainder of the 300 seconds and try again. If yast works right, just 'killall kicketh0 && killall sleep' and your done. I tried yast again tonight with the script in the background. Murphy's law is alive and well -- yast worked like it was supposed to. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Listmates,
I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simply ifup eth0 started the card just fine.
This is a brand new install of 11.0. The card is activated on boot using traditional ifup and the card comes up fine. The install DVD media was verified and no errors occurred during the install. I have 4 other 11.0 installs and this is the only time I have seen this behavior. However, this is the only x86_64 fixed IP install I have that is working with traditional ifup. I have my x86_64 laptop, but that is using network manager.
All 32-bit installs with fixed IP's work fine. Has anyone else experienced this "feature" with a fixed IP and x86_64?
-- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com I have a similar problem with a wireless connection. It never starts first time after a reboot, I always have to go into Yast->Network Devices and select
On Sunday 19 October 2008 07:19:02 David C. Rankin wrote: the adaptor, click edit (not change anything), click next etc. finish and then it starts up. Strange? Phil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Andrew Joakimsen -
David C. Rankin -
Matthias Bach -
Per Jessen -
Philip Burness