SSSD / sssd

#2498 "debug_timestamps = false" and "debug_microseconds = true" do not work after enabling journald with sssd.
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1163742

Description of problem:
"debug_timestamps = false" and "debug_microseconds = true" do not affect after
enabling journald with sssd.
Version-Release number of selected component (if applicable):
sssd-1.12.2-12.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Enable journald for sssd debug logging
2. Add "debug_timestamps = false" in sssd section and "debug_microseconds =
true" in nss section of sssd.conf file.
3. From "journalctl -f" output
----------------------------------------
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a32260
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service LDAP
replied to ping
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: 0x7fc1b5a32a90
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a359e0
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service pam
replied to ping
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: 0x7fc1b5a353d0
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a33920
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service nss
replied to ping
----------------------------------------
From "journalctl -f" output
---------------------------------------------
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Added timed
event "ltdb_timeout": 0x7f84e95b3d00
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Running
timer event 0x7f84e95bf960 "ltdb_callback"
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Destroying
timer event 0x7f84e95b3d00 "ltdb_timeout"
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Ending
timer event 0x7f84e95bf960 "ltdb_callback"
---------------------------------------------
Actual results:
From "journalctl -f" output
----------------------------------------
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a32260
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service LDAP
replied to ping
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: 0x7fc1b5a32a90
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a359e0
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service pam
replied to ping
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: 0x7fc1b5a353d0
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: dbus conn:
0x7fc1b5a33920
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Dispatching.
Nov 13 17:11:01 dhcp207-182.lab.eng.pnq.redhat.com sssd[12980]: Service nss
replied to ping
----------------------------------------
From "journalctl -f" output
---------------------------------------------
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Added timed
event "ltdb_timeout": 0x7f84e95b3d00
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Running
timer event 0x7f84e95bf960 "ltdb_callback"
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Destroying
timer event 0x7f84e95b3d00 "ltdb_timeout"
Nov 13 17:10:52 dhcp207-182.lab.eng.pnq.redhat.com sssd_nss[12982]: Ending
timer event 0x7f84e95bf960 "ltdb_callback"
---------------------------------------------
like both options do not affect
Expected results:
"debug_timestamps = false" and "debug_microseconds = true"
Additional info:
Disabling journald for sssd logging and everything works fine.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.12.3
owner: somebody => mzidek
patch: 0 => 1
review: True => 0
selected: =>
testsupdated: => 0
  • master: cbbe63ded9d628ffb2494132ca1e5ebe90e2d5f8

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue marked as depending on: #2671
- Issue set to the milestone: SSSD 1.12.3

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

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
Normal
defect
SSSD
None
None
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=1163742
0
0
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.