-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/09/2009 01:30 AM, David O'Brien wrote:
David O'Brien wrote:
> I've been playing around with having domains and services configured and
> not, just to see how sssd behaves. What does this mean? Is it indicative
> of something specific that I should be including in the doc?
>
> [root@alice ~]# sssd -d4
> [sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
I just found the "Please disregard the "Unable to register control with
rootdse!" messages, as they are erroneous." message on the SSSD Test Day
page. Seems I should dig a bit deeper before I put my hand up :-S
>
> sssd requires both at least one configured domain and one service before
> it will start. That is, using the local SSSD domain database provider
> you still need either NSS or PAM enabled before sssd will even start.
> (This may fall under the heading of "well, d'uh", but I'm just a
> beginner ;) )
>
> thanks a lot
David, they're an internal informational message from one of our
dependency libraries. Originally they were showing up at debug level 0,
which looked like a serious error. We later trapped them and restricted
them to debug level 4, to indicate that they're informational rather
than an error.
In general, our serious errors will always be reported at debug level 0
(i.e. even if you have no other debug messages enabled) and additional
information on these errors is usually carried in debug level 1
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAkr4DI0ACgkQeiVVYja6o6P3UgCfTB8oZotq9yvE3dad032QgkWz
PtcAn33j9t3okhk+CQ6vLxWp/W/ajiea
=yaWU
-----END PGP SIGNATURE-----