On (19/03/16 10:38), Harald Dunkel wrote:
>On 03/16/16 14:43, Lukas Slebodnik wrote:
>> On (16/03/16 14:30), Harald Dunkel wrote:
>>> (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.
>> 
>
>Are you sure? Then why doesn't it "spawn child processes here"?
>
Logs are from main process. If the main progess get a signal
for shutdown then it cannot continue with "spawning child processes".
sssd has to shutdown.

>I would guess the SIGTERM was either sent by systemd or sssd's
>startup script?
What do you mean by sssd's startup script?

You either have systemd or upstart/sysv
and you should know which initsystem do you use.

sssd does not send SIGTERM to itself therefore
signal had to be send from somewhere else.
So it's not a problem of sssd.

>Since freeipa doesn't work with anything else
>but systemd its a little bit cheap now to say "not my problem",
>is it?
>
"freeipa-server" doesn't work with anything else but systemd.
and freeipa-client just configure sssd and few other services.

But sssd itself can run without systemd.

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

Reply via email to