Tumbleweed - nslcd.service startet nicht

stob · 11. November 2025

Hallo liebe Community,

ich hoffe ich bin hier in der richtigen Untergruppe. Wenn nicht bitte ich um Entschuldigung und um Verschiebung in den richtigen Bereich,

Beim Starten des nslcd.service unter Tumbleweed kommt folgender Fehler:

Code

~ # systemctl status nslcd.service
× nslcd.service - Naming services LDAP client daemon.
     Loaded: loaded (/usr/lib/systemd/system/nslcd.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Mon 2025-11-10 12:49:10 CET; 20h ago
 Invocation: 4554a7ad7684401d96591473737c4c31
    Process: 1217 ExecStart=/usr/sbin/nslcd (code=exited, status=1/FAILURE)
        CPU: 36ms

Nov 10 12:49:10 wbbi167 systemd[1]: Starting Naming services LDAP client daemon....
Nov 10 12:49:10 wbbi167 nslcd[1234]: cannot create pid file (/var/run/nslcd/nslcd.pid): No such file or directory
Nov 10 12:49:10 wbbi167 nslcd[1217]: nslcd: wait_for_response(): read_response() returned 0 (expected 4)
Nov 10 12:49:10 wbbi167 nslcd[1217]: nslcd: unable to daemonize: No data available
Nov 10 12:49:10 wbbi167 systemd[1]: nslcd.service: Control process exited, code=exited, status=1/FAILURE
Nov 10 12:49:10 wbbi167 systemd[1]: nslcd.service: Failed with result 'exit-code'.
Nov 10 12:49:10 wbbi167 systemd[1]: Failed to start Naming services LDAP client daemon..

Alles anzeigen

Ich habe aus einem anderen Forum den Tipp versucht in die /usr/lib/systemd/system/nslcd.service

Code

[Service]
...
User=nslcd

einzufügen. Das hat den Fehler aber nicht verhindert.

Kann da jemand vielleicht weiterhelfen?

Schönen Gruß

stob

Sauerland · 11. November 2025

Was sagt:

Zitat von stob

ls -al /var/run/nslcd

stob · 14. November 2025

Code

 ls -al /var/run/nslcd
insgesamt 0
drwxr-xr-x.  2 nslcd nslcd   40 11. Nov 11:04 .
drwxr-xr-x. 46 root  root  1100 14. Nov 06:49 ..

ls -al /run
...
drwxr-xr-x.  2 nslcd  nslcd    40 11. Nov 11:04 nslcd
...

Sauerland · 14. November 2025

Zitat von stob

drwxr-xr-x. 2 nslcd nslcd 40 11. Nov 11:04 nslcd

Mal geändert in root:root

luigi · 14. November 2025

Falls Sauerlands Tipp nicht helfen sollte, schau mal in den folgenden Bug-report aus 10/2024:

#1085212 - nslcd.service doesn't start due to ProtectSystem=strict - Debian Bug report logs

Vielleicht wurde dieses Problem unter Tumbleweed noch nicht bereinigt.

Als work around hat damals das Setzen von

Code

ProtectSystem=full

oder

Code

ReadWritePaths=/run

geholfen.

stob · 24. November 2025

Zitat von luigi
Falls Sauerlands Tipp nicht helfen sollte, schau mal in den folgenden Bug-report aus 10/2024:
https://bugs-devel.debian.org/…bugreport.cgi?bug=1085212

Vielleicht wurde dieses Problem unter Tumbleweed noch nicht bereinigt.
Als work around hat damals das Setzen von
Code
ProtectSystem=full 
oder
Code
ReadWritePaths=/run
geholfen.
Alles anzeigen

Sauerland's Tipp mit chown root:root hat nur ein weiteres permission denied gebracht.

Ich geh mal davon aus, dass die Änderungen in /usr/lib/systemd/system/nslcd.service eingefügt werden sollen?

Sauerland · 24. November 2025

Also alles auf 0.

Kannst du mal als root:

Code

journalctl -f

und in einer 2. Konsole als root:

Code

systemctl start nslcd.service

Erscheint dann in der 1. Konsole irgendeine Ausgabe?

stob · 25. November 2025

Code

:/usr/lib/systemd/system # more nslcd.service
[Unit]
Description=Naming services LDAP client daemon.
After=syslog.target network.target named.service dirsrv.target slapd.service

[Service]
# added automatically, for details please see
# https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort
ProtectSystem=full
ProtectHome=true
PrivateDevices=true
ProtectHostname=true
ProtectClock=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=true
RestrictRealtime=true
# end of automatic additions
## ProtectSystem=full
## ReadWritePaths=/run
## ReadWritePaths=/runProtectSystem=strict
## User=nslcd
Type=forking
PIDFile=/run/nslcd/nslcd.pid
ExecStart=/usr/sbin/nslcd

[Install]
WantedBy=multi-user.target

Alles anzeigen

Code

journalctl -f
Nov 25 09:53:59 wbbi167 systemd[1467]: Reached target Basic System.
Nov 25 09:53:59 wbbi167 systemd[1467]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/root/.cache/kcrash-metadata/*.ini).
Nov 25 09:53:59 wbbi167 systemd[1467]: Reached target Main User Target.
Nov 25 09:53:59 wbbi167 systemd[1467]: Startup finished in 205ms.
Nov 25 09:53:59 wbbi167 systemd[1]: Started User Manager for UID 0.
Nov 25 09:53:59 wbbi167 systemd[1]: Started Session 3 of User root.
Nov 25 09:53:59 wbbi167 sshd-session[1463]: error: ssh_selinux_setup_pty: security_compute_relabel: Invalid argument
Nov 25 09:53:59 wbbi167 systemd[1]: Starting wtmpdb daemon...
Nov 25 09:53:59 wbbi167 systemd[1]: Started wtmpdb daemon.
Nov 25 09:53:59 wbbi167 sshd-session[1463]: logind: cannot set TTY(3, /dev/pts/0): Connection timed out
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Nov 25 09:54:02 wbbi167 systemd[1431]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.

Alles anzeigen

Code

Nov 25 09:58:19 wbbi167 systemd[1431]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
Nov 25 09:58:23 wbbi167 systemd[1]: Starting Naming services LDAP client daemon....
Nov 25 09:58:23 wbbi167 nslcd[1586]: cannot create pid file (/var/run/nslcd/nslcd.pid): Permission denied
Nov 25 09:58:23 wbbi167 nslcd[1584]: nslcd: wait_for_response(): read_response() returned 0 (expected 4)
Nov 25 09:58:23 wbbi167 nslcd[1584]: nslcd: unable to daemonize: No data available
Nov 25 09:58:23 wbbi167 systemd[1]: nslcd.service: Control process exited, code=exited, status=1/FAILURE
Nov 25 09:58:23 wbbi167 systemd[1]: nslcd.service: Failed with result 'exit-code'.
Nov 25 09:58:23 wbbi167 systemd[1]: Failed to start Naming services LDAP client daemon..
N

Code

ls -al /run
insgesamt 16
drwxr-xr-x. 46 root   root   1100 25. Nov 09:53 .
drwxr-xr-x. 18 root   root   4096 10. Nov 11:33 ..
...
drwxr-xr-x.  2 nslcd  nslcd    40 25. Nov 09:53 nslcd
...

luigi · 25. November 2025

Zitat von stob

Nov 25 09:53:59 wbbi167 sshd-session[1463]: error: ssh_selinux_setup_pty: security_compute_relabel: Invalid argument

Das deutet auf ein Problem mit selinux hin. Ich würde selinux mal testweise abschalten und dann den nslcd.service neu starten.

Das folgende Kommando setzt selinux temporär auf permissive.

Code

sudo setenforce 0

Vielleicht hilft aber auch schon

Code

sudo semanage permissive -a nslcd_t

stob · 26. November 2025

Zitat von luigi
...

Vielleicht hilft aber auch schon
Code
sudo semanage permissive -a nslcd_t

Das zweite hat schon geholfen. Danke!

Code

Nov 26 12:16:35 wbbi167 systemd[1]: Starting Naming services LDAP client daemon....
░░ Subject: A start job for unit nslcd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit nslcd.service has begun execution.
░░
░░ The job identifier is 2865.
Nov 26 12:16:35 wbbi167 nslcd[3292]: version 0.9.13 starting
Nov 26 12:16:35 wbbi167 nslcd[3292]: accepting connections
Nov 26 12:16:35 wbbi167 systemd[1]: Started Naming services LDAP client daemon..
░░ Subject: A start job for unit nslcd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit nslcd.service has finished successfully.
░░
░░ The job identifier is 2865.

Alles anzeigen

Ist das eine schnelle Lösung, oder könnte sowas fest in Tumbleweed eingebaut werden? Oder habe ich bei der Installation irgendwas verkehrt gemacht, das die selinux Probleme verursacht haben könnte?

Tumbleweed - nslcd.service startet nicht

Wlan langsam

Linux 7.3 veröffentlicht: Neue Rekorde bei der Beteiligung

Cairo-Dock Ersatz unter Plasma 6 Wayland

First Adobe, Now Autodesk? SolidCraft Wants to Replace Fusion

Tumbleweed-Update bricht ab

pit1958ffm

Wanderratte

k.113

aitexturegenerator

Giorgio68

Teilen