Purple - STATUSLIFETIME 1000
Hi
I am just using xymon to do some low level netwoek monitoring.
I changes the tasks to every 6 hours. And updated STATUSLIFETIME to 1000.
But my status is still purple. I can't figure out what I missed.
Thanks
On 4 September 2014 00:14, Ricardo L. <rltexas1 at gmail.com> wrote:
I changes the tasks to every 6 hours. And updated STATUSLIFETIME to 1000.
That's over 16 hours. Quite a lot. I suppose that's less than 3 cycles, so makes sense.
But my status is still purple. I can't figure out what I missed.
It will stay purple until the next update. Or after the change, did it go green and then purple again?
What task did you change to 6 hours? Can you give the updated section of the config file?
Which tests are purple? Are any tests not purple?
I don't think you would need to reload xymonlaunch after altering xymonserver.cfg, because I think each task that runs will read the updated file. But it couldn't hurt to restart I suppose.
J
Thanks
I did restart after updating the config files.
You mentioned that it will stay purple until the next update. I thought the purpose of STATUSLIFETIME was so a tests with long intervals didn't to purple ?
In the tasks.cfg I upped the interval for xymon network tests. But will also be making it longer for some custom ext scripts.
Thanks
On 4 September 2014 13:31, Ricardo L. <rltexas1 at gmail.com> wrote:
You mentioned that it will stay purple until the next update. I thought the purpose of STATUSLIFETIME was so a tests with long intervals didn't to purple ?
Yes, tests with long intervals stay non-purple for longer. But tests that were already purple before you changed STATUSLIFETIME won't change from purple until the next update. It's a once-off.
Unless you set the time qualifier (like 1000m), I think it defaults to seconds so using just 1000=~17 minutes (a bit less). You can use status+6h if you want to do 6 for the lifetime. You also need to make sure that is set in the clientlocal,cfg file as well. I don't have access to a system with the manpages at the moment but fairly certain that is the case.
On Wed, Sep 3, 2014 at 10:14 AM, Ricardo L. <rltexas1 at gmail.com> wrote:
Hi
I am just using xymon to do some low level netwoek monitoring.
I changes the tasks to every 6 hours. And updated STATUSLIFETIME to 1000.
But my status is still purple. I can't figure out what I missed.
Thanks
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Ok I'll try adding the m to the 1000 but on the info description to the right of that field if said it was in minutes.
Now I did not update clientlocal,cfg maybe that is the missing peice. The reason I didn't update it was because all is the tests as of now is server side only / agent less.
Where would I specify status+6h?
On 4 September 2014 13:47, Ricardo L. <rltexas1 at gmail.com> wrote:
Ok I'll try adding the m to the 1000 but on the info description to the right of that field if said it was in minutes.
Correct. Many configurable quantities are in seconds and allow specifying a qualifier like this. However STATUSLIFETIME is not one of them. The code assumes it's an integer value with no qualifier. If you add an "m" it will probably ignore the setting.
Now I did not update clientlocal,cfg maybe that is the missing peice. The
reason I didn't update it was because all is the tests as of now is server side only / agent less.
That shouldn't apply to the network tests.
Where would I specify status+6h?
Only if you have your own scripts that send status messages. If all you are doing is using network tests, then those will have the validity as per STATUSLIFETIME because xymonnet creates the "status+<validity>" as part of its status message.
J
participants (3)
-
jlaidman＠rebel-it.com.au
-
rltexas1＠gmail.com
-
solitaryr＠gmail.com