I'm working my way through a small rollout of hobbitclient on some AIX 5.3 boxen to replace the BB client.

At present, I am having some issues with disk alerts, especially for NFS mounted drives.

As Henrik probably noticed, AIX is nice enough to *not* include the option for specifying file system types in it's df command.  Well... it does in the sysv version but that won't let you get the results in kb :-)  So if I get a full disk on the NFS server, all the NFS clients let me know about it too!

Would it be possible to use a DEFAULT regex to exclude any lines with a : in them?  Something like...

DISK  %*:.* 101 102

Although my perl regex experience is a bit light... so any clarification would be appreciated!

Also - can you have multiple DISK lines undet the DEFAULT tag?  The man page doesn't say much either way, although I've got it working fine on one host entry for the PROC status

Regards, Andy.

#####################################################################################

This email is intended for the person to whom it is addressed only. If you are not the intended recipient, do not read, copy or use the contents in any way. The opinions expressed may not necessarily reflect those of ZESPRI Group of Companies ('ZESPRI').

While every effort has been made to verify the information contained herein, ZESPRI does not make any representations as to the accuracy of the information or to the performance of any data, information or the products mentioned herein. ZESPRI will not accept liability for any losses, damage or consequence, however, resulting directly or indirectly from the use of this e-mail/attachments. #####################################################################################

*crickets*

Nobody commented on this issue...can anyone else confirm the behavior?

-Charles

Charles Jones wrote:

I just built a new hobbit server with 4.1.2p1 and I am still seeing the behavior of, if you enable or disable "all" services for a host, it does not trigger the NOTICE rule and thus no email is sent out.
Below are the last 2 messages I sent reporting this problem.

-Charles

Charles Jones wrote:

...

I am stiil trying to troubleshoot my missing enable messages, so I deleted the NOTICE rule mentioned below and created a new rule:

Send me notice alerts of enable and disable

HOST=* MAIL me at mydomain.com NOTICE NOALERT

I then proceeded to disable 2 services on a host. I observed that I received a disable notification, both by actual receipt of the email, and by tail -f /var/log/maillog.

Then I enabled the services (by enabling "ALL" for that host), and...nothing. No mail was sent, as verified by my tailing of the log.

I then immediately disabled ALL services on another host, and no mail was sent. I then immediately re-enabled ALL services on that same host, and no mail was sent.

Through testing I discovered that when you disable or enable _"ALL"_ services on a host, no NOTICE message is generated. If I disable or disable _individual_ services, notice messages are generated and an email is sent out.

If you need me to do further testing, let me know.

-Charles

Charles Jones wrote:

...

1. When I disable a host in hobbit, it says it was disabled by unknown at 1.2.3.4 <mailto:unknown at 1.2.3.4>. In the bb maint.pl script, it had an option to put a username, but I don't see an option to do this in the Hobbit Maint page, so is "unknown" hard coded, or does it look for it somewhere else?

2. I added the "NOTICE" rule to my hobbit-alerts.cfg

HOST=* SERVICE=* COLOR=red MAIL me at mydomain.com <mailto:me at mydomain.com> RECOVERED NOTICE

I then tested disabling the cpu service for a host, and I received an email with the disable message:

---

From: hobbit at myhost.com <mailto:hobbit at myhost.com> Sent: Wednesday, November 09, 2005 5:01 PM To: me at mydomain.com <mailto:me at mydomain.com> Subject: Hobbit servername:cpu NOTICE servername:cpu INFO Monitoring of servername:cpu has been DISABLED by unknown for 240 minutes Disabled by: unknown @ 1.2.3.4 Reason: testing disable notice

This is what I expected to get. However, I then went and re-enabled the disabled service, and I did not get an email saying it was re-enabled. I checked the /var/log/maillog to make sure that it wasn't a mail delay. There simply was no email sent about the enable. I assume this isn't normal behavior :)

-Charles