Xymon Mailing List Archive search

Invalid timespec from DOWNTIME definition

2 messages in this thread

list W.J.M. Nelis · Fri, 20 Jun 2008 16:49:06 +0200 ·
Hello,

On 2008.02.05 user-78bb6d5d9024@xymon.invalid wrote:
Hi,
 [Skipping two questions]

  Finaly, the last question :
    2008-02-05 13:43:19 Invalid timespec - expected 4 digits, got: 'BackUP'
    2008-02-05 13:43:19 Bad timespec (missing colon or wrong weekdays): 1
    2008-02-05 13:43:22 Invalid timespec - expected 4 digits, got: 'BackUP'
    2008-02-05 13:43:22 Bad timespec (missing colon or wrong weekdays): 1
    2008-02-05 13:43:24 Invalid timespec - expected 4 digits, got: 'BackUP'
    2008-02-05 13:43:24 Bad timespec (missing colon or wrong weekdays): 1

  Here is my bb-hosts configuration file :
    1.2.3.4  server1 # conn ssh  DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.5  server2 # conn ssh  DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.6  server3 # conn ssh  DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.7  server4 # conn ssh  DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP

  Did I configured something wrong ?
The same goes for me. Hobbit is reporting this error quite some time now, but since
the last restart it also reports the error in the hobbitd test, under the heading
"Latest error messages", causing the hobbit server to become yellow. 

Changing the cause field in a DOWNTIME specification resulted in the same change in the error,
which is reported both in hobbitd.log and in the hobbitd test.

We are running Hobbit version 4.3.0-20070727. Is there another way of solving this
problem other than moving to the latest snapshot?

Kind regards,
  Wim Nelis.


**********************************************************************************************
Our disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for this e-mail message.
**********************************************************************************************
list Darin D [eit] Dugan · Fri, 20 Jun 2008 10:45:09 -0500 ·
Keep checking the archives. You need to specify both the service and
reason if specifying either.
http://hswn.dk/hobbiton/2008/06/msg00088.html
http://hswn.dk/hobbiton/2008/05/msg00020.html

Cheers.
D
quoted from W.J.M. Nelis

-----Original Message-----
From: W.J.M. Nelis [mailto:user-f4ccfde53c0d@xymon.invalid] 
Sent: Friday, June 20, 2008 9:49 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Invalid timespec from DOWNTIME definition

Hello,

On 2008.02.05 user-78bb6d5d9024@xymon.invalid wrote:
Hi,
 [Skipping two questions]

  Finaly, the last question :
    2008-02-05 13:43:19 Invalid timespec - expected 4 digits, got:
'BackUP'
    2008-02-05 13:43:19 Bad timespec (missing colon or wrong
weekdays): 1
    2008-02-05 13:43:22 Invalid timespec - expected 4 digits, got:
'BackUP'
    2008-02-05 13:43:22 Bad timespec (missing colon or wrong
weekdays): 1
    2008-02-05 13:43:24 Invalid timespec - expected 4 digits, got:
'BackUP'
    2008-02-05 13:43:24 Bad timespec (missing colon or wrong
weekdays): 1

  Here is my bb-hosts configuration file :
    1.2.3.4  server1 # conn ssh
DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.5  server2 # conn ssh
DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.6  server3 # conn ssh
DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
    1.2.3.7  server4 # conn ssh
DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP
  Did I configured something wrong ?
The same goes for me. Hobbit is reporting this error quite some time
now, but since
the last restart it also reports the error in the hobbitd test, under
the heading
"Latest error messages", causing the hobbit server to become yellow. 

Changing the cause field in a DOWNTIME specification resulted in the
same change in the error,
which is reported both in hobbitd.log and in the hobbitd test.

We are running Hobbit version 4.3.0-20070727. Is there another way of
solving this
problem other than moving to the latest snapshot?

Kind regards,
  Wim Nelis.


************************************************************************
**********************
Our disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for this
e-mail message.
************************************************************************
**********************