=> 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 . 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 ?

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 6 months ago (8 children)

@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 curl in it's processes as I have not initiated any curl commands.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 2 points 6 months ago*

    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 --init when running a container. It's a pretty common problem.

  • source
  • parent
  • [–] -1 points 6 months ago (6 children)

    What is their parent process?

  • source
  • parent
  • hideshow 6 child comments
  • [–] [S] 1 point 6 months ago* (5 children)

    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

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 6 months ago (4 children)
  • [–] [S] 1 point 6 months ago (3 children)

    7791 7768 201 /usr/sbin/netdata -u netdat 8.8 0.5 01:49:50

  • source
  • parent
  • hideshow 3 child comments
  • [–] -1 points 6 months ago (2 children)

    Sounds like netdata doing health checks but not always reaping its children. If you can reproduce it, I'd file a bug report.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 6 months ago (1 child)

    Seems like someone already did this:

    https://github.com/netdata/netdata/issues/20565

    Maybe upgrading will fix it?

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 2 points 6 months ago

    Hey bro, thanks for the lead! I will read the issue report and check if netdata is current.

    @ilyam8 - adding to it here, netdata does leave tons of zombies around, this is not a "cannot reproduce" (not sure why that tag was added without even the minimal response, and then removed needs triage on top of that, so this ticket just dies off) One simply needs a running netdata instance and let it run a while. With time, 1, three and then tens of zombies will be listed at login.

  • source
  • parent