Problem Solved,
I put DOWNTIME=cpu:*:2300:0750:"Backup",vmio:*:2300:0750:" Backup",procs:1:1000:1300:"Test" when the correct is DOWNTIME=cpu:*:2300:0750:"Backup",vmio:*:2300:0750:"Backup"*;* procs:1:1000:1300:"Test"
change the , to ;
Att
2014-03-03 13:34 GMT-03:00 Torsten Richter <bb4 at richter-it.net>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Bruno,
normally this should work. What if you remove the quotation marks?
Cheers Torsten
On 03.03.2014 16:06, Bruno Deschamps wrote:
I have a problem here using 3 DOWNTIMES:
DOWNTIME=cpu:*:2300:0750:"Backup",vmio:*:2300:0750:"Backup",procs:1:1000:1300:"Test"
There is any wrong configuration on my conf? Anyone has something like this working?
2014-02-12 17:30 GMT-02:00 Mike Burger <mburger at bubbanfriends.org>:
forwarding to the list as well.
---------- Ursprüngliche Nachricht ---------- Von: "bb4 at richter-it.net" <bb4 at richter-it.net> An: Mike Burger <mburger at bubbanfriends.org> Datum: 12. Februar 2014 um 11:11 Betreff: Re: [Xymon] Multiple schedules for DOWNTIME not displaying
in
info
Mike Burger <mburger at bubbanfriends.org> hat am 11. Februar 2014 um 19:59 geschrieben:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Mike, > > I had this problem too. > It seems, if you only have one scheduled downtime then spaces are no > problem but if you have more than one ... well it helps replacing the > spaces with underscores '_'. At least it worked for me and all scheduled > downtimes now show up on top of the info page. > > HTH > Torsten > > On 11.02.2014 17:41, Mike Burger wrote: >> I've got a server for which I want 2 different DOWNTIME schedules...one >> for "cpu" and one for "procs". >> >> The example on the hosts.cfg man page >> (http://www.xymon.com/xymon/help/manpages/man5/hosts.cfg.5.html ) >> indicates >> that the proper syntax for DOWNTIME is: >> >>
DOWNTIME=columns:day:starttime:endtime:cause[,columns:day:starttime:endtime:cause]
>> >> Following that example, I've set it up like so: >> >> <ip address> <hostname> # OS:aix >> disk,files,cpu,memory,msgs,ports,procs >> NOCOLUMNS:inode DOWNTIME=procs:*:2159:0030:"Nightly dwmain and dwstage >> database backups",cpu:*:0000:2359:"CPU Utilization due to daily jobs" >> >> But when I go to the info page, I see: >> >> Planned downtime: All days:2159:0030 (status:procs) (cause:Nightly >> dwmain >> and dwstage database backups) >> >> and at the bottom: >> >> Other tags: OS:aix disk,files,cpu,memory,msgs,ports,procs >> NOCOLUMNS:inode >> ,cpu:*:0000:2359:CPU Utilization due to daily jobs >> >> Should I not see both parts of the DOWNTIME line in the "Planned >> downtime" >> area on the client's info page? I've noticed this behavior in both >> 4.3.15 >> and 4.3.16 (I'm only trying to add this multi-schedule for the first >> time, >> today).
Thanks, Torsten.
Did the schedules work, though, with the spaces in place (i.e. was it just an issue with the aesthetics) or did putting the the underscores ("_") in cause the schedule to properly function, too?
-- Mike Burger http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
Hi Mike,
as far as I remember the schedules did not work. At least the second one didn't. So it was more than an aesthetics issue.
Cheers Torsten
Following this, I added the "_" to both schedules' "cause" sections, and it worked as expected.
Thanks, Torsten.
Mike Burger http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
+---------------------------------------------------------+ | E-mail : bb4 [at] richter-it.net | | | | Homepage: http://www.richter-it.net/ | +---------------------------------------------------------+ Download my public key from: http://gpg-keyserver.de/pks/lookup?search=0x899093AC&op=get -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32)
iEYEARECAAYFAlMUrzAACgkQ7DlmxomQk6zQFQCfexG2ZiQHPI4QcoZA5QykBSOm NjwAoLZmCmoRkhtl9AW+Sx8+GIEqCy/d =5U4T -----END PGP SIGNATURE-----