Learn more about these different git repos.
Other Git URLs
After first start of sssd I got ok and 0 exit code, but then appears lots of debug/error messages on concole. Shouldn't them be on the error log and thus init script end with fail?
[sssd] [add_new_provider] (0): Could not get provider configuration for [LOCAL] server_sort:Unable to register control with rootdse! server_sort:Unable to register control with rootdse! server_sort:Unable to register control with rootdse! server_sort:Unable to register control with rootdse! asq: Unable to register control with rootdse! asq: Unable to register control with rootdse! asq: Unable to register control with rootdse! server_sort:Unable to register control with rootdse! asq: Unable to register control with rootdse! server_sort:Unable to register control with rootdse! asq: Unable to register control with rootdse!
These are erroneous error messages generated by libldb, one of our dependencies. They are not indicative of any failure in the SSSD, as we are not using the features they warn about.
Leaving this ticket open to find a way to suppress displaying these erroneous messages, but lowering the priority.
owner: somebody => simo priority: major => minor
I think we should address this in the initscripts for now and redirect stderr to a log file or to /dev/null Once we will integrate the Event Logging API we will have means to redirect stuff by changing the configuration.
Reassigning to Jakub that is already working in the init scripts area.
owner: simo => jhrozek
Resolved in r4146c660af61cca7f3c4bcd89d810de1d34bae0a
resolution: => fixed status: new => closed
Fields changed
rhbz: => 0
Metadata Update from @zmraz: - Issue assigned to jhrozek - 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/1069
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.