On 6/15/23 10:47, Sumit Bose wrote:
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
Hello,
Thanks a lot for your help, sssd_be is indeed running:
server# ps aux | grep sss
root 793 0.0 0.2 27416 11864 ? Ss Jun14 0:00
/usr/sbin/sssd -i --logger=files
root 973 0.0 0.6 117424 26508 ? S Jun14 0:05
/usr/libexec/sssd/sssd_be --domain
ad.domain.com --uid 0 --gid 0
--logger=files
root 1127 0.0 0.3 71508 15500 ? S Jun14 0:00
/usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --logger=files
root 1157 0.0 1.2 63724 48912 ? Ss Jun14 0:03
/usr/libexec/sssd/sssd_nss --logger=files --socket-activated
root 247030 0.1 0.3 28788 14100 ? Ss 11:06 0:00
/usr/libexec/sssd/sssd_ssh --logger=files --socket-activated
root 247037 0.2 0.3 31520 15244 ? Ss 11:06 0:00
/usr/libexec/sssd/sssd_pam --logger=files --socket-activated
No particular reasons for having "service" setting being empty, it seems
it always worked without so I probably never configured it.
Regards, Adam.