So, I've started testing upgrading EL 8.0 to 8.1, in my case with Oracle Linux 8.
I spotted 2 issues during/after upgrade, both seem related to sssd. The first is that during the upgrade, sssd is updated and therefore restarted, but sssd fails to restart successfully. Nov 15 22:33:31 devzitsol8 systemd[1]: Stopping System Security Services Daemon... Nov 15 22:33:31 devzitsol8 sssd[nss][11571]: Shutting down Nov 15 22:33:31 devzitsol8 sssd[autofs][11574]: Shutting down Nov 15 22:33:31 devzitsol8 sssd[be[AD]][11570]: Shutting down Nov 15 22:33:31 devzitsol8 sssd[sudo][11573]: Shutting down Nov 15 22:33:31 devzitsol8 sssd[pam][11572]: Shutting down Nov 15 22:33:31 devzitsol8 sssd[be[implicit_files]][11569]: Shutting down Nov 15 22:33:31 devzitsol8 systemd[1]: Stopped System Security Services Daemon. Nov 15 22:33:31 devzitsol8 systemd[1]: Starting System Security Services Daemon... Nov 15 22:33:31 devzitsol8 sssd[33205]: Starting up Nov 15 22:33:31 devzitsol8 sssd[be[AD]][33207]: Starting up Nov 15 22:33:31 devzitsol8 sssd[be[implicit_files]][33206]: Starting up Nov 15 22:33:31 devzitsol8 sssd[be[AD]][33208]: Starting up Nov 15 22:33:33 devzitsol8 sssd[be[AD]][33209]: Starting up Nov 15 22:33:36 devzitsol8 sssd[nss][33211]: Starting up Nov 15 22:33:36 devzitsol8 sssd[autofs][33214]: Starting up Nov 15 22:33:36 devzitsol8 sssd[sudo][33213]: Starting up Nov 15 22:33:36 devzitsol8 sssd[pam][33212]: Starting up Nov 15 22:33:36 devzitsol8 sssd[nss][33215]: Starting up Nov 15 22:33:36 devzitsol8 sssd[autofs][33216]: Starting up Nov 15 22:33:36 devzitsol8 sssd[sudo][33217]: Starting up Nov 15 22:33:36 devzitsol8 sssd[pam][33218]: Starting up Nov 15 22:33:37 devzitsol8 sssd[be[AD]][33219]: Starting up Nov 15 22:33:37 devzitsol8 sssd[33205]: Exiting the SSSD. Could not restart critical service [AD]. Nov 15 22:33:37 devzitsol8 sssd[be[implicit_files]][33206]: Shutting down Nov 15 22:33:37 devzitsol8 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE Nov 15 22:33:37 devzitsol8 systemd[1]: sssd.service: Failed with result 'exit-code'. Nov 15 22:33:37 devzitsol8 systemd[1]: Failed to start System Security Services Daemon. This appears to be due to this: (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [be_res_get_opts] (0x0100): Lookup order: ipv4_first (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [recreate_ares_channel] (0x0100): Initializing new c-ares channel (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [sss_names_init_from_args] (0x0100): Using re [(((?P<domain>[^\\]+)\\(?P<name>.+$))|((?P<name>[^@]+)@(?P<domain>.+$))|(^(?P<name>[^@\\]+)$))]. (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [sss_fqnames_init] (0x0100): Using fq format [%1$s@%2$s]. (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [sbus_signal_handler] (0x0020): We do not listen to this signal! (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [sbus_signal_handler] (0x0020): We do not listen to this signal! (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [id] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [auth] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [access] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [chpass] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [sudo] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [autofs] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [selinux] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [hostid] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [subdomains] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_configuration] (0x0100): Using [ad] provider for [session] (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_module_open_lib] (0x0010): Unable to load module [ad] with path [/usr/lib64/sssd/libsss_ad.so]: libwbclient.so.0: cannot open shared object file: No such file or directory (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_module] (0x0020): Unable to create DP module. (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_target_init] (0x0010): Unable to load module ad (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_load_targets] (0x0020): Unable to load target [id] [80]: Accessing a corrupted shared library. (Fri Nov 15 22:33:37 2019) [sssd[be[AD]]] [dp_init_done] (0x0020): Unable to initialize DP targets [1432158209]: Internal Error After the 8.1 update completed though, I could happily start sssd. The second issue is more subtle, and comes due to our use of the autofs provider, using Active Directory for the map location. On bootup autofs takes a long time to start, which means that autofs-provided mounts are unavailable when the system first boots. This looks a lot like this Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1648521 Nov 16 10:27:46 devzitsol8 oddjob-mkhomedir[1513]: error creating /nethome: Permission denied Nov 16 10:29:04 devzitsol8 automount[1124]: lookup_read_master: lookup(sss): getautomntent_r: Invalid argument Nov 16 10:29:04 devzitsol8 automount[1124]: lookup(file): failed to read included master map auto.master Nov 16 10:29:04 devzitsol8 automount[1124]: lookup(file): failed to read included master map auto.master Nov 16 10:29:04 devzitsol8 automount[1124]: mounted indirect on /misc with timeout 300, freq 75 seconds Nov 16 10:29:04 devzitsol8 automount[1124]: mounted indirect on /net with timeout 300, freq 75 seconds Nov 16 10:29:04 devzitsol8 automount[1124]: mounted indirect on /nethome with timeout 300, freq 75 seconds Nov 16 10:29:04 devzitsol8 systemd[1]: Started Automounts filesystems on demand. Nov 16 10:29:04 devzitsol8 systemd[1]: Reached target Multi-User System. Nov 16 10:29:04 devzitsol8 systemd[1]: Starting Update UTMP about System Runlevel Changes... Nov 16 10:29:04 devzitsol8 systemd[1]: Started Update UTMP about System Runlevel Changes. Nov 16 10:29:04 devzitsol8 systemd[1]: Startup finished in 1.207s (kernel) + 5.624s (initrd) + 1min 37.318s (userspace) = 1min 44.150s. Nov 16 10:30:18 devzitsol8 systemd[1503]: Starting Mark boot as successful... Happy to provide more logs if it helps diagnose these issues. Cheers, John -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org
