[systemd-devel] Socket is dying, how to automatically restart it?

[David Strauss]

Are you sure it's not the corresponding service that really failed?

On Wed, Apr 10, 2013 at 11:46 AM, Kok, Auke-jan H
<auke-jan.h.kok at intel.com> wrote:
> On Wed, Apr 10, 2013 at 11:10 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>
>> Op 10 apr. 2013, om 19:13 heeft Mantas Mikulėnas <grawity at gmail.com> het volgende geschreven:
>>
>>> On Wed, Apr 10, 2013 at 8:03 PM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>>> Hi,
>>>>
>>>> I have a bit of a heisenbug where dropbear.socket will just die and needs a systemctl restart dropbear.socket. I can't tell why it's dying, just that it does within 3 days of uptime. After restarting it it seems to be rock solid again for at least some weeks.
>>>>
>>>> The real way to fix this is to find out why it dies,
>>>
>>> After death, does `systemctl status dropbear.socket` show any error
>>> messages in the status line?
>>
>> No, only that it's dead, so systemd knows that it's has failed somehow
>
> "dead" isn't necessarily the same as "failed"... and I wonder if you
> can use ExecStartPost= here to kick it - it's valid for [Socket]
> sections.
>
> Auke
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel



-- 
David Strauss
   | david at davidstrauss.net
   | +1 512 577 5827 [mobile]