Am Wed, Jun 14, 2023 at 03:45:53PM +0200 schrieb Adam Cecile: > On 6/14/23 15:42, Striker Leggette wrote: > > On 6/14/23 09:35, Adam Cecile wrote: > > > (2023-06-14 15:21:20): [pac] [sbus_dbus_request_name] (0x0020): > > > Unable to > > > request name on the system bus [3] > > This seems to be where things break. Can you confirm DBus on this system > > is running properly? Check: > > > > # systemctl status dbus.service > > # dbus-monitor
Hi, SSSD is not using the system DBus service but implements it's own. Can you check if the other SSSD processes, especially the backend process sssd_be, are running when you are trying to start the PAC responder? Please note the we currently recommend to start the PAC responder together with the other SSSD components by adding 'pac' to the 'service' line in sssd.conf. It looks like the line is empty in your sssd.conf, is there a reason for this, typically I would expect at least 'nss' and 'pam' in this line, see man sssd.conf for details. bye, Sumit > > > > Can we see your sssd.conf? > > Sure ! Here you go: > > server:~# systemctl status dbus.service > ● dbus.service - D-Bus System Message Bus > Loaded: loaded (/lib/systemd/system/dbus.service; static) > Active: active (running) since Wed 2023-06-14 15:20:32 CEST; 23min ago > TriggeredBy: ● dbus.socket > Docs: man:dbus-daemon(1) > Main PID: 757 (dbus-daemon) > Tasks: 1 (limit: 4604) > Memory: 2.2M > CPU: 274ms > CGroup: /system.slice/dbus.service > └─757 /usr/bin/dbus-daemon --system --address=systemd: --nofork > --nopidfile --systemd-activation --syslog-only > > Jun 14 15:20:31 server systemd[1]: Starting dbus.service - D-Bus System > Message Bus... > Jun 14 15:20:32 server systemd[1]: Started dbus.service - D-Bus System > Message Bus. > > > server:~# dbus-monitor > Failed to open connection to session bus: Unable to autolaunch a dbus-daemon > without a $DISPLAY for X11 > > > sssd.conf: > > [sssd] > domains = ad.domain.com > config_file_version = 2 > services = > > [domain/ad.domain.com] > ad_domain = ad.domain.com > ad_server = adsrv01.ad.domain.com, adsrv02.ad.domain.com, > adsrv03.ad.domain.com > krb5_realm = AD.DOMAIN.COM > realmd_tags = > cache_credentials = true > krb5_validate = false > id_provider = ad > krb5_store_password_if_offline = true > override_shell = /bin/bash > default_shell = /bin/bash > override_homedir = /home/%u > fallback_homedir = /home/%u > ldap_id_mapping = true > use_fully_qualified_names = false > access_provider = simple > simple_allow_groups = itadmin > ad_gpo_map_remote_interactive = > ldap_user_extra_attrs = altSecurityIdentities:altSecurityIdentities > ldap_user_ssh_public_key = altSecurityIdentities > chpass_provider = ad > pwd_expiration_warning = 21 > _______________________________________________ > sssd-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
