Posted by: paragon | October 28, 2006

PRM: Process Resource Monitor – HowTo: Set Rules

PRM: Process Resource Monitor from RFxNetworks is a nifty monitor to take care of runaway proc’s and auto kill them if they rise above the predefined setting.

Be sure to take a look at the rules directory, one value of note is for Exim – on a busy server you may need to ReOption the value for max proc’s from 10 to 20 … be sure the reason for added proc’s is due to how busy the server is with mail and not that you have a client that is spamming…

Fine the custom service config files here:

/usr/local/prm/rules

(Please note: This example is for a cPanel server)

And here is the result of the exim rule file:

# seconds to wait before rechecking a flaged pid (pid’s noted resource
# intensive but not yet killed).
WAIT=”12″

# counter limit that a process must reach prior to kill. the counter value
# increases for a process flaged resource intensive on rechecks.
KILL_TRIG=”3″

# argument to pass onto kill commands
KARG=”9″

# Max CPU usage readout for a process – % of all cpu resources (decimal values unsupported)
MAXCPU=”85″

# Max MEM usage readout for a process – % of system total memory (decimal values unsupported)
MAXMEM=”15″

# Max processes for a given command – this is not max processes for user but rather the executable
MAXPS=”20″

**** The last option of Max processes for a given command was bumped from 10 to 20

Cheers,

Dave Safley

http://www.ParagonHost.com

Advertisements

Responses

  1. […] Paragonhost has a very useful post on setting up custom PRM rules (Process Resource Monitor). […]


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: