Hi Marco,

sixerjman <sixerj...@gmail.com> ezt írta (időpont: 2019. aug. 4., V, 14:03):
>
> Hmmm, it looks like inetd watchdog timer is expiration (systemd or inet's?) 
> is the root cause:
>
> -- Logs begin at Sat 2019-07-06 06:34:04 EDT, end at Sun 2019-08-04 07:55:01 
> EDT. --
> Jul 23 08:37:26 debiant systemd[1]: Starting Internet superserver...
> Jul 23 08:37:27 debiant systemd[1]: Started Internet superserver.
> Jul 23 19:00:05 debiant systemd[1]: inetd.service: Watchdog timeout (limit 
> 5s)!
> Jul 23 19:00:05 debiant systemd[1]: inetd.service: Killing process 1628 
> (inetd) with signal SIGABRT.
> Jul 23 19:00:07 debiant systemd-coredump[3087]: Process 1628 (inetd) of user 
> 0 dumped core.
> Jul 23 19:00:07 debiant systemd[1]: inetd.service: Main process exited, 
> code=dumped, status=6/ABRT
> Jul 23 19:00:07 debiant systemd[1]: inetd.service: Failed with result 
> 'watchdog'.
> Jul 23 19:00:08 debiant systemd[1]: inetd.service: Service RestartSec=100ms 
> expired, scheduling restart.
> Jul 23 19:00:08 debiant systemd[1]: inetd.service: Scheduled restart job, 
> restart counter is at 1.
> Jul 23 19:00:08 debiant systemd[1]: Stopped Internet superserver.

This seems to be an issue in inetd's watchdog handling. What do you think?
(Not reassigning yet to avoid ping-pong between packages.)

Cheers,
Balint

PS: Thanks sixerjman!

Reply via email to