#3287 Lots of The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported] messages
Closed: Fixed 6 years ago Opened 7 years ago by orion.

I'm starting to enable logging of critical failures for sssd (see also https://bugzilla.redhat.com/show_bug.cgi?id=1416150). However I'm getting a lot of these messages:

Jan 24 13:24:18 mail sssd_nss: The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]

It appears to happen around lookups of system users, but perhaps not always:

(Tue Jan 24 13:40:24 2017) [sssd[nss]] [nss_cmd_initgroups_search] (0x0080): No matching domain found for [postfix], fail!
(Tue Jan 24 13:40:24 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
(Tue Jan 24 13:40:36 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
(Tue Jan 24 13:41:06 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]
(Tue Jan 24 13:41:21 2017) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported]

I do have:

[nss]
filter_users = root,apache,dovecot,mailman,postfix,aliascp,ijrs-porsec,porsec
filter_groups = root,apache,dovecot,mailman,postfix,aliascp,ijrs-porsec,porsec
filter_users_in_groups = false

Running sssd-1.14.0-43.el7_3.11.x86_64


Also seems to be paired with:

Jan 24 13:53:54 mail sssd_be: Target [subdomains] is not initialized

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.3

Fields changed

rhbz: => 0

Metadata Update from @orion:
- Issue set to the milestone: SSSD 1.14.3

7 years ago

This just means that the operation (get subdomains in this case) is not supported in the selected provider. It is not an error per se, just an information.

Metadata Update from @pbrezina:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None

6 years ago

And so I would argue should not be reported at the level that it currently is (in case that wasn't clear).

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

6 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

6 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

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/4320

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata