Weird enough, the script didn't fire... but I found these errors in rrd-data.log just a few moments before I got an alert:
2005-10-25 06:13:54 RRD error updating /usr/local/hobbit/data/rrd/host.foobar.com/vmstat.rrd from 127.0.0.1: illegal attempt to update using time 1130213634 when last update time is 1130213634 (minimum one second step)
2005-10-25 06:18:56 RRD error updating /usr/local/hobbit/data/rrd/host.foobar.com/netstat.rrd from 127.0.0.1: illegal attempt to update using time 1130213936 when last update time is 1130213936 (minimum one second step)
2005-10-25 06:18:56 RRD error updating /usr/local/hobbit/data/rrd/host.foobar.com/vmstat.rrd from 127.0.0.1: illegal attempt to update using time 1130213936 when last update time is 1130213936 (minimum one second step)
2005-10-25 06:34:05 RRD error updating /usr/local/hobbit/data/rrd/host.foobar.com/netstat.rrd from 127.0.0.1: illegal attempt to update using time 1130214845 when last update time is 1130214845 (minimum one second step)
2005-10-25 06:34:05 RRD error updating /usr/local/hobbit/data/rrd/host.foobar.com/vmstat.rrd from 127.0.0.1: illegal attempt to update using time 1130214845 when last update time is 1130214845 (minimum one second step)
And some more about other graphs in the rrd-status.log file.
You just might be right Lars... seems to look like timing.
I just don't understand why my script didn't fire, this would give more certainty about the timing problem. The data should be normal.
Arnoud
Arnoud Post wrote:
I have just made a script which makes a copy of the clientdata file when an alert is seen. Now I just have to wait and see...
#!/bin/sh
#
CP="/bin/cp"
BBHOME="/usr/local/hobbit"
DATE=`/bin/date "+%Y%M%d.%H%M%S"`
$CP $BBHOME/client/tmp/msg.txt $BBHOME/client/logs/clientdata.$DATE and added in hobbit-alerts.cfg:
HOST=www.foobar.com
SCRIPT /usr/local/hobbit/server/bin/copy_clientdata.sh Grt,
Arnoud
lars ebeling wrote:
On Mon, Oct 24, 2005 at 10:52:29AM +0200, Arnoud Post wrote:
I use Hobbit client and server, but the data was not parsed propperly. This
happend 2 times now.
The disk check gives this error:
- Filesystems NOT ok
red Expected string (Capacity and Mounted) not found in df output header
This happens me at least once a day at the hobbitserver. I have written abou this Aug 16. I think there are timing problems when the client-script is running. This is what I got.
Tue Aug 16 13:56:37 METDST 2005 - Filesystems NOT ok
Expected string (Capacity and Mounted) not found in df output header
System: leopg9 Tue Aug 16 13:56:37 2005