Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Zombie Processes

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    14 Posts 8 Posters 6.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      phospher
      last edited by

      I'm running 4 pfSense 2.0 boxes of the Oct 18th build and they all seem to have something in common. That is they all have a bunch of zombie processes. It appears that the check_reload_status is not reaping it's children.

      last pid: 17765;  load averages:  0.03,  0.05,  0.01                                  up 1+22:49:53  22:35:39
      68 processes:  1 running, 40 sleeping, 27 zombie
      CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
      Mem: 38M Active, 15M Inact, 45M Wired, 192K Cache, 34M Buf, 1385M Free
      Swap: 1024M Total, 1024M Free
      
      
      # ps ajx| grep Z
      root     239   222   222   222    0 ZN    ??    0:00.21 <defunct>root    8252   222   222   222    0 ZN    ??    0:00.21 <defunct>root    8874   222   222   222    0 ZN    ??    0:00.20 <defunct>root    9862   222   222   222    0 ZN    ??    0:00.20 <defunct>root   11131   222   222   222    0 ZN    ??    0:00.21 <defunct>root   16577   222   222   222    0 ZN    ??    0:00.16 <defunct>root   17584   222   222   222    0 ZN    ??    0:00.27 <defunct>root   18257   222   222   222    0 ZN    ??    0:00.21 <defunct>root   19476   222   222   222    0 ZN    ??    0:00.16 <defunct>root   20829   222   222   222    0 ZN    ??    0:00.21 <defunct>root   21463   222   222   222    0 ZN    ??    0:00.21 <defunct>root   22826   222   222   222    0 ZN    ??    0:00.21 <defunct>root   23109   222   222   222    0 ZN    ??    0:00.49 <defunct>root   25134   222   222   222    0 ZN    ??    0:00.20 <defunct>root   28688   222   222   222    0 ZN    ??    0:00.21 <defunct>root   29034   222   222   222    0 ZN    ??    0:00.21 <defunct>root   30116   222   222   222    0 ZN    ??    0:00.21 <defunct>root   31676   222   222   222    0 ZN    ??    0:00.50 <defunct>root   32261   222   222   222    0 ZN    ??    0:00.21 <defunct>root   40587   222   222   222    0 ZN    ??    0:00.21 <defunct>root   46739   222   222   222    0 ZN    ??    0:00.16 <defunct>root   47719   222   222   222    0 ZN    ??    0:00.21 <defunct>root   48849   222   222   222    0 ZN    ??    0:00.21 <defunct>root   49621   222   222   222    0 ZN    ??    0:00.22 <defunct>root   50886   222   222   222    0 ZN    ??    0:00.21 <defunct>root   56004   222   222   222    0 ZN    ??    0:00.16 <defunct>root   58094   222   222   222    0 ZN    ??    0:00.16 <defunct>#</defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct> 
      
      # ps ajx|grep 222
      root     222     1   222   222    0 INs   ??    0:00.01 /usr/local/sbin/check_reload_status
      root     224   222   222   222    0 IN    ??    0:00.00 /usr/local/sbin/check_reload_status
      root     239   222   222   222    0 ZN    ??    0:00.21 <defunct>root    8252   222   222   222    0 ZN    ??    0:00.21 <defunct>root    8874   222   222   222    0 ZN    ??    0:00.20 <defunct>root    9862   222   222   222    0 ZN    ??    0:00.20 <defunct>root   11131   222   222   222    0 ZN    ??    0:00.21 <defunct>root   16577   222   222   222    0 ZN    ??    0:00.16 <defunct>root   17584   222   222   222    0 ZN    ??    0:00.27 <defunct>root   18257   222   222   222    0 ZN    ??    0:00.21 <defunct>root   19476   222   222   222    0 ZN    ??    0:00.16 <defunct>root   20829   222   222   222    0 ZN    ??    0:00.21 <defunct>root   21463   222   222   222    0 ZN    ??    0:00.21 <defunct>root   22826   222   222   222    0 ZN    ??    0:00.21 <defunct>root   23109   222   222   222    0 ZN    ??    0:00.49 <defunct>root   25134   222   222   222    0 ZN    ??    0:00.20 <defunct>root   28688   222   222   222    0 ZN    ??    0:00.21 <defunct>root   29034   222   222   222    0 ZN    ??    0:00.21 <defunct>root   30116   222   222   222    0 ZN    ??    0:00.21 <defunct>root   31676   222   222   222    0 ZN    ??    0:00.50 <defunct>root   32261   222   222   222    0 ZN    ??    0:00.21 <defunct>root   40587   222   222   222    0 ZN    ??    0:00.21 <defunct>root   46739   222   222   222    0 ZN    ??    0:00.16 <defunct>root   47719   222   222   222    0 ZN    ??    0:00.21 <defunct>root   48849   222   222   222    0 ZN    ??    0:00.21 <defunct>root   49621   222   222   222    0 ZN    ??    0:00.22 <defunct>root   50886   222   222   222    0 ZN    ??    0:00.21 <defunct>root   56004   222   222   222    0 ZN    ??    0:00.16 <defunct>root   58094   222   222   222    0 ZN    ??    0:00.16</defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct></defunct> 
      
      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Yeah there were issues with check_reload_status around then. Update to a new build and it should be OK.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • P
          phospher
          last edited by

          Awesome, thanks Jimp!

          1 Reply Last reply Reply Quote 0
          • R
            robl
            last edited by

            @phospher:

            Awesome, thanks Jimp!

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

            Rob

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

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

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • E
                eri--
                last edited by

                Should be really fixed on new snapshots.

                1 Reply Last reply Reply Quote 0
                • P
                  phospher
                  last edited by

                  Cool, I will update and test.

                  Thanks.

                  1 Reply Last reply Reply Quote 0
                  • F
                    felles
                    last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • N
                      nocer
                      last edited by

                      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,

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        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.

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • R
                          robl
                          last edited by

                          @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

                          1 Reply Last reply Reply Quote 0
                          • L
                            learnin9
                            last edited by

                            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

                            1 Reply Last reply Reply Quote 0
                            • E
                              eri--
                              last edited by

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

                              1 Reply Last reply Reply Quote 0
                              • F
                                FisherKing
                                last edited by

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

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.