SSSD / sssd

#3278 Target [subdomains] is not initialized log spam
Closed: Fixed Opened by orion.

Closed: Fixed
Reopen Issue

Running sssd-1.14.0-43.el7_3.4.x86_64, I get lots of these messages in the domain log:

(Tue Jan 17 10:51:06 2017) [sssd[be[default]]] [dp_find_method] (0x0020): Target [subdomains] is not initialized
(Tue Jan 17 10:51:14 2017) [sssd[be[default]]] [dp_find_method] (0x0020): Target [subdomains] is not initialized
(Tue Jan 17 10:51:31 2017) [sssd[be[default]]] [dp_find_method] (0x0020): Target [subdomains] is not initialized
(Tue Jan 17 10:51:31 2017) [sssd[be[default]]] [dp_find_method] (0x0020): Target [subdomains] is not initialized
(Tue Jan 17 10:51:44 2017) [sssd[be[default]]] [dp_find_method] (0x0020): Target [subdomains] is not initialized

I'm using sssd with ldap, and I suspect the subdomains target is just not relevant for it. I see messages like:

(Tue Jan 17 10:48:54 2017) [sssd[be[default]]] [dp_target_init] (0x0020): Target [selinux] is not supported by module [ldap].
(Tue Jan 17 10:48:54 2017) [sssd[be[default]]] [dp_target_init] (0x0020): Target [hostid] is not supported by module [ldap].

but those do not appear to repeat after startup

I agree the log level should be decreased, I suggest SSSDBG_CONF_SETTINGS.

I also tried to get rid of it with:

subdomains_provider = none

but that does not appear to help.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.16

Fields changed

rhbz: => 0

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

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.16)

Metadata Update from @jstephen:
- Issue assigned to jstephen
  • master: e98d085b529e0ae5e07a717ce3b30f3943be0ee0

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

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)

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 set to the milestone: SSSD 1.14.3 (was: SSSD 1.15.4)
- Issue status updated to: Closed (was: Open)

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

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.
Metadata
None
None
None
Highest
false
false
false
defect
SSSD
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.