Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I started a sec process via

/etc/init.d/sec start
with a bad config file (the arguments being passed are in an unintended format.

When a rule passes it tries to mail me. If the mail script dies, it mails me saying that the mail script dies.

I am getting hundreds of mails from something having to do with this process... I found a sec process via

ps auxw | grep sec
and killed it.

The script that mails me is called I moved that file so it could no longer be executed.

ps auxw | grep
does not show anything either.

However, I am still getting emails and the load average on the server is really high. Any ideas on how to debug this?

Tried running the following commands to see what was in the queue. I cleared the queue a few minutes ago, so notihgn should be showing up and indeed, nothing is:

root@localhost:/var/log# exim4 -bp
root@localhost:/var/log# mailq
share|improve this question

Check your queue with mailq, maybe you have too many messages queued for delivery and it will take some time. You can use exim4 -Mrm <id> to remove a message from the queue, so if you grep the correct IDs for the messages you don't want you can remove it with a for loop like this:

mailq |grep root | awk '{ print $3}' | xargs exim4 -Mrm

Just notice that in this case I am grepping root so it will remove any message that was sent by root, YMMV.

share|improve this answer
updated my question. seems as if there is nothing in the queue. – Hersheezy May 4 '11 at 5:29
Well I failed... had to restart :( Thanks a ton though for your input, it was much appreciated! – Hersheezy May 4 '11 at 14:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.