Bug#805623: systemd: weird behaviour using 'Restart=on-watchdog'

[Michael Biebl]

Am 20.11.2015 um 13:16 schrieb Arturo Borrero Gonzalez:
> On 20 November 2015 at 13:13, Michael Biebl <biebl at debian.org> wrote:
>> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>>> exited, code=killed, status=6/ABRT
>>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Changed
>>> stop-sigabrt -> failed
>>
>> It seems your process aborted and you don't have Restart=on-failure or
>> Restart=on-abort.
>>
>> I assume that's why it is not restarted.
>>
> 
> I sent just SIGSTOP as in previous cases.
> 
> What means 'aborted' for systemd? I can reproduce the behaviour, so I
> think it seems related to systemd, don't you?
> 

abort is usually issued by the process itself, but it can also be sent
externally. You need to find out if the abort actually came from systemd
or the process died on its own for some other reason.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151120/96743af9/attachment-0002.sig>