1.2.3.4 prod-db2 # ssh pulldata TRENDS:*,disk:disk|disk1,vmstat:vmstat1 DOWNTIME=*:0159:0400:Database_Resync 1.2.3.5 prod-db3 # ssh pulldata TRENDS:*,disk:disk|disk1,vmstat:vmstat1 DOWNTIME=*:0159:0400:Database_Resync
My hobbitd status currently says: "Invalid timespec - expected 4 digits, got: 'Database_Resync'"
I see nothing wrong with my syntax, the bb-hosts man page says: DOWNTIME=day:starttime:endtime:cause[,day:starttime:endtime:cause]
What am I doing wrong? Also, is it possible to specify DOWNTIME per service? Because I do not want to put the entire host into maint mode, just the "procs", in this case.
On Mon, Oct 09, 2006 at 01:21:32PM -0700, Charles Jones wrote:
1.2.3.4 prod-db2 # ssh pulldata TRENDS:*,disk:disk|disk1,vmstat:vmstat1 DOWNTIME=*:0159:0400:Database_Resync 1.2.3.5 prod-db3 # ssh pulldata TRENDS:*,disk:disk|disk1,vmstat:vmstat1 DOWNTIME=*:0159:0400:Database_Resync
My hobbitd status currently says: "Invalid timespec - expected 4 digits, got: 'Database_Resync'"
This was the subject of another mail here a few days ago. Basically, the code and the docs are not in sync. When you list a cause for the downtime, you must also specify the tests that this applies to. So for all tests, it would be DOWNTIME=*:*:0159:0400:Database_Resync with the first "*" being the service.
Regards, Henrik
participants (2)
-
henrik＠hswn.dk
-
jonescr＠cisco.com