What does "INFO reaped unknown pid" in the log mean?

[snyderpa-owl]

With cron running under supervisor at loglevel 'info' and a job that runs every 60 seconds, the supervisor log receives a new message every minute:

2022-09-23 19:40:05,839 INFO reaped unknown pid 10547 (exit status 0)

Searching the documentation for "reap" yields only one result (the changelog) with no clear explanation of why I should care that supervisor reaped an unknown pid with exit status 0.

Expectation: if there is some change I should make to my deployment, I should be able to find that in the documentation. If it means nothing to me, it should be a debug message so that I can isolate it from the interesting INFO events about service startup.

[sblondon]

This line is written by the logger in supervisord.py file.

The line is equivalent to a unit test.

It seems a process managed by supervisor has been killed whereas still managed by supervisord. Perhaps the cron task starts child processes which are badly closed (so are zombies)? (I don't get why the cron task is runned by supervisord and not crontab.)

[nook24]

I have a similar issue. I use supervisor to manage nginx and php-fpm inside of a docker container. How ever, when I run a command with sudo inside the container, Supervisor logs the message 2023-05-11 13:25:08,163 INFO reaped unknown pid 691 (exit status 1) even if the command is total unrelated to supervisor at all.

echo 1 => No log message

sudo echo 1 => 2023-05-11 13:27:52,360 INFO reaped unknown pid 694 (exit status 1)

I'm not sure what's happening here to be honest.

// Edit
In my case it was because supervisor was running as PID 1, i added tini to resolve this issue