On (16/03/16 14:30), Harald Dunkel wrote: >Hi Jakub, > >On 03/16/16 09:30, Jakub Hrozek wrote: >> >> If you can reproduce the issue, it would be nice to increase the debug_level >> a bit so that the debug logs are more verbose.. >> > >Using debug level 9 I got > >(Wed Mar 16 13:24:57 2016) [sssd] [server_setup] (0x0400): CONFDB: >/var/lib/sss/db/config.ldb >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3c2a0 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3c360 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3c2a0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3c360 "ltdb_timeout" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3c2a0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): no modules required by the db >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): No modules specified for >this database >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3c2d0 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3c390 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3c2d0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3c390 "ltdb_timeout" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3c2d0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3c4e0 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3c5a0 >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3c4e0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3c5a0 "ltdb_timeout" >(Wed Mar 16 13:25:00 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3c4e0 >"ltdb_callback" >(Wed Mar 16 13:25:00 2016) [sssd] [sysdb_domain_init_internal] (0x0200): DB >File for example.com: /var/lib/sss/db/cache_example.com.ldb >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3dbe0 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3dca0 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3dbe0 >"ltdb_callback" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3dca0 "ltdb_timeout" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3dbe0 >"ltdb_callback" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x0400): asq: Unable to register >control with rootdse! >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3dd80 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3de40 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3dd80 >"ltdb_callback" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3de40 "ltdb_timeout" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3dd80 >"ltdb_callback" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_callback": 0xb3dfd0 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Added timed event >"ltdb_timeout": 0xb3e090 >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Running timer event 0xb3dfd0 >"ltdb_callback" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Destroying timer event >0xb3e090 "ltdb_timeout" >(Wed Mar 16 13:25:01 2016) [sssd] [ldb] (0x4000): Ending timer event 0xb3dfd0 >"ltdb_callback" >(Wed Mar 16 13:25:04 2016) [sssd] [sbus_new_server] (0x0400): D-BUS Server >listening on >unix:path=/var/lib/sss/pipes/private/sbus-monitor,guid=d5f35f30568405c90a0fc9e756e950a0 >(Wed Mar 16 13:25:05 2016) [sssd] [sbus_add_watch] (0x2000): 0xb3e070/0xb3dda0 >(14), R/- (enabled) >(Wed Mar 16 13:25:05 2016) [sssd] [get_ping_config] (0x0100): Time between >service pings for [example.com]: [10] >(Wed Mar 16 13:25:05 2016) [sssd] [get_ping_config] (0x0100): Time between >SIGTERM and SIGKILL for [example.com]: [60] >(Wed Mar 16 13:25:05 2016) [sssd] [start_service] (0x0100): Queueing service >example.com for startup ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sssd should spawn child processes here. >(Wed Mar 16 13:25:06 2016) [sssd] [monitor_quit_signal] (0x2000): Received >shutdown command ^^^^^^^^^^^^^^^^^^^^^^^^^ After a second, sssd got signal for shutdown. >(Wed Mar 16 13:25:08 2016) [sssd] [monitor_quit_signal] (0x0040): Monitor >received Terminated: terminating children ^^^^^^^^^^ SIGTERM >(Wed Mar 16 13:25:08 2016) [sssd] [monitor_quit] (0x0040): Returned with: 0 >(Wed Mar 16 13:25:08 2016) [sssd] [monitor_quit] (0x0020): Terminating >[example.com][474] >(Wed Mar 16 13:25:08 2016) [sssd] [monitor_quit] (0x0020): Child [example.com] >terminated with a signal >(Wed Mar 16 13:25:08 2016) [sssd] [monitor_cleanup] (0x0010): Error removing >pidfile! (2 [No such file or directory]) >(Wed Mar 16 13:25:08 2016) [sssd] [sbus_remove_watch] (0x2000): >0xb3e070/0xb3dda0 > >
It does not look like problem in sssd. LS -- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project