SuSE 12.1 - After resume from "Hibernation" network connection won't work

uzivak · July 26, 2012, 10:03am

As it said in the title I have this problem. In the case resuming from sleep network works fine. In the case of normal boot up works of course fine. But as I find I prefer sleep instead of hibernation I do not recognize it as a big bug. So for interest if there is some solution. Thanks Jiri

glistwan · July 26, 2012, 11:27am

As a workaround you can try this command :


/etc/init.d/network restart

Also please specify if you connect with WiFi or cable.

robin_listas · July 26, 2012, 11:43am

On 2012-07-26 10:06, uzivak wrote:
>
> As it said in the title I have this problem. In the case resuming from
> sleep network works fine. In the case of normal boot up works of course
> fine. But as I find I prefer sleep instead of hibernation I do not
> recognize it as a big bug. So for interest if there is some solution.

Traditional networking or via desktop applet?

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

uzivak · July 27, 2012, 8:43am

I hope traditional. I am not using any desktop applet.

uzivak · July 27, 2012, 9:15am

That command returns:

redirecting to systemctl
Failed to issue method call: Access denied

glistwan · July 27, 2012, 10:13am

You need to run this as root. Use this command before :


su -

and enter the root password. After that the command that restarts the network will work.

uzivak · July 27, 2012, 12:44pm

I did
“Doma:~ # /etc/init.d/network restart”

and this is the result:

           "redirecting to systemctl"

            "Job failed. See system logs and 'systemctl status' for details."

glistwan · July 27, 2012, 12:59pm

uzivak:

I did
“Doma:~ # /etc/init.d/network restart”

and this is the result:
           "redirecting to systemctl"

            "Job failed. See system logs and 'systemctl status' for details."

And what is the output of ‘systemctl status’ ?

You could also try this systemd command :

systemctl restart network.service

instead of the one I gave you erlier. (it was working fine with sysintv )

robin_listas · July 27, 2012, 3:53pm

On 2012-07-27 12:46, uzivak wrote:
>
> I did
> “Doma:~ # /etc/init.d/network restart”
>
> and this is the result:
>
> “redirecting to systemctl”
>
> “Job failed. See system logs and ‘systemctl status’ for
> details.”

Please do as the error message recommended. What do you see there?

And use code tags to post results.

Posting in Code Tags - A Guide

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

uzivak · July 29, 2012, 6:52am

glistwan:

And what is the output of ‘systemctl status’ ?

You could also try this systemd command :
systemctl restart network.service
instead of the one I gave you erlier. (it was working fine with sysintv )

Here is the result:

   
Doma:~ # systemctl restart network.service 
Job failed. See system logs and 'systemctl status' for details.

uzivak · July 29, 2012, 6:54am

Using CODE tags learned.
I don’t know where are this systems logs and I also don’t know what is it “systemctl status”.

glistwan · July 29, 2012, 1:43pm

It’s a command to show more information about the error. One of the systemd magic tricks. You can read more here :
https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet

robin_listas · July 29, 2012, 2:03pm

On 2012-07-29 13:46, glistwan wrote:
>
> uzivak;2476988 Wrote:
>> Using CODE tags learned.
>> I don’t know where are this systems logs and I also don’t know what is
>> it “systemctl status”.
> It’s a command to show more information about the error. One of the
> systemd magic tricks. You can read more here :
> https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet

And all system logs are in the system log directory, ie, /var/log/. You can sort by date and
see what files changed recently, but it will be the messages file. Or, you can open a terminal,
and run this sequence:


cer@Telcontar:~> su -
Password:
Telcontar:~ # tailf /var/log/messages

And then in another terminal try to restart the network again. The new log messages will
display in the first terminal, so you can copypaste them here.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

uzivak · August 12, 2012, 8:08pm

robin_listas:

On 2012-07-29 13:46, glistwan wrote:
>
> uzivak;2476988 Wrote:
>> Using CODE tags learned.
>> I don’t know where are this systems logs and I also don’t know what is
>> it “systemctl status”.
> It’s a command to show more information about the error. One of the
> systemd magic tricks. You can read more here :
> https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet

And all system logs are in the system log directory, ie, /var/log/. You can sort by date and
see what files changed recently, but it will be the messages file. Or, you can open a terminal,
and run this sequence:
cer@Telcontar:~> su -
Password:
Telcontar:~ # tailf /var/log/messages
And then in another terminal try to restart the network again. The new log messages will
display in the first terminal, so you can copypaste them here.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Terminal 1:


jiri@Doma:~>su -
Heslo:
Doma:~ # tailf /var/log/messages

Terminal 2:


Doma:~ # systemctl restart network.service

Aug 12 19:55:37 Doma network[13726]: Shutting down network interfaces:
Aug 12 19:55:37 Doma network[13726]: br0
Aug 12 19:55:37 Doma ifdown[14011]: br0
Aug 12 19:55:37 Doma network[13726]: xc: error: Could not obtain handle on privileged command interface (2 = No such file or directory): Internal error
Aug 12 19:55:37 Doma network[13726]: Traceback (most recent call last):
Aug 12 19:55:37 Doma network[13726]: File “/usr/sbin/xend”, line 36, in
Aug 12 19:55:37 Doma network[13726]: from xen.xend.server import SrvDaemon
Aug 12 19:55:37 Doma network[13726]: File “/usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py”, line 26, in
Aug 12 19:55:37 Doma network[13726]: import relocate
Aug 12 19:55:37 Doma network[13726]: File “/usr/lib64/python2.7/site-packages/xen/xend/server/relocate.py”, line 28, in
Aug 12 19:55:37 Doma network[13726]: from xen.xend import XendDomain
Aug 12 19:55:37 Doma network[13726]: File “/usr/lib64/python2.7/site-packages/xen/xend/XendDomain.py”, line 36, in
Aug 12 19:55:37 Doma network[13726]: from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
Aug 12 19:55:37 Doma network[13726]: File “/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py”, line 20, in
Aug 12 19:55:37 Doma network[13726]: from xen.xend import balloon, sxp, image
Aug 12 19:55:37 Doma network[13726]: File “/usr/lib64/python2.7/site-packages/xen/xend/image.py”, line 46, in
Aug 12 19:55:37 Doma network[13726]: xc = xen.lowlevel.xc.xc()
Aug 12 19:55:37 Doma network[13726]: xen.lowlevel.xc.Error: (1, ‘Internal error’, ‘xc_interface_open failed: No such file or directory’)
Aug 12 19:55:37 Doma network[13726]: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running?
Aug 12 19:55:37 Doma network[13726]: failed to stat /var/run/xenstored.pid: No such file or directory
Aug 12 19:55:37 Doma network[13726]: cannot init xl context
Aug 12 19:55:37 Doma dhcpcd[14077]: br0: sending signal 15 to pid 13575
Aug 12 19:55:37 Doma dhcpcd[14077]: br0: exiting
Aug 12 19:55:37 Doma dhcpcd[13575]: br0: received SIGTERM, stopping
Aug 12 19:55:37 Doma dhcpcd[13575]: br0: removing default route via 192.168.0.1 metric 0
Aug 12 19:55:37 Doma dhcpcd[13575]: br0: removing IP address 192.168.0.124/24
Aug 12 19:55:37 Doma avahi-daemon[886]: Withdrawing address record for 192.168.0.124 on br0.
Aug 12 19:55:37 Doma avahi-daemon[886]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.0.124.
Aug 12 19:55:37 Doma avahi-daemon[886]: Interface br0.IPv4 no longer relevant for mDNS.
Aug 12 19:55:37 Doma dhcpcd[13575]: br0: exiting
Aug 12 19:55:38 Doma avahi-daemon[886]: Withdrawing address record for fe80::1e6f:65ff:fecc:9559 on br0.
Aug 12 19:55:38 Doma kernel: [46359.465111] br0: port 1(eth0) entering forwarding state
Aug 12 19:55:38 Doma avahi-daemon[886]: Withdrawing workstation service for br0.
Aug 12 19:55:38 Doma kernel: [46359.484124] device eth0 left promiscuous mode
Aug 12 19:55:38 Doma kernel: [46359.484137] br0: port 1(eth0) entering disabled state
Aug 12 19:55:38 Doma avahi-daemon[886]: Withdrawing address record for fe80::1e6f:65ff:fecc:9559 on eth0.
Aug 12 19:55:38 Doma network[13726]: …done eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
Aug 12 19:55:38 Doma ifdown[14239]: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
Aug 12 19:55:39 Doma network[13726]: …doneShutting down service network . . . . . . . . …done
Aug 12 19:55:40 Doma network[14425]: Setting up network interfaces:
Aug 12 19:55:40 Doma network[14425]: lo
Aug 12 19:55:40 Doma ifup[14678]: lo
Aug 12 19:55:40 Doma ifup[14678]: lo
Aug 12 19:55:40 Doma ifup[14678]: IP address: 127.0.0.1/8
Aug 12 19:55:40 Doma network[14425]: lo IP address: 127.0.0.1/8
Aug 12 19:55:40 Doma ifup[14678]:
Aug 12 19:55:40 Doma network[14425]: …done eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
Aug 12 19:55:40 Doma ifup[14782]: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
Aug 12 19:55:40 Doma kernel: [46361.541968] r8169 0000:05:00.0: eth0: link down
Aug 12 19:55:40 Doma kernel: [46361.541978] r8169 0000:05:00.0: eth0: link down
Aug 12 19:55:40 Doma kernel: [46361.542725] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 12 19:55:40 Doma ifup[14782]: eth0
Aug 12 19:55:40 Doma ifup[14782]: IP address: 0.0.0.0/32
Aug 12 19:55:40 Doma network[14425]: eth0 IP address: 0.0.0.0/32
Aug 12 19:55:40 Doma ifup[14782]:
Aug 12 19:55:40 Doma SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 …
Aug 12 19:55:40 Doma SuSEfirewall2: Firewall rules successfully set
Aug 12 19:55:40 Doma network[14425]: …done br0
Aug 12 19:55:40 Doma ifup[14966]: br0
Aug 12 19:55:40 Doma kernel: [46361.875684] device eth0 entered promiscuous mode
Aug 12 19:55:40 Doma network[14425]: br0 Ports: [eth0]
Aug 12 19:55:40 Doma kernel: [46361.879705] ADDRCONF(NETDEV_UP): br0: link is not ready
Aug 12 19:55:40 Doma ifup-bridge[15016]: br0 forwarddelay (see man ifcfg-bridge)
Aug 12 19:55:42 Doma kernel: [46363.092125] r8169 0000:05:00.0: eth0: link up
Aug 12 19:55:42 Doma kernel: [46363.094513] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 12 19:55:42 Doma kernel: [46363.094945] br0: port 1(eth0) entering forwarding state
Aug 12 19:55:42 Doma kernel: [46363.094971] br0: port 1(eth0) entering forwarding state
Aug 12 19:55:42 Doma kernel: [46363.097358] ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
Aug 12 19:55:42 Doma network[14425]: br0 forwarddelay (see man ifcfg-bridge) … ready
Aug 12 19:55:42 Doma ifup-bridge[15016]: … ready
Aug 12 19:55:42 Doma ifup-dhcp[15146]: br0 Starting DHCP4+DHCP6 client
Aug 12 19:55:42 Doma dhcpcd[15209]: br0: dhcpcd 3.2.3 starting
Aug 12 19:55:42 Doma dhcpcd[15209]: br0: hardware address = 1c:6f:65:cc:95:59
Aug 12 19:55:42 Doma dhcpcd[15209]: br0: broadcasting for a lease
Aug 12 19:55:43 Doma ifup-dhcp[15146]: .
Aug 12 19:55:43 Doma avahi-daemon[886]: Registering new address record for fe80::1e6f:65ff:fecc:9559 on eth0..
Aug 12 19:55:43 Doma avahi-daemon[886]: Registering new address record for fe80::1e6f:65ff:fecc:9559 on br0..
Aug 12 19:55:45 Doma ifup-dhcp[15146]: .
Aug 12 19:55:52 ifup-dhcp[15146]: last message repeated 2 times
Aug 12 19:55:52 Doma kernel: [46373.394033] eth0: no IPv6 routers present
Aug 12 19:55:52 Doma kernel: [46373.626014] br0: no IPv6 routers present
Aug 12 19:55:53 Doma ifup-dhcp[15146]: .
Aug 12 19:56:02 ifup-dhcp[15146]: last message repeated 3 times
Aug 12 19:56:02 Doma network[14425]: br0 Starting DHCP4+DHCP6 client. . . . . . . .
Aug 12 19:56:02 Doma ifup-dhcp[15146]:
Aug 12 19:56:02 Doma network[14425]: br0 DHCP4 continues in background
Aug 12 19:56:02 Doma ifup-dhcp[15146]: br0 DHCP4 continues in background
Aug 12 19:56:02 Doma network[14425]: br0 DHCP6 continues in background
Aug 12 19:56:02 Doma ifup-dhcp[15146]: br0 DHCP6 continues in background
Aug 12 19:56:02 Doma network[14425]: [1Awaiting
Aug 12 19:56:02 Doma dhcpcd[15209]: br0: timed out
Aug 12 19:56:02 Doma dhcpcd[15209]: br0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-br0.info’
Aug 12 19:56:02 Doma dhcpcd[15209]: br0: adding IP address 192.168.0.124/24
Aug 12 19:56:02 Doma avahi-daemon[886]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.124.
Aug 12 19:56:02 Doma dhcpcd[15209]: br0: adding default route via 192.168.0.1 metric 0
Aug 12 19:56:02 Doma avahi-daemon[886]: New relevant interface br0.IPv4 for mDNS.
Aug 12 19:56:02 Doma avahi-daemon[886]: Registering new address record for 192.168.0.124 on br0.IPv4.
Aug 12 19:56:03 Doma network[14425]: Waiting for virtual interfaces: br0
Aug 12 19:56:03 Doma ifdown[16840]: br0
Aug 12 19:56:12 Doma network[14425]: 8 7 6 4 3 2 1 0
Aug 12 19:56:12 Doma network[14425]: br0
Aug 12 19:56:12 Doma network[14425]: br0 DHCP4 client (dhcpcd) is running
Aug 12 19:56:12 Doma network[14425]: br0 . . . but is still waiting for data
Aug 12 19:56:12 Doma network[14425]: br0 DHCP6 client (dhclient6) is running
Aug 12 19:56:12 Doma network[14425]: br0 . . . but is still waiting for data
Aug 12 19:56:12 Doma network[14425]: br0 IP address: 192.168.0.124/24
Aug 12 19:56:12 Doma network[14425]: br0 is up
Aug 12 19:56:12 Doma network[14425]: [1Awaiting
Aug 12 19:56:12 Doma network[14425]: br0 interface is not ready until now
Aug 12 19:56:12 Doma network[14425]: …failedSetting up service network . . . . . . . . . …failed
Aug 12 19:56:12 Doma systemd[1]: network.service: control process exited, code=exited status=7
Aug 12 19:56:12 Doma systemd[1]: Unit network.service entered failed state.
Aug 12 19:56:18 Doma dhcpcd[15209]: br0: Failed to lookup hostname via DNS: Temporary failure in name resolution
Aug 12 19:56:18 Doma ifup[17573]: br0
Aug 12 19:56:18 Doma SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 …
Aug 12 19:56:18 Doma SuSEfirewall2: using default zone ‘ext’ for interface br0
Aug 12 19:56:18 Doma SuSEfirewall2: Firewall rules successfully set
Aug 12 19:56:18 Doma dhcpcd[15209]: br0: exiting

HealingMindNOS · August 15, 2012, 9:12am

I had the same problem. After waking OSS 12.1 from a sleep, it didn’t want to log on a wifi network anymore, so I plugged “/etc/init.d/network restart” into a root terminal, it paused for a moment at “redirecting to systemctl,” now I’m back on the network!

I’m guessing this is a bug. How do I look it up or log it? Thanks in advance!

robin_listas · August 17, 2012, 12:48am

On 2012-08-12 20:16, uzivak wrote:

…

> Code:
> --------------------
>
> Doma:~ # systemctl restart network.service
>
> --------------------

The messages below should go inside code tags, too. But I see you are using xen, I have no
experience there.

>
>
> Aug 12 19:55:37 Doma network[13726]: Shutting down network interfaces:
> Aug 12 19:55:37 Doma network[13726]: br0
> Aug 12 19:55:37 Doma ifdown[14011]: br0
> Aug 12 19:55:37 Doma network[13726]: xc: error: Could not obtain handle
> on privileged command interface (2 = No such file or directory):
> Internal error
> Aug 12 19:55:37 Doma network[13726]: Traceback (most recent call last):
> Aug 12 19:55:37 Doma network[13726]: File “/usr/sbin/xend”, line 36, in
> <module>
> Aug 12 19:55:37 Doma network[13726]: from xen.xend.server import
> SrvDaemon

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

robin_listas · August 17, 2012, 12:48am

On 2012-08-15 09:16, HealingMindNOS wrote:
>
> I had the same problem.

Exactly the same, same error log? I guess not.

> After waking OSS 12.1 from a sleep, it didn’t
> want to log on a wifi network anymore, so I plugged “/etc/init.d/network
> restart” into a root terminal, it paused for a moment at “redirecting to
> systemctl,” now I’m back on the network!
>
> I’m guessing this is a bug. How do I look it up or log it? Thanks in
> advance!

openSUSE:Submitting bug reports

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

pschmidtke · December 10, 2012, 6:33pm

I now have the very same problem on openSuse 12.2 after a erroneous restart from hibernation (I had to switch off the machine completely)

Now I get an IP adress from my DHCP, but I can not ing my router (192.168.0.1) which is a bit weird. I connect via ifconfig, so no network manager.

I get the often seen error : network.service: control process exited, code=exited status=7

Even after a “service network restart” I cannot bring my connection up and running so now I am really stuck. Anyone has an idea of how to solve this issue?

Thanks in advance.

peter