[sles-beta] systemd sysvinit-compat weirdness

Aman Nijhawan anijhawan at vmware.com
Fri Sep 25 10:08:19 MDT 2015


Actually its a list of 20 services, I have tried getting a late debug shell on the system and it seems it is not able to swap off correctly. 

I am not doing any special mapping from my init scripts, there are a couple of scripts doing the su but they are not the ones having an issue shutting down. 

This issue is not there if I manually try to call shutdown. 

>From my understanding of systemd-sysvinit compat. It should just call the init.d script’s start and stop does it not do that?

Is there a support person you can put me in touch with that I can share my system with?

Thanks
Aman
On Sep 25, 2015, at 8:31 AM, Frederic Crozat <fcrozat at suse.com> wrote:

> Le vendredi 25 septembre 2015 à 14:23 +0000, Aman Nijhawan a écrit :
>> I  am seeing lockups on shutdown and reboot in sles12 with my services on sles12 that are using sysvinit-compat.
>> It seems systemd is not shutting down services correctly. 
>> 
>> My solution is to write a custom script  that gets invoked before the shutdown target and before the reboot target and shuts down the service correctly on reboot. 
>> But this feels like a hack and also slows the shutdown process down. 
>> 
>> Is anyone else seeing this? Is there a better solution?
> 
> Usually, when people reports this kind of behavior, it is because the
> initscript is doing some "ugly" things or is tricking systemd in the way
> it is trying to map the initscript to one of the "common" system service
> type.
> 
> So, my questions would be :
> - is your script tries to switch to another user (calling su foobar) to
> start a process as a non-root user ?
> - is your script tries to spawn a process which might take a long time
> before it terminates ?
> 
> The best way to debug this would be to boot systemd into debug mode (add
> systemd.log_level=debug to your kernel cmdline or use "systemd-analyse
> set-log-level debug" to change the debug output for the current
> session), then start your initscript, then terminate it (I'm assuming
> you have the same issue when stopping it and not only at shutdown).
> 
> 
> -- 
> Frederic Crozat
> Enterprise Desktop Release Manager
> SUSE
> 
> 
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.suse.com_mailman_listinfo_sles-2Dbeta&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=NplWt5dPxRkI-IKERB_URshYbPCJx5RwT-hRor4bJJI&m=F8KoFFUJZjvI_N78_w7TXUz6kYe9-i1nUTL8xNhDyhA&s=9aN4DhEVdZbtB2xdtjMkxAc2w28ov07ebk2sY_yo7Hk&e= 



More information about the sles-beta mailing list