The Planet Forums > /bin/grep -c [-]> /var/log/exim

Got-Hosting

Feb 6 2004, 07:56 AM

Anyone know what is calling these? They are killing two of my servers. Server load is over 2.

root 94.11 176.68 2.0
Top Process %CPU 99.9 /bin/grep -c [-]> /var/log/exim_mainlog
Top Process %CPU 99.7 /bin/grep -c [-]> /var/log/exim_mainlog
Top Process %CPU 91.9 /bin/grep -c < /var/log/exim_mainlog

If I kill the process anotehr one just spawns.

Got-Hosting

Feb 6 2004, 08:15 AM

Well, it seems that it was being called by gpan's mrtg package. Seems some RH9/RHEL boxes have issues with it for soem reason.

Not good.

I really came to rely on MRTG a lot. I guess I'm going to have to figure it out the hard way.

Dave#

Feb 6 2004, 08:40 AM

disable that part of the config

I try not to use any server side scripts for MRTG - defeats the purpose IMVO

Got-Hosting

Feb 6 2004, 08:42 AM

Can you help to make it simple for me? What would I edit to take taht part out?

Thanks! I had not thought of that!

Jon

Dave#

Feb 6 2004, 08:44 AM

QUOTE

Originally posted by Got-Hosting
Can you help to make it simple for me? What would I edit to take taht part out?

Thanks! I had not thought of that!

Jon

find mrtg.cfg and comment out the exim part - near the end from memory

benito

Dec 12 2004, 09:06 AM

Hi!

I got the same issue, you find the fix for this problem ?

Got-Hosting

Dec 12 2004, 09:14 AM

In /etc/mrtg/mrtg.cfg, towards the end of the file it goes from being double spaced to single spaced. You simply need to delete all the double spaced lines.

benito

Dec 12 2004, 04:34 PM

QUOTE

Originally posted by Got-Hosting
In /etc/mrtg/mrtg.cfg, towards the end of the file it goes from being double spaced to single spaced. You simply need to delete all the double spaced lines.

Hi!

Do you mean something like change this:

CODE

#----------------------------

# Memory

#----------------------------

Target[localhost.mem]: `free -bt | grep buffers/cache | awk '{print $3"n"$4}'`

MaxBytes[localhost.mem]: 665536000

Title[localhost.mem]: Memory Utilization for domain.com

PageTop[localhost.mem]: <H3>Memory Utilization for domain.com </H3>

Options[localhost.mem]: gauge,growright

YLegend[localhost.mem]: Bytes

ShortLegend[localhost.mem]: B

Legend1[localhost.mem]: Free real memory

Legend2[localhost.mem]: Free swap memory

Legend3[localhost.mem]: Maximal 5 Minute Memory In Use

Legend4[localhost.mem]: Maximal 5 Minute Active Memory

LegendI[localhost.mem]: Used:

LegendO[localhost.mem]: Buffers + Cache:

XSize[localhost.mem]: 350

To this ?:

CODE

#----------------------------

# Memory

#----------------------------

Target[localhost.mem]: `free -bt | grep buffers/cache | awk '{print $3"n"$4}'`

MaxBytes[localhost.mem]: 665536000

Title[localhost.mem]: Memory Utilization for domain.com

PageTop[localhost.mem]: <H3>Memory Utilization for domain.com </H3>

Options[localhost.mem]: gauge,growright

YLegend[localhost.mem]: Bytes

ShortLegend[localhost.mem]: B

Legend1[localhost.mem]: Free real memory

Legend2[localhost.mem]: Free swap memory

Legend3[localhost.mem]: Maximal 5 Minute Memory In Use

Legend4[localhost.mem]: Maximal 5 Minute Active Memory

LegendI[localhost.mem]: Used:

LegendO[localhost.mem]: Buffers + Cache:

XSize[localhost.mem]: 350

Got-Hosting

Dec 12 2004, 04:57 PM

No, what I mean is that at a certain point in that file, the spacing goes from being double spaced to being single spaced. All the mail stuff is single spaced, so you delete the part of the file that is single spaced.

You could also read the file, as you can usually tell what is going on by reading the lines.