#3154 sssd exits if clock is adjusted backwards after boot
Closed: Fixed None Opened 2 years ago by lslebodn.

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

Description of problem:
The sssd daemon does not start on aarch64 architecture after reboot even if it
was enabled. Other architectures are not affected.
Switching selinux to permissive mode does not helps. There are not AVC denials
BTW.
It started with the rebased version. sssd-1.13.0-40.el7 works fine.

Version-Release number of selected component (if applicable):
sssd-1.14.0-14.el7.aarch64

How reproducible:
always

Steps to Reproduce:
1. Configure sssd with realmd. Either IPA or AD, does not matter for this test.

# realm -v join --user=admin <ipa.domain>

... snip ...

Client configuration complete.

 * /usr/bin/systemctl enable sssd.service
 * /usr/bin/systemctl restart sssd.service
 * /usr/bin/sh -c /usr/sbin/authconfig --update --enablesssd --enablesssdauth
--enablemkhomedir --nostart && /usr/bin/systemctl enable oddjobd.service &&
/usr/bin/systemctl start oddjobd.service
 * Successfully enrolled machine in realm

#
# ll /etc/systemd/system/multi-user.target.wants/sssd.service
lrwxrwxrwx. 1 root root 36 Aug  4 05:57
/etc/systemd/system/multi-user.target.wants/sssd.service ->
/usr/lib/systemd/system/sssd.service

2. Check that sssd is running and reboot

3. After reboot check sssd status

# uptime
 06:20:25 up 7 min,  1 user,  load average: 0.00, 0.05, 0.05
# service sssd status
Redirecting to /bin/systemctl status  sssd.service
? sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor
preset: disabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           ??journal.conf
   Active: failed (Result: exit-code) since Thu 2016-08-04 06:13:59 EDT; 6min
ago
  Process: 756 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 779 (code=exited, status=1/FAILURE)

# ausearch -m avc  -ts recent
<no matches>
#


4. If sssd si started manually it just start and works as expected

# service sssd start
Redirecting to /bin/systemctl start  sssd.service
# service sssd status
Redirecting to /bin/systemctl status  sssd.service
? sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor
preset: disabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           ??journal.conf
   Active: active (running) since Thu 2016-08-04 06:22:23 EDT; 5s ago
  Process: 2554 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 2556 (sssd)
   CGroup: /system.slice/sssd.service
           ??2556 /usr/sbin/sssd -D -f
           ??2557 /usr/libexec/sssd/sssd_be --domain ipa.baseos.qe --uid 0
--gid 0 --debug-to-files
           ??2558 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
           ??2559 /usr/libexec/sssd/sssd_sudo --uid 0 --gid 0 --debug-to-files
           ??2560 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --debug-to-files
           ??2561 /usr/libexec/sssd/sssd_ssh --uid 0 --gid 0 --debug-to-files
           ??2562 /usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --debug-to-files
           ??2565 /usr/bin/nsupdate -g -d -D

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => pbrezina
patch: 0 => 1
review: True => 0
selected: =>
status: new => assigned
testsupdated: => 0

master:

milestone: NEEDS_TRIAGE => SSSD 1.14.2
resolution: => fixed
status: assigned => closed

Metadata Update from @lslebodn:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.14.2

2 years ago

Login to comment on this ticket.

Metadata