Zombie Processes

robl · Oct 28, 2010, 4:25 PM

@phospher:

Awesome, thanks Jimp!

Hmm. I am still seeing this same issue on Thu Oct 28 03:32:27 EDT 2010 build.

Rob

jimp · Oct 28, 2010, 4:43 PM

I just checked and I'm seeing them also again. I'll pass it along.

eri-- · Oct 28, 2010, 7:48 PM

Should be really fixed on new snapshots.

phospher · Oct 28, 2010, 8:22 PM

Cool, I will update and test.

Thanks.

felles · Nov 1, 2010, 10:40 PM

Hi,

I'm running the beta4 with compile time "Sat Oct 30 19:40:13 EDT 2010" on an atom board and having the same zombie issues as described above.

regards

/F

nocer · Nov 2, 2010, 12:22 AM

hello

yup, still there.

pfsense# uname -ar
FreeBSD pfsense.local 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #1: Mon Nov  1 15:42:55 EDT 2010     sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386

pfsense# ps ajx | grep Z
root    3352   219   219   219    0 ZN    ??    0:12.08 <defunct>root   12088   219   219   219    0 ZN    ??    0:00.47 <defunct>root   12736   219   219   219    0 ZN    ??    0:00.47 <defunct>root   19249   219   219   219    0 ZN    ??    0:00.32 <defunct>root   19499   219   219   219    0 ZN    ??    0:00.47 <defunct>root   31271   219   219   219    0 ZN    ??    0:00.37 <defunct>root   31512   219   219   219    0 ZN    ??    0:00.41 <defunct>root   48315   219   219   219    0 ZN    ??    0:00.37 <defunct>root   49372   219   219   219    0 ZN    ??    0:00.38 <defunct>root   50591   219   219   219    0 ZN    ??    0:00.37 <defunct>root   52139   219   219   219    0 ZN    ??    0:00.37 <defunct>root   53442   219   219   219    0 ZN    ??    0:05.40 <defunct>root   62890   219   219   219    0 ZN    ??    0:00.47 <defunct>root   63060   219   219   219    0 ZN    ??    0:11.73 <defunct>root    8042 59642  7726 55985    2 S+     0    0:00.00 grep Z

pfsense# ps ax |grep 219
  219  ??  INs    0:00.01 /usr/local/sbin/check_reload_status
20373   0  S+     0:00.00 grep 219</defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct>

all is harmless anyway but it just annoying tho…

cheers,

jimp · Nov 2, 2010, 12:22 AM

I'm not sure that check_reload_status was rebuilt after that fix went in. I just rebuilt it by hand and restarted the builds. Try again after the next new snapshot.

robl · Nov 4, 2010, 6:40 PM

@jimp:

I'm not sure that check_reload_status was rebuilt after that fix went in. I just rebuilt it by hand and restarted the builds. Try again after the next new snapshot.

Problem still happening as of this build: Thu Nov 4 01:20:42 EDT 2010 (i386)

Rob

learnin9 · Nov 9, 2010, 5:53 AM

I found the same issue on my system.so I installed the cron package from the pfsense GUI.
this is my cron list:
0 3 * * * killall check_reload_status
1 3 * * * /usr/local/sbin/check_reload_status

eri-- · Nov 9, 2010, 8:13 PM

Heh 'typo' was preventing the fix from actually being applied.
Newer snaps have the correct fix.

FisherKing · Nov 10, 2010, 4:45 PM

Installed the update from 2010-11-09 16:xx (i386). The process count is no longer climbing out of control.
Thanks!