Frequent Report is getting huge...

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Frequent Report is getting huge...

Postby mito » Tue Sep 11, 2007 9:28 am

Hey all, hopefully you can help me figure this out.

I have been seeing rising sizes of my Scalix Frequent Report that is a bit troublesome. Every now and then I'll get the report in an email, and when I do it emails me the entire history, so that it is always adding more and more. Last night I got it and it was 41mb in size!

The actual error is this:



Code: Select all

--Performing Port Check on localhost:25-----
Error: Timeout on port mail.domain.com:25
-------------------------------------------
-------------------------------------------
The following text is the output from the fatal log


And then follows the fatal log, which is huge. The reason that I'm getting this, I am guessing, is because it tried to run the check during the very end of the backup routine, where I have it set to restart all mail processes (needed due to a bug with the SAC not being accessible after a few hours of being up and running). I believe this because I got the message at 6:30am today and the backup finished at 6:26am.

What does everyone do to clean up the fatal log? Or better yet, my fatal log is right now full of nothing other than failed routing requests from spam trying to use the server as a relay. Is there a way to prevent the relay requests from getting to the fatal log?

Thanks
Mito

gren
Scalix
Scalix
Posts: 264
Joined: Thu Mar 25, 2004 10:27 am
Contact:

Postby gren » Wed Sep 12, 2007 12:19 pm

Hi mito.

I assume you are using ommaint from the Admin Resource Kit?
http://downloads.scalix.com/ark/ommaint

This tends to use omshowlog at a high level and without limit on history to report problems with services.

Some customisations you might want to make :

Say you want messages up to level 11 (rather than the default of 99) and only for the last day (1440 minutes) and perhaps include the PIDs, then near the top of the script, setup an environment variable :
OMSHOWLOG_STD_OPTS="-P -p 1440 -l 11"
find all references to $SX_BIN_DIR/omshowlog

In these lines, change the string "$SX_BIN_DIR/omshowlog"
to "$SX_BIN_DIR/omshowlog ${OMSHOWLOG_STD_OPTS}"

Delete the existing "-l 99"

Hope that helps.

Regards,
Gren.

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Postby mito » Wed Sep 12, 2007 10:45 pm

Definitely worth a shot, I just changed it all and we'll see how that works.

Thanks!


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 5 guests