You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/27
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!
Comments
Comment from sgallagh at 2009-04-29 14:26:39
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
Comment from simo at 2009-04-30 15:33:59
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
Comment from jhrozek at 2009-05-10 22:09:05
Resolved in r4146c660af61cca7f3c4bcd89d810de1d34bae0a
resolution: => fixed
status: new => closed
Comment from dpal at 2012-01-19 02:22:23
Fields changed
rhbz: => 0
Comment from zmraz at 2017-02-24 14:33:33
Metadata Update from @zmraz:
The text was updated successfully, but these errors were encountered: