Learn more about these different git repos.
Other Git URLs
If there is bad configuration file present (I had there some html content), while trying to start sssd, the bad database files are created and sssd is not started. When I change the conf file, sssd cannot start because of the bad db files. Why they are even created, when 1, there is bad conf file, 2, the sssd process does not even start.
The workaround can be to delete the bad created db files and start sssd with correct conf file again.
Assigning this to myself. I thought I prevented this from happening.
owner: somebody => sgallagh priority: major => critical status: new => assigned
zmraz please attach your corrupted config file (and maybe the config.ldb that is generated) so that we can reproduce the issue
Corrupted sssd.conf sssd.conf
Bad database file config.ldb
And I got this error after with correct sssd.conf (provided for testday)
[root@becks sssd]# service sssd start server_sort:Unable to register control with rootdse! [ OK ] [sssd] [confdb_create_base] (0): Failed to initialize DB (68,[Entry @ATTRIBUTES already exists]), aborting!
I have been able to reproduce the error. I will look into this immediately.
Fixed in commit [a3d6555]
resolution: => fixed status: assigned => closed
Fields changed
rhbz: => 0
Metadata Update from @zmraz: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.0
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/1071
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.