Status to Green on msgs column ?
list Nicolas Dorfsman
Hi, Is anything change in 4.2.0 final version on side of msgs status ? My msgs columns seem to wait for a re-cycle of my messages file (so for a delete of the matched line) before re-coming to green. What's the matter ?
list Nicolas Dorfsman
Nobody seems to understand my question...probably to my english. Let's try with another question.... How could the msg column become green even if some messages have match a red rule ? 2007/2/9, Nicolas Dorfsman <user-ef21b83534bb@xymon.invalid>:
▸
Hi, Is anything change in 4.2.0 final version on side of msgs status ? My msgs columns seem to wait for a re-cycle of my messages file (so for a delete of the matched line) before re-coming to green. What's the matter ?
list Henrik Størner
▸
On Mon, Feb 12, 2007 at 09:48:11AM +0100, Nicolas Dorfsman wrote:
Nobody seems to understand my question...probably to my english. Let's try with another question.... How could the msg column become green even if some messages have match a red rule ?
If the offending messages are older than 30 minutes, they do not trigger a "red" status on the "msgs" column. Regards, Henrik
list Nicolas Dorfsman
2007/2/12, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid>:
▸
On Mon, Feb 12, 2007 at 09:48:11AM +0100, Nicolas Dorfsman wrote:How could the msg column become green even if some messages have match a red rule ?If the offending messages are older than 30 minutes, they do not trigger a "red" status on the "msgs" column.
So...I have a problem. My msgs column is staying red forever. Where could I start to look for ?
list Thomas Kern
Is there some way to increase that 30 minute window? Thomas Kern XXX-XXX-XXXX
▸
----- Original Message -----
From: user-ce4a2c883f75@xymon.invalid <user-ce4a2c883f75@xymon.invalid>
To: user-ae9b8668bcde@xymon.invalid <user-ae9b8668bcde@xymon.invalid>
Sent: Mon Feb 12 04:03:54 2007
Subject: Re: [hobbit] Re: Status to Green on msgs column ?
On Mon, Feb 12, 2007 at 09:48:11AM +0100, Nicolas Dorfsman wrote:Nobody seems to understand my question...probably to my english. Let's try with another question.... How could the msg column become green even if some messages have match a red rule ?
If the offending messages are older than 30 minutes, they do not trigger a "red" status on the "msgs" column. Regards, Henrik
list Henrik Størner
▸
On Mon, Feb 12, 2007 at 10:50:18AM +0100, Nicolas Dorfsman wrote:
2007/2/12, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid>:On Mon, Feb 12, 2007 at 09:48:11AM +0100, Nicolas Dorfsman wrote:How could the msg column become green even if some messages have match a red rule ?If the offending messages are older than 30 minutes, they do not trigger a "red" status on the "msgs" column.So...I have a problem. My msgs column is staying red forever. Where could I start to look for ?
The lines in the logfile that causes it to be red should be flagged in the status display. Then go hunting in your client configuration for the lines that match these log messages. Regards, Henrik
list Henrik Størner
▸
On Mon, Feb 12, 2007 at 06:43:08AM -0500, Kern, Thomas wrote:
Is there some way to increase that 30 minute window?
No, it's currently hard-coded in the clients' log-scanning program. Regards, Henrik
list Nicolas Dorfsman
▸
2007/2/12, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid>:
On Mon, Feb 12, 2007 at 09:48:11AM +0100, Nicolas Dorfsman wrote:How could the msg column become green even if some messages have match a red rule ?If the offending messages are older than 30 minutes, they do not trigger a "red" status on the "msgs" column.So...I have a problem. My msgs column is staying red forever. Where could I start to look for ?The lines in the logfile that causes it to be red should be flagged in the status display. Then go hunting in your client configuration for the lines that match these log messages.
I was busy by some other tasks.
My problem is still there... The case is on a Solaris 10 box where
I've installed the client compiled on Solaris 8.
I'm going to try to compile client on Solaris 10.
In the meantime, could you tell me where is located the code which is
responsible for this behaviour ?