Yast unable to restart network

[glistwan]

Hi,

When I change something in network setings using yast (for example hostname) it failes to restart the network. I have to start knetworkmanager manually from the terminal. Does anyone get the same type of behaviour ? I’m attaching the relevant yast log.

I’m using 11.3 KDE 4.5.4 2.6.34.7-0.5-desktop kernel.

2010-12-08 07:06:17 <1> opensusetest(6010) [YCP] network/runtime.ycp:28 Running SuSEconfig ...
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:60 Dummy 127.0.0.2 IP will be added
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:111 Writing hosts configuration
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:147 hosts=$"127.0.0.1":"localhost.localdomain	localhost"], "127.0.0.2":"opensusetest.site opensusetest"], "::1":"localhost ipv6-localhost ipv6-loopback"], "fe00::0":"ipv6-localnet"], "ff00::0":"ipv6-mcastprefix"], "ff02::1":"ipv6-allnodes"], "ff02::2":"ipv6-allrouters"], "ff02::3":"ipv6-allhosts"]]
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 127.0.0.1 ("localhost.localdomain	localhost"]:"localhost.localdomain	localhost"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 127.0.0.2 ("opensusetest.site opensusetest"]:"opensuse.site opensuse"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 ::1 ("localhost ipv6-localhost ipv6-loopback"]:"localhost ipv6-localhost ipv6-loopback"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 fe00::0 ("ipv6-localnet"]:"ipv6-localnet"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 ff00::0 ("ipv6-mcastprefix"]:"ipv6-mcastprefix"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 ff02::1 ("ipv6-allnodes"]:"ipv6-allnodes"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 ff02::2 ("ipv6-allrouters"]:"ipv6-allrouters"])
2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:149 ff02::3 ("ipv6-allhosts"]:"ipv6-allhosts"])
2010-12-08 07:06:22 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:66 Enabling service network
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall4Network.ycp:42 Writing the firewall configuration
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:3313 Some ServicesAcceptRelated are defined
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:2520 Firewall settings weren't modified, skipping...
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:2541 Firewall enable/disable wasn't modified, skipping...
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:1371 Firewall services are started
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:2418 Some RPC service found: false
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] SuSEFirewall.ycp:2452 Configuration hasn't modified, skipping restarting services
2010-12-08 07:06:23 <5> opensusetest.site(6010) [YCP] Lan.ycp:488 virt_net_proposal nil
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] Service.ycp:454 Reloading service network
2010-12-08 07:06:23 <1> opensusetest.site(6010) [YCP] Service.ycp:287 Running service initscript network reload
2010-12-08 07:06:30 <3> opensusetest.site(6010) [bash] ShellCommand.cc(shellcommand):78               No configuration found for pan0 
2010-12-08 07:06:30 <3> opensusetest.site(6010) [bash] ShellCommand.cc(shellcommand):78               Nevertheless the interface will be shut down.
2010-12-08 07:06:31 <3> opensusetest.site(6010) [bash] ShellCommand.cc(shellcommand):78 bridge-utils not installed
2010-12-08 07:07:06 <3> opensusetest.site(6010) [bash] ShellCommand.cc(shellcommand):78 waiting
2010-12-08 07:07:06 <1> opensusetest.site(6010) [YCP] network/runtime.ycp:28 Running SuSEconfig ...
2010-12-08 07:07:08 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:08 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 15
2010-12-08 07:07:09 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:09 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 14
2010-12-08 07:07:10 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:10 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 13
2010-12-08 07:07:11 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:11 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 12
2010-12-08 07:07:12 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:12 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 11
2010-12-08 07:07:13 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:13 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 10
2010-12-08 07:07:14 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:14 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 9
2010-12-08 07:07:15 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:15 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 8
2010-12-08 07:07:16 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:16 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 7
2010-12-08 07:07:17 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:17 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 6
2010-12-08 07:07:18 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:18 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 5
2010-12-08 07:07:19 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:19 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 4
2010-12-08 07:07:20 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:20 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 3
2010-12-08 07:07:21 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:21 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 2
2010-12-08 07:07:22 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running ...
2010-12-08 07:07:22 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network ... 1
2010-12-08 07:07:24 <1> opensusetest.site(6010) [ui] YPushButton.cc(setFunctionKey):204 Guessing button role YOKButton for YPushButton "OK" at 0xb0a93144 from function key F10
2010-12-08 07:07:48 <1> opensusetest.site(6010) [YCP] clients/lan.ycp:152 Lan module finished
2010-12-08 07:07:48 <1> opensusetest.site(6010) [YCP] clients/lan.ycp:153 ----------------------------------------
2010-12-08 07:07:48 <1> opensusetest.site(6010) [wfm] WFMSubAgent.cc(~WFMSubAgent):41 Deleting SubAgent: 0 scr
2010-12-08 07:07:48 <1> opensusetest.site(6010) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil)
2010-12-08 07:07:48 &lt;1&gt; opensusetest.site(6010) [agent-modules] ModulesConf.cc(writeFile):560 Modules not modified, not writing
2010-12-08 07:07:48 &lt;1&gt; opensusetest.site(6010) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil)
2010-12-08 07:07:48 <1> opensusetest.site(6010) [liby2] genericfrontend.cc(main):837 Finished YaST2 component 'y2base'
2010-12-08 07:07:48 <1> opensusetest.site(6010) [liby2] genericfrontend.cc(main):842 Exiting with client return value 'nil'
2010-12-08 07:07:48 <1> opensusetest.site(6010) [Y2Perl] YPerl.cc(destroy):164 Shutting down embedded Perl interpreter.

Best regards,
Greg

[keellambert]

Hi Greg,

Try the following,

1. in Yast–Network Settings–Global Options, select ‘Traditional Method with ifup’, then in the ‘Hostname/DNS’ tab - correct if necessary your host name, press ok & then reboot.
2. in Yast–Network Settings–Global Options, re-select ‘User Conrolled with NetworkManager’.

You should now be up and running.

Michael

[glistwan]

Thanks for the suggestion hovewer It doesn’t work. I still have to start knetworkmanager manually.

Best regards,
Greg

[chief_sealth]

@keellambert

1. in Yast–Network Settings–Global Options, select ‘Traditional Method with ifup’, then in the ‘Hostname/DNS’ tab - correct if necessary your host name, press ok & then reboot.

It’s not necessary to reboot. The changes should take place immediately.

[keellambert]

Hi Greg,

in Yast–Net Settings–Overview tab, what do you see in the lower pane, bottom three lines should be something like.

• Device Name: eth0
• Started xxxx
• IP address …

What does the xxxx state.

If this is MANUAL then switch back to ‘Traditional Method with ifup’, and then find the control to select AUTO then reboot.
Then after reboot go back and select ‘User Conrolled with NetworkManager’.

If this is AUTO then go to Yast-System-Hardware-Network-(“your Device Name” as stated above)-STARTMODE.
– If this parameter is set to manual, change it to auto click ok… and reboot.

Does this solve your problem?

Michael

[glistwan]

@keellambert

Hi Greg,

in Yast–Net Settings–Overview tab, what do you see in the lower pane, bottom three lines should be something like.

• Device Name: eth0
• Started xxxx
• IP address …

What does the xxxx state.

If this is MANUAL then switch back to ‘Traditional Method with ifup’, and then find the control to select AUTO then reboot.
Then after reboot go back and select ‘User Conrolled with NetworkManager’.

If this is AUTO then go to Yast-System-Hardware-Network-(“your Device Name” as stated above)-STARTMODE.
– If this parameter is set to manual, change it to auto click ok… and reboot.

Does this solve your problem?

Michael

Both are set to auto at the moment.

Best regards,
Greg

[keellambert]

Hi Greg,

Please confirm which of the following packages you have installed,
NetworkManager
NetworkManager-glib
NetworkManager-kde4
NetworkManager-kde4-libs
NetworkManager-kde4-libs-lang
libproxy1-networkmanager
plasmoid-networkmanagement

Michael

[glistwan]

NetworkManager-vpnc-0.8-3.1.i586
NetworkManager-openvpn-kde4-0.9.svn1192577-8.6.i586
NetworkManager-0.8-8.2.1.i586
NetworkManager-kde4-0.9.svn1192577-8.6.i586
NetworkManager-openvpn-0.8-3.1.i586
NetworkManager-vpnc-kde4-0.9.svn1192577-8.6.i586
NetworkManager-glib-0.8-8.2.1.i586
NetworkManager-kde4-libs-lang-0.9.svn1192577-8.6.noarch
NetworkManager-kde4-libs-0.9.svn1192577-8.6.i586
NetworkManager-pptp-0.8-3.1.i586
NetworkManager-pptp-kde4-0.9.svn1192577-8.6.i586
libproxy1-networkmanager-0.4.3-1.3.i586

Best regards,
Greg

[keellambert]

Try copying the file,
/usr/share/kde4/env/knetworkmanager.default.sh
to
/home/<<your user name>>/.kde4/share/autostart/knetworkmanager.default.sh

and restart X.

If it does not work try putting a file <<anyname>>.sh into directory /home/<<your user name>>/.kde4/share/autostart/
with the contents,

knetworkmanager

and then restarting X
If either work it is only papering over why its not working in the first place.

Michael

[robin_listas]

On 2010-12-09 19:36, glistwan wrote:
>
> Hi,
>
> When I change something in network setings using yast (for example
> hostname) it failes to restart the network. I have to start
> knetworkmanager manually from the terminal. Does anyone get the same
> type of behaviour ? I’m attaching the relevant yast log.
>
> I’m using 11.3 KDE 4.5.4 2.6.34.7-0.5-desktop kernel.
>
>
> Code:
> --------------------
> 2010-12-08 07:06:17 <1> opensusetest(6010) [YCP] network/runtime.ycp:28 Running SuSEconfig …
> 2010-12-08 07:06:21 <1> opensusetest.site(6010) [YCP] Host.ycp:60 Dummy 127.0.0.2 IP will be added
…
> 2010-12-08 07:07:06 <1> opensusetest.site(6010) [YCP] network/runtime.ycp:28 Running SuSEconfig …
> 2010-12-08 07:07:08 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running …
> 2010-12-08 07:07:08 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network … 15
…
> 2010-12-08 07:07:22 <1> opensusetest.site(6010) [YCP] NetworkService.ycp:141 Network is not running …
> 2010-12-08 07:07:22 <1> opensusetest.site(6010) [YCP] Lan.ycp:563 waiting for network … 1
> --------------------

The SuSEconfig script can take long to run, sometimes even a minute. I
don’t see there the output of the script or that it really waits for it. I
could be mistaken, but I would try to run it in a root’s xterm, see if
there are errors or warnings.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

[glistwan]

@keellambert

Try copying the file,
/usr/share/kde4/env/knetworkmanager.default.sh
to
/home/<<your user name>>/.kde4/share/autostart/knetworkmanager.default.sh

and restart X.

If it does not work try putting a file <<anyname>>.sh into directory /home/<<your user name>>/.kde4/share/autostart/
with the contents,

knetworkmanager

and then restarting X
If either work it is only papering over why its not working in the first place.

Michael

Restarting X works even without copying the scripts You specified to my home directory.

@robin_listas

The SuSEconfig script can take long to run, sometimes even a minute. I
don’t see there the output of the script or that it really waits for it. I
could be mistaken, but I would try to run it in a root’s xterm, see if
there are errors or warnings.

You would like me to run

/etc/init.d/network restart

as root and post the output here ?

Best regards,
Greg

[keellambert]

Hi Greg,

1. Is your network up and running after a reboot? Or do you have to start it manually?

2. My machine reboots from the gui to the melody playing at the gui start in under 60 seconds, including the logging in. Pause in Grub is set at 4 seconds.

Michael

[glistwan]

@keellambert

Hi Greg,

1. Is your network up and running after a reboot? Or do you have to start it manually?

2. My machine reboots from the gui to the melody playing at the gui start in under 60 seconds, including the logging in. Pause in Grub is set at 4 seconds.

Michael

Yep it works automatically after the reboot. I was just wondering why Yast fails to restart the network.

Best regards,
Greg

[robin_listas]

On 2010-12-11 10:06, glistwan wrote:
> robin_listas Wrote:

> You would like me to run
>
> Code:
> --------------------
> /etc/init.d/network restart
> --------------------
>
> as root and post the output here ?

No, SuSEconfig. No need to post the output, use your judgement

I mean, it will print a long list, but does it complain of errors?

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

[glistwan]

Error in file "/usr/share/applications/kde4/kfontview.desktop": "fonts/package" is an invalid MIME type ("fonts" is an unregistered media type)

That’s the only error SuSEconfig generates. There are also some warnings concerning fonts but thats all.

Best regards,
Greg

[keellambert]

Hi Greg,

My logic tells me the event you describe is normal. After any low level system parameter change I would expect a reboot necessary for its implementation.

If you notice, on a normal boot, the machine name is give on the first splash screen after your bootloader screen. This implies the machine name is embedded in the initialization scripts, perhaps even the initrd file.

Have a good Christmas & a happy New Year.

Michael

[glistwan]

Maybe Your right
Thanks a lot for help anyway.

Thanks and have a good Christmas $ a happy new year as well.

Best regards,
Greg

[robin_listas]

On 2010-12-11 18:36, keellambert wrote:
>
> Hi Greg,
>
> My logic tells me the event you describe is normal. After any low level
> system parameter change I would expect a reboot necessary for its
> implementation.

In Linux, no.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

[robin_listas]

On 2010-12-11 16:36, glistwan wrote:

> That’s the only error SuSEconfig generates. There are also some
> warnings concerning fonts but thats all.

Then I don’t know.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

[glistwan]

@robin_listas

On 2010-12-11 16:36, glistwan wrote:

> That’s the only error SuSEconfig generates. There are also some
> warnings concerning fonts but thats all.

Then I don’t know.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Thank a lot for help anyway.

Best regards,
Greg