# VERIFICATION FOR X&Y
After running the following script (repro.sh), the log shows the LDAP
resolution is rescheduled:
#!/bin/bash
change_time() {
sudo systemctl stop systemd-timesyncd
HOUR=$(date +%H)
MIN=$(date +%M)
NEW=$((10#$HOUR - 1))
sudo date --set "${NEW}:${MIN}"
echo "Setting time to ${NEW}:${MIN}"
}
sudo systemctl restart sssd
sleep 20
change_time
Excerpts from /var/log/sssd/sssd_openstacklocal.log:
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [fo_resolve_service_send]
(0x0100): Trying to resolve service 'LDAP'
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [get_server_status]
(0x1000): Status of server 'ldap' is 'not working'
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [get_server_status]
(0x1000): Status of server 'ldap' is 'not working'
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [fo_resolve_service_send]
(0x0020): No available servers for service 'LDAP'
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_resolve_server_done]
(0x1000): Server resolution failed: 5
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [sdap_id_op_connect_done]
(0x0020): Failed to connect, going offline (5 [Input/output error])
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_mark_offline]
(0x2000): Going offline!
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_mark_offline]
(0x2000): Initialize check_if_online_ptask.
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_ptask_create]
(0x0400): Periodic task [Check if online (periodic)] was created
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_ptask_schedule]
(0x0400): Task [Check if online (periodic)]: scheduling task 63 seconds from
now [1488462456]
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_run_offline_cb]
(0x0080): Going offline. Running callbacks.
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [sdap_id_op_connect_done]
(0x4000): notify offline to op #1
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]]
[sdap_dom_enum_ex_connected] (0x0400): Backend is marked offline, retry later!
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_ptask_done] (0x0400):
Task [enumeration]: finished successfully
(Thu Mar 2 13:46:33 2017) [sssd[be[openstacklocal]]] [be_ptask_schedule]
(0x0400): Task [enumeration]: scheduling task 300 seconds from last execution
time [1488462691]
(Thu Mar 2 12:46:00 2017) [sssd[be[openstacklocal]]]
[watchdog_fd_read_handler] (0x0040): Time shift detected, restarting watchdog!
* Some initialization log entries
(Thu Mar 2 12:46:40 2017) [sssd[be[openstacklocal]]] [fo_resolve_service_send]
(0x0100): Trying to resolve service 'LDAP'
(Thu Mar 2 12:46:40 2017) [sssd[be[openstacklocal]]] [get_server_status]
(0x1000): Status of server 'ldap' is 'name not resolved'
(Thu Mar 2 12:46:40 2017) [sssd[be[openstacklocal]]] [get_port_status]
(0x1000): Port status of port 389 for server 'ldap' is 'neutral'
(Thu Mar 2 12:46:40 2017) [sssd[be[openstacklocal]]]
[fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 6 seconds
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641875
Title:
Scheduled events (e.g. LDAP connection retries) are affected by clock
adjustments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1641875/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
