Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 3356 views
  • Users 0 members are here
Options
Suggested
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

High CPU utilization

marcin
I run 3.209 for quite long time without any problems.
I realized lately the following errors in Selfmonitor log files:

"Apr 29 00:03:13 (none) superdaemon.pl[244]: [WAR 102] Too much memory for a single process - please check
Apr 29 00:03:30 (none) superdaemon.pl[244]: [WAR 103] Allocating to much swap - please check"

From time to time CPU utilization goes almost 100%.
Not long time ago it was 100% for almost 2 full days.
CPU utilization went back to normal by itself.

Any ideas?


This thread was automatically locked due to age.
Parents
  • 0
    The likely cause is very large log files being processed at midnight.
    In particular, the kernel log and the filter log will grow very large unless you have packet filter drop rules in place to keep the junk out of your logs. ASL will log drop a number of different packet types by default. The Microsoft Netbios beaconing is usually the worst offender when it comes to cluttering up your log files.

    Here are some filter rules you should consider implementing:

    Internal_Network_  { netbios }  Internal_Broadcast_  Drop
    Internal_Network_  { netbios } Internal_Interface_  Drop
    Any { netbios } External_Interface_  Drop
    Any  { netbios } Any  Drop

    That should take care of the bulk of your problem.
  • 0 in reply to VelvetFog
    It can be right but why my processor was 100% for full 2 days. It was not only at the midnight
Reply Children