| Summary: | sssd failes to start after update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Torsten <tnielsen> | ||||
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | abokovoy, jhrozek, lslebodn, mzidek, pbrezina, preichl, rharwood, sbose, ssorce | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | sssd-1.14.2-2.fc23 sssd-1.14.2-2.fc25 sssd-1.14.2-2.fc24 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-12-17 00:23:41 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Torsten
2016-11-08 13:19:19 UTC
journalctl output is not useful by default for sssd. Please follow https://fedorahosted.org/sssd/wiki/Troubleshooting Increased the debug level and restarted sssd. Looking through the /var/log/sssd/sssd.log There seemed to be a line for each AD user (a lot!) I also noticed some mention of DB, so I went ahead and deleted the cache-files under /var/lib/sss/db This seemed to do the trick sssd could now start - and after a reboot, I could login. Maybe You can close this one, but I don't think a system upgrade should make sssd fail to restart. From /var/log/sssd/sssd.log (after failed restart of sssd) ---- (Tue Nov 8 14:48:53 2016) [sssd] [server_setup] (0x0400): CONFDB: /var/lib/sss/db/config.ldb (Tue Nov 8 14:48:53 2016) [sssd] [sss_names_init_from_args] (0x0100): Using re [(((?P<domain>[^\\]+)\\(?P<name>.+$))|((?P<name>[^@]+)@(?P<domain>.+$))|(^(?P<name>[^@\\]+)$))]. (Tue Nov 8 14:48:53 2016) [sssd] [sss_fqnames_init] (0x0100): Using fq format [%1$s@%2$s]. (Tue Nov 8 14:48:53 2016) [sssd] [sysdb_domain_init_internal] (0x0200): DB File for uni.au.dk: /var/lib/sss/db/cache_uni.au.dk.ldb (Tue Nov 8 14:48:53 2016) [sssd] [sysdb_domain_init_internal] (0x0200): Timestamp file for uni.au.dk: /var/lib/sss/db/timestamps_uni.au.dk.ldb (Tue Nov 8 14:48:53 2016) [sssd] [ldb] (0x0400): asq: Unable to register control with rootdse! (Tue Nov 8 14:48:53 2016) [sssd] [sysdb_domain_cache_upgrade] (0x0100): Upgrading DB [uni.au.dk] from version: 0.17 (Tue Nov 8 14:48:53 2016) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.18 It's difficult to say from log file but it could be a duplicate of upstream bug. https://fedorahosted.org/sssd/ticket/3232 How big files were in /var/lib/sss/db/ ? The original files, I don't know - they are gone. This is what I have now: # ls -lht /var/lib/sss/db/ total 31M -rw-------. 1 root root 3,5K Nov 8 18:05 ccache_UNI.AU.DK -rw-------. 1 root root 27M Nov 8 18:05 cache_uni.au.dk.ldb -rw-------. 1 root root 1,6M Nov 8 18:05 timestamps_uni.au.dk.ldb -rw-------. 1 root root 1,3M Nov 8 17:49 config.ldb -rw-------. 1 root root 1,3M Nov 8 14:59 sssd.ldb (In reply to Torsten from comment #4) > The original files, I don't know - they are gone. > > This is what I have now: > # ls -lht /var/lib/sss/db/ > total 31M > -rw-------. 1 root root 3,5K Nov 8 18:05 ccache_UNI.AU.DK > -rw-------. 1 root root 27M Nov 8 18:05 cache_uni.au.dk.ldb It could take some time to upgrade 27 MiB cache. I can confirm you hit upstream bug https://fedorahosted.org/sssd/ticket/3232 I am so sorry for inconveniences. The bug is fixed in upstream. and you already found a workaround. rm -f /var/lib/sss/db/cache_* Upstream ticket: https://fedorahosted.org/sssd/ticket/3232 sssd-1.14.2-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-66bc868b6e sssd-1.14.2-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b04d690b49 sssd-1.14.2-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b0d27da617 sssd-1.14.2-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b0d27da617 sssd-1.14.2-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b04d690b49 sssd-1.14.2-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-66bc868b6e sssd-1.14.2-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. sssd-1.14.2-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. sssd-1.14.2-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. |