#3287 Lots of The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.NotSupported] messages

Created 8 months ago by orion
Modified 4 months ago

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

See also ticket #3278

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.3

Fields changed

rhbz: => 0

7 months ago

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

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.

5 months ago

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

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

  • master: e98d085b529e0ae5e07a717ce3b30f3943be0ee0
4 months 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)

  • sssd-1-14: 82a62c650243283d2e8a5177e0f9f35ef1b3478c
4 months 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)

4 months 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)

Login to comment on this ticket.

defect

SSSD

1.14.0

false

false

0

false

false

false

false

cancel