| View previous topic :: View next topic |
| Author |
Message |
ruddy32
n00b
Joined: 07 May 2014
Posts: 40
Location: France
|
 Posted: Sun Aug 31, 2014 9:33 pm Post subject: [systemd] service failed at boot (solved) |
 |
|
Hi,
Many services cannot start at boot time. It's not possible to logon the system, keyboard input did not work. Using chroot, I get following errors in /var/log/messages:
| Code: |
...
Aug 31 00:20:10 lt001 systemd[1]: Failed to start Wait for Plymouth Boot Screen to Quit.
Aug 31 00:20:10 lt001 systemd[1]: Unit plymouth-quit-wait.service entered failed state.
...
Aug 31 00:20:14 lt001 systemd-logind[4749]: Failed to add match for NameOwnerChanged: Connection timed out
Aug 31 00:20:14 lt001 systemd-logind[4749]: Failed to fully start up daemon: Connection timed out
Aug 31 00:20:14 lt001 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Aug 31 00:20:14 lt001 systemd[1]: Failed to start Login Service.
Aug 31 00:20:14 lt001 systemd[1]: Unit systemd-logind.service entered failed state.
...
Aug 31 00:20:39 lt001 systemd-logind[4802]: Failed to add match for NameOwnerChanged: Connection timed out
Aug 31 00:20:39 lt001 systemd-logind[4802]: Failed to fully start up daemon: Connection timed out
Aug 31 00:20:39 lt001 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Aug 31 00:20:39 lt001 systemd[1]: Failed to start Login Service.
Aug 31 00:20:39 lt001 systemd[1]: Unit systemd-logind.service entered failed state.
...
Aug 31 00:21:20 lt001 systemd[1]: Failed to start GNOME Display Manager.
Aug 31 00:21:20 lt001 systemd[1]: Unit gdm.service entered failed state.
...
Aug 31 00:22:00 lt001 systemd[1]: Failed to start Bluetooth service.
Aug 31 00:22:00 lt001 systemd[1]: Unit bluetooth.service entered failed state.
...
Aug 31 00:22:00 lt001 systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Aug 31 00:22:00 lt001 systemd[1]: Unit avahi-daemon.service entered failed state.
...
Aug 31 00:22:00 lt001 systemd[1]: Failed to start Network Manager.
Aug 31 00:22:00 lt001 systemd[1]: Unit NetworkManager.service entered failed state.
...
Aug 31 00:22:15 lt001 systemd[1]: dhcpd4.service: main process exited, code=exited, status=1/FAILURE
Aug 31 00:22:15 lt001 systemd[1]: Unit dhcpd4.service entered failed state.
...
|
Many times I get this line too :
| Code: |
nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't contact LDAP server
|
I'm not sure that ldap problem is the root cause.
The kernel config match systemd wiki page.
What might be wrong in the system config that make systemd service not work at boot?
_________________
ruddy32
Last edited by ruddy32 on Tue Sep 02, 2014 8:37 am; edited 1 time in total |
|
| Back to top |
|
 |
luna80
Veteran
Joined: 01 Feb 2004
Posts: 1546
Location: switzerland
|
| Posted: Mon Sep 01, 2014 12:16 pm Post subject: |
|
|
try to look here
there is a similar error
_________________
*** !f j00 c4n r34D tH15 tH3N j00 n33D t0 l0g Off *** |
|
| Back to top |
|
|
ruddy32
n00b
Joined: 07 May 2014
Posts: 40
Location: France
|
| Posted: Mon Sep 01, 2014 2:42 pm Post subject: |
|
|
I have this message in systemd journal :
| Code: |
...
dbus_bus_get_private(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or th
e network connection was broken.
...
<error> [1409564807.614997] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (44) Error initializing authority: Erreur lors de l'envoi de l'identification : Erreur d'envoi de message : Relais brisé (pipe)
...
|
It might be a problem with policykit configuration.
_________________
ruddy32 |
|
| Back to top |
|
|
ruddy32
n00b
Joined: 07 May 2014
Posts: 40
Location: France
|
| Posted: Tue Sep 02, 2014 8:35 am Post subject: |
|
|
Finally, I remove ldap from /etc/nsswitch.conf and all works fine.
PS: slapd.service was not enabled
_________________
ruddy32 |
|
| Back to top |
|
|
|
Installing Gentoo
