Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debud/errror messages on console #1069

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Debud/errror messages on console #1069

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/27

  • Created at 2009-04-29 14:19:02 by zmraz
  • Closed as Fixed
  • Assigned to jhrozek

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:

  • Issue assigned to jhrozek
  • Issue set to the milestone: SSSD 1.0
@sssd-bot sssd-bot added the Closed: Fixed Issue was closed as fixed. label May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants