This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Really High CPU Load for webadmin.plx

Setup : SG210 HA Master-Slave

50-70% CPU running webadmin.plx.  Seems like process is in some kinda of never-ending loop. 

Is this normal to have to reboot firewalls regularly.

 

top - 14:02:37 up 6 days, 6:06, 1 user, load average: 1.78, 1.62, 1.66
Tasks: 186 total, 5 running, 178 sleeping, 0 stopped, 3 zombie
Cpu(s): 62.8%us, 9.0%sy, 0.0%ni, 27.4%id, 0.3%wa, 0.0%hi, 0.5%si, 0.0%st
Mem: 8101356k total, 6298940k used, 1802416k free, 505696k buffers
Swap: 4194300k total, 0k used, 4194300k free, 3244648k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3660 wwwrun 20 0 117m 114m 10m R 48 1.5 20:53.46 webadmin.plx
32404 root 20 0 58316 41m 1652 S 41 0.5 0:01.63 confd.plx
3699 root 20 0 47716 43m 2332 S 19 0.5 26:49.44 ctmon.plx
5591 wwwrun 20 0 124m 122m 10m R 11 1.5 19:42.91 webadmin.plx
5497 root 20 0 26432 22m 2332 S 6 0.3 8:48.94 ctmon.plx
32413 root 20 0 58728 41m 1652 R 5 0.5 0:00.14 confd.plx
3700 root 20 0 6500 4236 912 S 3 0.1 5:31.09 cttop



This thread was automatically locked due to age.
Parents
  • Hi, Joseph, and welcome to the UTM Community!

    I developed a habit many years ago to never leave WebAdmin up on the Dashboard as that used to lead to a problem from a memory leak.  It looks like top is not showing that though, so maybe that glitch was fixed.

    If the trick recommended by Sachin is only a temporary fix and you find yourself needing to reboot or rerun the command, then there's something unusual happening and you should get Sophos Support involved.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Hi, Joseph, and welcome to the UTM Community!

    I developed a habit many years ago to never leave WebAdmin up on the Dashboard as that used to lead to a problem from a memory leak.  It looks like top is not showing that though, so maybe that glitch was fixed.

    If the trick recommended by Sachin is only a temporary fix and you find yourself needing to reboot or rerun the command, then there's something unusual happening and you should get Sophos Support involved.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data