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

Defunct processes

Scheduled Pinned Locked Moved General pfSense Questions
2 Posts 2 Posters 2.2k 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.
  • K
    korkakak
    last edited by May 3, 2008, 12:01 AM

    Hi all,

    I am using pfsense quite sometime(3+ months). Recently it came to my attention that are defunct processes (Z) left behind for no apparent reason.

    System details;

    
    # sysctl -a | grep -i hw. | grep mem
    hw.physmem: 393650176
    hw.usermem: 322949120
    hw.realmem: 402587648
    hw.firewire.fwmem.speed: 2
    hw.firewire.fwmem.eui64_lo: 0
    hw.firewire.fwmem.eui64_hi: 0
    hw.cbb.start_memory: 2281701376
    hw.pci.host_mem_start: 2147483648
    # uname -a
    FreeBSD cerberus 6.2-RELEASE-p11 FreeBSD 6.2-RELEASE-p11 #0: Sun Feb 24 16:32:58 EST 2008     sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense.6  i386
    # uptime
     2:40AM  up 20 days, 22:11, 2 users, load averages: 0.19, 0.66, 0.77
    # sysctl -a | grep -i CPU
    kern.threads.virtual_cpu: 1
    kern.ccpu: 1948
    kern.smp.cpus: 1
    kern.smp.maxcpus: 1
    debug.cpufreq.verbose: 0
    debug.cpufreq.lowest: 0
    hw.ncpu: 1
    hw.acpi.cpu.cx_supported: C1/0 C2/90 C3/900
    hw.acpi.cpu.cx_lowest: C1
    hw.acpi.cpu.cx_usage: 100.00% 0.00% 0.00%
    machdep.cpu_idle_hlt: 1
    dev.cpu.0.%desc: ACPI CPU
    dev.cpu.0.%driver: cpu
    dev.cpu.0.%location: handle=\_PR_.CPU0
    dev.cpu.0.%pnpinfo: _HID=none _UID=0
    dev.cpu.0.%parent: acpi0
    dev.cpu.0.freq: 1000
    dev.cpu.0.freq_levels: 1000/-1 500/-1
    dev.acpi_throttle.0.%desc: ACPI CPU Throttling
    dev.acpi_throttle.0.%parent: cpu0
    dev.cpufreq.0.%driver: cpufreq
    dev.cpufreq.0.%parent: cpu0
    
    

    (CPU in HRF; P3 @ 1 Ghz with 384Mbytes RAM)

    incident report;

    
    # ps aux | grep defunct | wc -l
          56
    # ps aux | grep defunct
    root   10619  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10620  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10621  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10622  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10625  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10626  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10627  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10628  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10629  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10630  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10631  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10632  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10633  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10634  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10635  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10636  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10637  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10638  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10639  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10640  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10642  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10643  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10644  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10645  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10646  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10647  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10648  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10649  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10650  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10651  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10652  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10653  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10684  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10685  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10686  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10687  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10688  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10689  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10690  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10691  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10705  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10706  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10707  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10708  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10709  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10710  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10711  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10712  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10713  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10714  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10715  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10716  0.0  0.0     0     0  ??  ZN    2:39AM   0:00.00 <defunct>root   10719  0.0  0.0     0     0  ??  Z     2:39AM   0:00.01 <defunct>root   10720  0.0  0.0     0     0  ??  Z     2:39AM   0:00.01 <defunct>root   82328  0.0  0.0     0     0  ??  Z     7:05PM   0:00.06 <defunct>root   10722  0.0  0.1   372   248  p0  R+    2:39AM   0:00.00 grep 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></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> 
    

    I guess that this appeared either when I started using PPPoE or PPPtP(before that everything seems working pretty straight forward without extra processes.)

    Stats are since pfsense 1.2 was installed. Some sort of time line of the process number (gray); During week 14 the radical fallout of the processes is obviously due to system's reboot. Notice week 15 where I started using PPPtP and PPPoE. My guess is that PPPoE is to blame, but I could experiment a bit and come out with some more info.

    So far it doesn't seem to be much trouble with the process crazy spawning but it would be nice to have some better looking graphs.
    Sorry for the forum entropy increase :-P

    Nikos

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by May 3, 2008, 12:11 AM

      I don't see that on any of my systems though I'm using pppoe and pptp on almost all of them as well.

      processes.png
      processes.png_thumb

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received