Learn more about these different git repos.
Other Git URLs
After every startup, sssd_nss segfaults, but reconnects and works fine after that because it starts before sssd_dp:
[sssd[nss]] [sbus_add_connection] (5): Adding connection 1DC0EB0 [sssd[nss]] [sbus_add_conn_watch] (5): 1DC1280: 11, 2=WRITE [sssd[nss]] [sbus_new_connection] (1): Failed to open connection: name=org.freedesktop.DBus.Error.NoServer, message=Failed to connect to socket /var/lib/sss/pipes/private/sbus-dp: Connection refused [sssd[nss]] [sss_dp_conn_reconnect] (4): Failed to reconnect [5(Input/output error)]! [sssd[nss]] [sss_dp_conn_reconnect] (4): Retrying in 5 seconds
And after that:
[sssd[dp]] [sbus_new_server] (3): D-BUS Server listening on unix:path=/var/lib/sss/pipes/private/sbus-dp,guid=1bacb1008d25b3137903500a49eef2e7
I haven't been able to get a backtrace so far because I haven't been able to reproduce the race condition in gdb.
Is it a good idea to start the Data Provider service first, wait for the startup and then queue the other services asynchronously as we do now?
The other part of fix would of course be don't segfault NSS when reconnecting.
Fields changed
owner: somebody => sgallagh status: new => assigned version: 0.3.1 => 0.3.2
Fixed by commit [f7e3265]
resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @jhrozek: - Issue assigned to sgallagh
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1066
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.