Liddler has the info you need on changing the settings.
I'd like to know what is causing your server to reach a load average of 147!!!
What do you have running on it that causes it to get to that level?
Main Topics
Browse All TopicsThe /var/log/syslog contains:
Jan 6 10:32:35 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MTA-IPv4: load average: 147
Jan 6 10:32:35 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MTA-IPv6: load average: 147
Jan 6 10:32:35 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MSA: load average: 147
Jan 6 10:32:50 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MTA-IPv4: load average: 147
Jan 6 10:32:50 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MTA-IPv6: load average: 147
Jan 6 10:32:50 webext-db01-a sendmail[354]: [ID 702911 mail.info] rejecting connections on daemon MSA: load average: 147
...
In addition, the cronjobs are not running either.
What does those messages in the syslog mean? what is wrong?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The loadaverage is the average number of threads on the run queue during the previous minute. The run queue is a queue of threads that are runnable, that is able to run if they could get on the CPU. The reasoning used by sendmail is that accepting a mail messgae for delivery is a pretty big commitment of resources, and as such will increase the loadvaerage even further. So, when it stops accepting messages, it allows the existing messages to be delivered and removed from the system and freeing up the resources to be used by other jobs. Since internet mail is a store and forward protocol, the sending process on the other machine is supposed to try again later, so all this does is delay the delivery, rather than risk
a possible failure and/or longer delays due to resource contention.
So, while liddler's answer is factually correct, it might b exectly the wrong thing to do, since removing the loadavg check will make an already
overloaded system even worse. A lodavg of 147 is pretty high. In my experience, a loadavg in the low twenties is the max for interactive use, and the forties is where even batch type processing starts to suffer.
Of course, if the system was running fine other than that, and if the system isn't a mail server, it might make sense to up the limit. I mean if the systme's loadavg is regularly 147 in the normal course of its duties, then mail would never be accepted with this limit. This is one of the reasons why it is important to establish a baseline of normal work for comparison.
On the other hand, if the system is in fact a mail server and isn' doing anything else, you need to establish why the loadavg is so high. Is it just because the mail load is too much for the poor thing, or is there another problem? For instance, a naming system (DNS) problem might result in a longer service time per message, increasing the number of sendmail processes actually running.
If the loadave is too high high, then cron jobs will take a long time to run. Cron will only allow itself to have a certain number of children at once, so if they run too long, then this will prevent other jobs from running. So, it sounds like the loadavg is way too high for this system, and your only course of action is to try to determine why.
a reboot might help, but it would good to find out what processes were causing the bottleneck.
Do you have top installed? (if not you can get it from www.sunfreeware.com) use top to see what is hogging the processor.
Copy the output here, if you don't understand it.
I suspect cron jobs won't run if there are a large number of existing cron jobs still running - Which would also push up the load average, even if the individual jobs aren't very big.
Check /var/cron/log for errors; Also try ps -ef |grep " "`ps -ef |grep [c]ron |awk '{print $2}'` to see if there are a large number of jobs currently running under cron - It may be that someone has changed a job so it never exits, or a job is waiting for a resource that isn't available.
ps -ef should also give you some clues if there are vast numbers of jobs running - Maybe just a badly behaved user or script, leaving jobs hung ;-)
Business Accounts
Answer for Membership
by: liddlerPosted on 2004-01-06 at 02:13:16ID: 10050987
Looks like your load averages are high, i.e. your machine is too busy
What is the output of command:
uptime
Just googled and found this:
Check your /etc/mail/sendmail.cf file and unhash/change the
appropriate lines:
# load average at which we just queue messages
#O QueueLA=8
# load average at which we refuse connections
#O RefuseLA=12
# load average at which we delay connections; 0 means no limit
#O DelayLA=0