<div dir="ltr"><div><div><div><div><div>Hello <br><br></div> I am using Fedora 19 and systemd in it is 204 I guess. The issue is present in there. The following is whatmy unit file is <br><br>>>>><br>cat /usr/lib/systemd/system/Myservice.service <br>
[Unit]<br>Description=This is a test service<br><br>[Service]<br>#PIDFile=/var/run/Myservice.pid<br>#ExecStartPre=/tmp/one_start_pre.sh<br>#ExecStartPre=/bin/systemctl stop Myservice<br>ExecStartPost=/tmp/one_start_post.sh<br>
#ExecStartPre=/usr/bin/systemctl stop Myservice<br>RemainAfterExit=yes<br><br>ExecStart=/tmp/one.sh<br><b><span style="color:rgb(255,0,0)">Restart=on-failure</span></b><br>NotifyAccess=all<br>WatchdogSec=10<br>User=admin<br>
Group=admin<br><br>[Install]<br>Alias=myservice.services<br><br><<<<<<br><br></div>systemctl output <br><br>>>><br><br>sudo systemctl status Myservice<br>Myservice.service - This is a test service<br>
Loaded: loaded (/usr/lib/systemd/system/Myservice.service; disabled)<br> Active: active (running) since Thu 2013-12-05 18:39:36 IST; 1s ago<br> Process: 20968 ExecStartPost=/tmp/one_start_post.sh (code=exited, status=0/SUCCESS)<br>
Main PID: 20967 (one.sh)<br> CGroup: name=systemd:/system/Myservice.service<br> ├─<b><span style="color:rgb(255,0,0)">20967</span></b> /bin/bash /tmp/one.sh<br> └─20971 sleep 5<br><br><br></div><span style="color:rgb(0,0,255)">After some time I made the watchdog timer fail. </span><br>
<br>sudo systemctl status Myservice<br>Myservice.service - This is a test service<br> Loaded: loaded (/usr/lib/systemd/system/Myservice.service; disabled)<br> Active: active (running) since Thu 2013-12-05 18:40:52 IST; 2s ago<br>
Process: 21180 ExecStartPost=/tmp/one_start_post.sh (code=exited, status=0/SUCCESS)<br> Main PID: 21179 (one.sh)<br> CGroup: name=systemd:/system/Myservice.service<br> ├─<span style="color:rgb(255,0,0)"><b>20967</b></span> /bin/bash /tmp/one.sh<br>
├─21006 /bin/bash /tmp/one.sh<br> ├─21030 /bin/bash /tmp/one.sh<br> ├─21058 /bin/bash /tmp/one.sh<br> ├─21092 /bin/bash /tmp/one.sh<br> ├─21133 /bin/bash /tmp/one.sh<br> ├─21166 sleep 5<br>
├─21169 sleep 5<br> ├─21172 sleep 5<br> ├─21175 sleep 5<br> ├─21178 sleep 5<br> ├─21179 /bin/bash /tmp/one.sh<br> ├─21184 sleep 5<br> └─21191 sleep 5<br>
<br><br><<<<<<<br><br>$$ ] systemctl --version<br>systemd 204<br>+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ<br><br></div>Thanks<br></div>Salil<br><div><div><br></div></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 November 2013 20:27, Hoyer, Marko (ADITG/SW2) <span dir="ltr"><<a href="mailto:mhoyer@de.adit-jv.com" target="_blank">mhoyer@de.adit-jv.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> > One more issue I observed is - if I specify Restart=on-failure, if<br>
> > watchdog timer expire, it restart the service. But I can see that it<br>
> > create two processes rather than restarting the process. But if I do<br>
> > systemctl restart Myservice , it kills the previous instance of<br>
> > service and start a new service. Any pointers on why it happens so.<br>
<br>
</div>This part has been already reported as a bug in May:<br>
<a href="http://lists.freedesktop.org/archives/systemd-devel/2013-May/011030.html" target="_blank">http://lists.freedesktop.org/archives/systemd-devel/2013-May/011030.html</a><br>
<br>
Best to my knowledge, this has been fixed in systemd 203, 204, or 205 ...<br>
Please note that the link above does not contain the final bug fix. Some discussions followed which led to the final solution at a certain point. Follow the threads, you'll find it ...<br>
<br>
<br>
Best regards<br>
<br>
Marko Hoyer<br>
Software Group II (ADITG/SW2)<br>
<br>
Tel. +49 5121 49 6948<br>
</blockquote></div><br></div>