Hey,
I'm getting this message pretty often...
(Thu Jan 26 21:23:03 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
I get it in pam and nss services...could someone suggest which log level I should enable to figure out what the actual message is that sssd doesn't like? Best I can tell, these really started to show up after we updated to Centos 7.3 but the logs have rolled off so I can't say that definitively. It appears that users aren't necessarily being impacted but I don't like mysteries in my logs.
thanks
=G=
Note: I've tried bumping to 0x1010.
?
On Thu, Jan 26, 2017 at 09:32:04PM +0000, Galen Johnson wrote:
Hey,
I'm getting this message pretty often...
(Thu Jan 26 21:23:03 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
You can ignore these messages. They are a bit too loud by accident: https://fedorahosted.org/sssd/ticket/3287
I get it in pam and nss services...could someone suggest which log level I should enable to figure out what the actual message is that sssd doesn't like? Best I can tell, these really started to show up after we updated to Centos 7.3 but the logs have rolled off so I can't say that definitively. It appears that users aren't necessarily being impacted but I don't like mysteries in my logs.
The PAM and NSS responders periodically ask the sssd_be process about a list of autodiscovered "subdomains". I assume you are using id_provider=ldap that doesn't support subdomains, so the sssd_be's ldap id_provider replies with NotSupported.
I am indeed using id_provider=ldap. Thanks for the info. Reading through the linked issues, there appears to be no way to "turn them off" currently. Is that true or will we need to wait for an update? On a busy system, this pumps up the logs quite a bit.
thanks
=G=
________________________________________ From: Jakub Hrozek jhrozek@redhat.com Sent: Friday, January 27, 2017 4:30 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: sssd error message help
On Thu, Jan 26, 2017 at 09:32:04PM +0000, Galen Johnson wrote:
Hey,
I'm getting this message pretty often...
(Thu Jan 26 21:23:03 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
You can ignore these messages. They are a bit too loud by accident: https://fedorahosted.org/sssd/ticket/3287
I get it in pam and nss services...could someone suggest which log level I should enable to figure out what the actual message is that sssd doesn't like? Best I can tell, these really started to show up after we updated to Centos 7.3 but the logs have rolled off so I can't say that definitively. It appears that users aren't necessarily being impacted but I don't like mysteries in my logs.
The PAM and NSS responders periodically ask the sssd_be process about a list of autodiscovered "subdomains". I assume you are using id_provider=ldap that doesn't support subdomains, so the sssd_be's ldap id_provider replies with NotSupported. _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
On Fri, Jan 27, 2017 at 02:20:39PM +0000, Galen Johnson wrote:
I am indeed using id_provider=ldap. Thanks for the info. Reading through the linked issues, there appears to be no way to "turn them off" currently. Is that true or will we need to wait for an update? On a busy system, this pumps up the logs quite a bit.
I'm sorry, but this log level needs to be changed in the code. The only workaround I can think of (untested though) is to set debug_level to 0x0000 explicitly.
That's fine. I can wait for the fix. Good enough for now to know that it's innocuous in our setup.
=G=
________________________________________ From: Jakub Hrozek jhrozek@redhat.com Sent: Friday, January 27, 2017 12:01 PM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: sssd error message help
On Fri, Jan 27, 2017 at 02:20:39PM +0000, Galen Johnson wrote:
I am indeed using id_provider=ldap. Thanks for the info. Reading through the linked issues, there appears to be no way to "turn them off" currently. Is that true or will we need to wait for an update? On a busy system, this pumps up the logs quite a bit.
I'm sorry, but this log level needs to be changed in the code. The only workaround I can think of (untested though) is to set debug_level to 0x0000 explicitly. _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users@lists.fedorahosted.org