Hi

I don't know if it has been already asked, but i ask :)

i d like to know if it s possible to make a trigger for disk space when the space grows very fast. (that means there is a problem sometimes).

For instance, if the disk space grows up to 20% in a small time (to specify) , there is an alert (warning or red alert).

Thanks

Regards, Nicolas LIENARD

Thanks for answear; i ll make an external script as Rolf suggered.

Regards, Nicolas

No. Hobbit currently only warns on the current level, not the trend in how fast disk utilisation is growing.

Regards, Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

Instead of storing the history data in temporary files, you could just fetch the data out of the RRD files.

-----Original Message----- From: Rolf Schrittenlocher [mailto:Schrittenlocher at rz.uni-frankfurt.de] Sent: Tuesday, August 29, 2006 5:59 AM To: hobbit at hswn.dk Subject: Re: [hobbit] new feature ?

Hi Nicolas,

it seems to be not too complicate to write a custom script for that purpose. Store the output of df -k in a temporary file, check the difference in an intervall and alert if something is growing fast.

...

Hi

I don't know if it has been already asked, but i ask :)

i d like to know if it s possible to make a trigger for disk space when the space grows very fast. (that means there is a problem sometimes).

For instance, if the disk space grows up to 20% in a small time (to specify) , there is an alert (warning or red alert).

Thanks

Regards, Nicolas LIENARD

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Mit freundlichen Gruessen Rolf Schrittenlocher

HRZ/BDV, Senckenberganlage 31, 60054 Frankfurt Tel: (49) 69 - 798 28908 Fax: (49) 69 - 798 28817 LBS: lbs-f at mlist.uni-frankfurt.de Persoenlich: schritte at rz.uni-frankfurt.de

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

Charles Goyard schrieb:

You can use the "time offset" in the CPU column to make sure your hosts are on-time. The gain is that all you hosts don't cry when you restart your ntp server, and you have one less script to maintain.

That's a good idea. I haven't discovered this feature, yet.

Thanks.

Dirk Kastens

On 8/29/06, Henrik Stoerner <henrik at hswn.dk> wrote:

On Tue, Aug 29, 2006 at 11:00:54AM +0200, Dirk Kastens wrote:

...

before updating our hobbit server to version 4.2.0, I tested the ntp configuration with the bb-ntp-1_4.sh script on the client nodes. When I now configure the server to use the ntp network test instead, I realize that this doesn't work with most of our RedHat clients. I get the response

ntpdate -u -q -p 2 a.b.c.d server a.b.c.d, stratum 0, offset 0.000000, delay 0.00000 29 Aug 10:53:26 ntpdate[3509]: no server suitable for synchronization found

Funny, this is the second question about NTP checking this morning.

...

The network test works with all AIX clients and with older RedHat clients. The manual page of ntpdate on a RedHat machine says, that "the ntpdate program is to be retired from this distribution". Is there another way of testing the ntp synchronisation from the server side or do I still have to use the bb-ntp.sh script?

Currently you have to use client-side scripts if the ntpdate program does not work.

For the 4.2.0 release, ntp checking really was not on my mind. It would make lots of sense to include the output from ntpq -c "rv 0" in the client output, and then process this on the server to pickup the current synchronization status, stratum and clock offset, with suitable configuration settings to trigger an alert if it loses sync or the stratum gets too high.

You can regard that as a promise to improve this in a later version.

Excellent!

Regards,

Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu