Ubuntu Server 16.04 SSSD Not Loading [closed]
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
I am attempting to authenticate my Ubuntu 16.04 server to an AD but having trouble loading SSSD. My sssd.conf file looks like this:
[sssd] services = nss, pam config_file_version = 2 domains = MYDOMAIN.LOCAL id_provider = ad access_provider = ad override_homedir = /home/%d/%u It is owned by root:root and file permission is set to 600. When attempting to start SSSD, systemctl reports the following:
● sssd.service - System Security Services Daemon Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2016-06-03 08:06:46 EDT; 9s ago Process: 6979 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=4) Jun 03 08:06:46 tempsvr systemd[1]: Starting System Security Services Daemon. Jun 03 08:06:46 tempsvr sssd[6979]: SSSD couldn't load the configuration database [2]: No such file or directory. Jun 03 08:06:46 tempsvr systemd[1]: sssd.service: Control process exited, code=exited status=4 Jun 03 08:06:46 tempsvr systemd[1]: Failed to start System Security Services Daemon. Jun 03 08:06:46 tempsvr systemd[1]: sssd.service: Unit entered failed state. Jun 03 08:06:46 tempsvr systemd[1]: sssd.service: Failed with result 'exit-code'. Не разворачивается ALDPro
Бьюсь 2 неделю. Не разворачивается. Подскажите п-та в чем ошибки.
root@sage:~# astra-modeswitch get
2
root@sage:~# cat /etc/apt/sources.list
# Astra Linux repository description https://wiki.astralinux.ru/x/0oLiC
root@sage:~# cat /etc/apt/preferences.d/aldpro
Package: *
Pin: release n=generic
Pin-Priority: 900
root@sage:~# cat /etc/hostname
sage.610.local
root@sage:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
127.0.1.1 sage
192.168.0.134 sage.610.local sage
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
root@sage:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND — YOUR CHANGES WILL BE OVERWRITTEN
nameserver 1.1.1.1
nameserver 192.168.0.134
nameserver 127.0.0.1
search 610.local
# The loopback network interface
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.134
netmask 255.255.255.0
gateway 192.168.0.123
dns-nameservers 1.1.1.1
dns-nameservers 192.168.0.134
dns-nameservers 127.0.0.1
dns-search 610.local
При установке aldpro-mp ошибки:
Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service.
Job for krb5-kdc.service failed because the control process exited with error code.
See «systemctl status krb5-kdc.service» and «journalctl -xe» for details.
invoke-rc.d: initscript krb5-kdc, action «start» failed.
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service masked)
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
sssd-autofs.service is a disabled or a static unit, not starting it.
sssd-nss.service is a disabled or a static unit, not starting it.
sssd-pam.service is a disabled or a static unit, not starting it.
sssd-ssh.service is a disabled or a static unit, not starting it.
sssd-sudo.service is a disabled or a static unit, not starting it.
A dependency job for sssd-ssh.socket failed. See ‘journalctl -xe’ for details.
A dependency job for sssd-nss.socket failed. See ‘journalctl -xe’ for details.
A dependency job for sssd-autofs.socket failed. See ‘journalctl -xe’ for details.
A dependency job for sssd-sudo.socket failed. See ‘journalctl -xe’ for details.
A dependency job for sssd-pam.socket failed. See ‘journalctl -xe’ for details.
A dependency job for sssd-pam-priv.socket failed. See ‘journalctl -xe’ for details.
Job for sssd.service failed because the control process exited with error code.
See «systemctl status sssd.service» and «journalctl -xe» for details.
invoke-rc.d: initscript sssd, action «start» failed.
● sssd.service — System Security Services Daemon
Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2022-07-26 14:03:48 MSK; 18ms ago
Process: 10905 ExecStart=/usr/sbin/sssd -i $ (code=exited, status=4)
Main PID: 10905 (code=exited, status=4)
. because /etc/sssd/sssd.conf is not available yet
LINUX: sssd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
[root@testbox ~]# systemctl start sssd.service
Job for sssd.service failed because the control process exited with error code. See “systemctl status sssd.service” and “journalctl -xe” for details.
[root@testbox ~]#
[root@testbox ~]# systemctl status sssd.service
â sssd.service – System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/sssd.service.d
ââjournal.conf
Active: failed (Result: exit-code) since Sun 2018-04-08 20:54:14 UTC; 4s ago
Process: 77009 ExecStart=/usr/sbin/sssd -i -f (code=exited, status=2)
Main PID: 77009 (code=exited, status=2)
Apr 08 20:54:14 testbox systemd[1]: Starting System Security Services Daemon…
Apr 08 20:54:14 testbox sssd[77009]: SSSD is already running
Apr 08 20:54:14 testbox systemd[1]: sssd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 20:54:14 testbox systemd[1]: Failed to start System Security Services Daemon.
Apr 08 20:54:14 testbox systemd[1]: Unit sssd.service entered failed state.
Apr 08 20:54:14 testbox systemd[1]: sssd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@testbox ~]#
Output of /var/log/sssd/sssd.log
(Sun Apr 8 20:54:41:430809 2018) [sssd] [main] (0x0010): pidfile exists at /var/run/sssd.pid
1) Take a duplicate session and look at /var/log/sssd/sssd.log while starting the sssd
# tail -f /var/log/sssd/sssd.log
2) If you see “pidfile exists at /var/run/sssd.pid” then remove the file
# rm /var/run/sssd.pid
3) Try to start the sssd service and check status as well
# systemctl start sssd.service
# systemctl status sssd.service
Having SSSD problems at boot since upgrading to 20.10 [duplicate]
As the journalctl file is about 8000 lines I only post the lines that signal the start of the sssd problems. If more info is needed please tell me.
Nov 05 20:44:30 loosken sssd[1031]: SSSD couldn't load the configuration database [2]: No such file or directory. Nov 05 20:44:30 loosken systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION Nov 05 20:44:30 loosken systemd[1]: sssd.service: Failed with result 'exit-code'. Nov 05 20:44:30 loosken systemd[1]: Failed to start System Security Services Daemon. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder private socket. Nov 05 20:44:30 loosken snapd[1030]: AppArmor status: apparmor is enabled and all features are available Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD NSS Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD SSH Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD Sudo Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD AutoFS Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAC Service responder socket. Nov 05 20:44:30 loosken systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Nov 05 20:44:30 loosken dbus-daemon[995]: [system] AppArmor D-Bus mediation is enabled