Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am experiencing a problem with sendmail on my server. I have been using a system integrity monitor on the server and have recently been getting the following emails.
System integrity monitor on xxxxxxx.net has taken action in responce to an event. Recent event logs are enclosed below for your inspection. There has been 3 events today, if an average of 8 events is reached, e-mail alerts will be terminated for the duration of the day.
The events in question are the similar to the following:
Oct 31 10:40:35 sendmail: sendmail shutdown succeeded
Oct 31 10:40:39 sendmail: sendmail startup succeeded
When I run the TOP command I get the following information:
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
3414 root 25 0 2852 2852 2068 R 22.6 0.2 281:18 sendmail: ./j7U6mTQ29698: from queue
5918 root 25 0 2840 2840 2068 R 22.6 0.2 221:42 sendmail: ./j7U8P1j01281: from queue
15237 root 25 0 2848 2848 2068 R 19.6 0.2 157:32 sendmail: ./j83CUuw25958: from queue
8742 root 25 0 2840 2840 2060 R 17.0 0.2 192:03 sendmail: ./j81Cfh109118: from queue
11734 root 25 0 2840 2840 2060 R 17.0 0.2 172:13 sendmail: ./j82EYVe26050: from queue
I appears that sendmail is spawning processes that consume all the cpu. I have killed the sendmail process several times and the cpu goes back to the normal 2-5% range, however after about 40 minutes there are a few processes that are consuming 97-98% of the cpu. I did not see anything in the queue - I figured it might be trying to send something that was queued there due to the "from queue" listed by the TOP command.
I would appreciate any help in understanding why the processes are consuming so much cpu and how to kill or eliminate the processes themselves.
first of all try these things to find out why send mail is using more CPU time.
1) find out to whome is the send mail sending al mails. check /var/log/mail and see the mail queue and find out who was the recepient of all these mails( or most of those).
2) as which user is the sendmail running. It should never be running as root.
3) check ur root@localhost mail account (type mail at console and if u have problems go through man mail). From here you can have a comprehensive lokk at system generated mails to root mail account relating to common problem notification. Check andfind out which possible situation is occuring again and again that is making sendmail send mails and use CPU time considerably.
these are basic diagnosis steps that should get you going in the right direction is you are still stuck.