=> There are 90 zombie processes.
On one of my Homelab servers running Ubuntu Jammy, I always seem to get zombie processes. A quick check with ps -eo pid,ppid,stat,cmd | grep -w Z shows them all <defunct>. It just bugs me. I shut down the server in the most nicest of ways I know how with sudo shutdown -h now but I always get zombie processes shown on start up.
Am I missing something? Do these show up on your servers? How do you deal with them besides just ignoring them if they are <defunct>?


@BakedCatboy@lemmy.ml @frongt@lemmy.zip Most of them are from [curl] but one is from [health.sh]. I am assuming one of the docker containers uses
curlin it’s processes as I have not initiated anycurlcommands.If you use containers with health checks (including with curl), you need to tell docker (or podman) to provide an init process to reap child processes. For docker that means providing
--initwhen running a container. It’s a pretty common problem.What is their parent process?
Lots of these: Zombie PID: 230650 | Parent PID: 7791 | Parent Name: spawn-unnamed
Two of those: Zombie PID: 61072 | Parent PID: 7791 | Parent Name: bash
Lots of these: Zombie PID: 56798 | Parent PID: 7791 | Parent Name: health.sh
Lots of these: Zombie PID: 16761 | Parent PID: 7646 | Parent Name: curl
…and a box of naked lady tee’s
What is 7791?
7791 7768 201 /usr/sbin/netdata -u netdat 8.8 0.5 01:49:50
Sounds like netdata doing health checks but not always reaping its children. If you can reproduce it, I’d file a bug report.
Seems like someone already did this:
https://github.com/netdata/netdata/issues/20565
Maybe upgrading will fix it?
Hey bro, thanks for the lead! I will read the issue report and check if netdata is current.