zombie processes

Hi,

I am an absolute n00b in Linux, Server, OMV, so please keep that in mind.

I have the same Zombie-problem ... I think the "new PID" is not the problem,
and "normal", but the root of all evil is another point.

It seems to be, that the zombie-process/es end/s and then revive/s. then he gets a
new PID assigned. The same thing would happen if you kill the zombie with

kill 14778

When the Z wont end and comes back, it gets a new PID (from father process!?).

So it make no sense to kill the process, nor to kill the father process. This zombie
keeps coming back. (in my case) The question we now have to ask ourselves is:

What causes this MOUNTPOINT error / zombie?

Does anyone else have zombie processes related to MOUNT POINT?
Does anyone have an answer for that?

Same here... 2 zombies processes

root@omvglbvprd1:~# ps aux |grep 'Z'
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     15366  0.0  0.0      0     0 ?        Zs   10:49   0:00 [mountpoint] <defunct>
root     15367  0.0  0.0      0     0 ?        Zs   10:49   0:00 [mountpoint] <defunct>
root     15373  0.0  0.0  12788  1000 pts/0    S+   10:49   0:00 grep Z

me too. Any solution?

Zitat von sbocquet

2 zombies processes

So what?

Ignoring them is the most simple way to deal with those processes especially since you can clearly read above how much impact they have on your system: exactly none (no memory wasted, just some entries in the process table that do not hurt)

https://kerneltalks.com/howto/…need-know-zombie-process/

If you want to investigate you would need to check PPID (parent process ID --> 'ps -eaf' and there 3rd column) to get an idea which process forked them (maybe just to realize that these processes have already quit). But the best way to deal with zombies is to learn that they're harmless if it's just a few and ignore them.

Hi tkaiser,

I already done my research but haven't had the time to post here

root      1077     1  0 mars19 ?       00:00:11 /usr/bin/monit -c /etc/monit/monitrc
...
root     20316  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>
root     20317  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>
root     20318  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>

And here is the answer

Zitat von sbocquet

And here is the answer

And since these zombies die pretty fast (look at your timestamps) it's just the result of monit calling '/bin/mountpoint' to get a clue which mountpoints or directories below /srv or /media belong to which block device (to graph disk utilization or whatever). They come and go most probably every minute or even seconds and are harmless

Being a former heavy Solaris and still macOS user I love execsnoop.

Working everydays on Solaris 8/10 at Work...