Network Manager doesn't start

Hello everyone!

Please, help to solve the problem.
Network Manager doesn’t start since last update
Opensuse 12.3. Try to reinstall - no result.

systemctl start network.service
Job for NetworkManager.service failed. See systemctl status Network Manager.service and journalctl -n for details.

journalctl -n
NetworkManager.service: main process exited, code=killed, status=11/SEGV
Failed to start Network Manager.
Unit networkManager.service entered failed state

Thanks a lot in advance.

Yast → Network Devices → Network Settings

Click the “Global Options” tab.

Switch to using “ifup” configuration instead of NetworkManager.

Then click the “Overview” tab, and configure your network device(s).

(I may have some of the names wrong there – I’m looking at 13.2, and some names have changed).

You should be able to get the network going with “ifup” settings.

That doesn’t fix NetworkManager. But it should get you a connection, and maybe you can then try again to reinstall NetworkManager. Or consider installing/upgrading to 13.2, since 12.3 is approaching end-of-life anyway.

Thank you, I do it, but here is one more error…

dhclient eth0
/sbin/dhclient-script: line 282: /etc/init.d/syslog: No such file or directory
scripts/functions.common: line 137: logger: command not found
Failed to issue method call: Unit winbind.service failed to load: No such file or directory. See system logs and ‘systemctl status winbind.service’ for details.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
iptables-batch v1.4.21: invalid port/service NXPort' specified Try iptables-batch -h’ or ‘iptables-batch --help’ for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
iptables v1.4.21: invalid port/service NXPort' specified Try iptables -h’ or ‘iptables --help’ for more information.
ip6tables-batch v1.4.21: invalid port/service NXPort' specified Try ip6tables-batch -h’ or ‘ip6tables-batch --help’ for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
ip6tables v1.4.21: invalid port/service NXPort' specified Try ip6tables -h’ or ‘ip6tables --help’ for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory

That brings back memories.

That’s a bug. It was fixed a long time ago. But you didn’t install that update, so you still have the bug.

The default should have been for your system to use “dhcpcd” rather than “dhclient” for DHCP lookups. I’m not sure how that changed. You will have to change back to “dhcpcd”. You can change that in Yast “/etc/sysconfig” editor. You may need to look around. I can’t easily check, because that part has changed a lot in the opensuse 13.2 that I am currently running. With “dhcpcd” you should be able to get your network running.

My recollection is that I used to change to “dhclient” because “dhcpcd” bungled some things (such as WiFi). So if you have trouble with WiFi setup, see if you can use an ethernet cable connection at least until you have run updates and got your system fully up to date.

As I understand you mean to put DHCLIENT_BIN=“dhcpcd”

I do it. But the logs are the same:

localhost:/home/lubov # dhclient eth0
scripts/functions.common: line 137: logger: command not found
Failed to issue method call: Unit winbind.service failed to load: No such file or directory. See system logs and 'systemctl status winbind.service' for details.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
iptables-batch v1.4.21: invalid port/service `NXPort' specified
Try `iptables-batch -h' or 'iptables-batch --help' for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
iptables v1.4.21: invalid port/service `NXPort' specified
Try `iptables -h' or 'iptables --help' for more information.
ip6tables-batch v1.4.21: invalid port/service `NXPort' specified
Try `ip6tables-batch -h' or 'ip6tables-batch --help' for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
ip6tables v1.4.21: invalid port/service `NXPort' specified
Try `ip6tables -h' or 'ip6tables --help' for more information.
/sbin/SuSEfirewall2: line 115: /bin/logger: No such file or directory
localhost:/home/lubov # 

You probably have to restart the network.

Maybe:


# systemctl stop network.service
###  wait a few seconds
# systemctl start network.service

Or rebooting should also restart the network.

Here’s my best recollection of the bug. After a successful DHCP lookup, the “dhclient” command runs “/sbin/dhclient-script”. But there was a messed up file descriptor, so that any message to stderr accidently went to “/sbin/dhclient-script” and clobbered that file. Hence the error that you are getting.

Hm… What is happening:


dhclient eth0
bash: dhclient: command not found
dhcpcd eth0
err,eth failed to lookup hostname via DNS: Name or service not known