From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Oliver Schad" <oliver.schad@automatic-server.com>,
supervision@list.skarnet.org
Subject: Re: Expected behaviour zombie processes
Date: Tue, 01 Dec 2020 10:25:27 +0000 [thread overview]
Message-ID: <em59dc64f1-0dc0-49c2-9df8-ebcf09768fc6@elzian> (raw)
In-Reply-To: <20201201104538.36b8b8fb@flunder>
>Hi everybody
>
>I've observed the following situation:
>
>root 490 0.0 0.0 13004 1596 ? S Nov05 0:00 s6-supervise lxe
>root 2738 0.6 0.0 0 0 ? Zsl Nov05 251:13 [lxe] <defunct>
>
>So you see a zombie process. What is the expected behaviour of
>s6-supervise here? I would expect, that this case is solved immediatly
>by s6-supervise and a new process is spawned.
>
>The observed behaviour was, that no new process was spawned and even
>s6-svc -r didn't respawn a process.
Hi Oli,
There is no indication that the zombie lxe process is a direct child
of s6-supervise. What does 's6-svstat /run/service/lxe' say?
If that lxe process was s6-supervise's child, s6-supervise should
definitely reap the zombie immediately and spawn a new lxe process;
failing to do so would be a bug that has, to my knowledge, never
happened. There is definitely something else at play here.
--
Laurent
prev parent reply other threads:[~2020-12-01 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 9:45 Oliver Schad
2020-12-01 10:25 ` Laurent Bercot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em59dc64f1-0dc0-49c2-9df8-ebcf09768fc6@elzian \
--to=ska-supervision@skarnet.org \
--cc=oliver.schad@automatic-server.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).