Questions about Enable/Disable/NOTICE 🔗 link

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 user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid> RECOVERED NOTICE
 I then tested disabling the cpu service for a host, and I received an email with the disable message:
From: user-d5279360b102@xymon.invalid <mailto:user-d5279360b102@xymon.invalid>
Sent: Wednesday, November 09, 2005 5:01 PM
To: user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid>
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

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.
#####################################################################################

Just a follow up on my own thread...

Andy France wrote on 10/11/2005 05:25:27 p.m.:

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!

I've had a look at how BB resolves this issue.  They grep the df output
for
lines that begin with /dev.

This will work fine for me as all my LV's (logical volumes), whether
locally attached SCSI disks or fibre attached FAStT SAN disks, follow
this
convention... which is kind of obvious seeing as i never noticed any
problems with the BB client! ;-)

Can anyone else confirm that all AIX systems will follow this
convention?  I'm relatively new to AIX and only run 5.2 and 5.3.  I
therefore feel I'm not qualified to categorically state that all local
filesystems will be created on logical volumes.  Does AIX actually enfore
the use of LVM?

At this point, I've made the following change to my copies of
hobbitclient-aix.sh

df -Ik | sed ...
*becomes*
df -Ik | grep '^/dev' | sed...

Would anyone have objections to getting the source updated to match by
Henrik?

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!

This would obviously become a bit redundant :-)

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.

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

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

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.
#####################################################################################

Andy France a écrit :

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!

-----Original Message-----
From: Andy France [mailto:user-ee2a9e4eaf57@xymon.invalid]
Sent: Thursday, November 10, 2005 3:39 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Fw: [hobbit] hobbitclient, disk and AIX


Just a follow up on my own thread...

Andy France wrote on 10/11/2005 05:25:27 p.m.:

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!

I've had a look at how BB resolves this issue.  They grep the df output for
lines that begin with /dev.

This will work fine for me as all my LV's (logical volumes), whether
locally attached SCSI disks or fibre attached FAStT SAN disks, follow this
convention... which is kind of obvious seeing as i never noticed any
problems with the BB client! ;-)

Can anyone else confirm that all AIX systems will follow this
convention?  I'm relatively new to AIX and only run 5.2 and 5.3.  I
therefore feel I'm not qualified to categorically state that all local
filesystems will be created on logical volumes.  Does AIX actually enfore
the use of LVM?

At this point, I've made the following change to my copies of
hobbitclient-aix.sh

df -Ik | sed ...
  *becomes*
df -Ik | grep '^/dev' | sed...

Would anyone have objections to getting the source updated to match by
Henrik?

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!

This would obviously become a bit redundant :-)

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.
############################################################################
#########

Andy France <user-ee2a9e4eaf57@xymon.invalid> wrote on 10/11/2005 09:38:34 p.m.:

Just a follow up on my own thread...

Andy France wrote on 10/11/2005 05:25:27 p.m.:

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!

I've had a look at how BB resolves this issue.  They grep the df output
for
lines that begin with /dev.

This will work fine for me as all my LV's (logical volumes), whether
locally attached SCSI disks or fibre attached FAStT SAN disks, follow
this
convention... which is kind of obvious seeing as i never noticed any
problems with the BB client! ;-)

Can anyone else confirm that all AIX systems will follow this
convention?  I'm relatively new to AIX and only run 5.2 and 5.3.  I
therefore feel I'm not qualified to categorically state that all local
filesystems will be created on logical volumes.  Does AIX actually
enfore
the use of LVM?

At this point, I've made the following change to my copies of
hobbitclient-aix.sh

df -Ik | sed ...
*becomes*
df -Ik | grep '^/dev' | sed...

Whoops!

df -Ik | grep -E '^/dev'\|'^Filesystem' | sed...

Would anyone have objections to getting the source updated to match by
Henrik?

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!

This would obviously become a bit redundant :-)

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.

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

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

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.
#####################################################################################

-----Original Message-----
From: Frédéric Mangeant [mailto:user-b6ea1d850181@xymon.invalid] 
Sent: Thursday, November 10, 2005 3:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] hobbitclient, disk and AIX

Andy France a écrit :

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!

Hi

you can install GNU coreutils 
(ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/coreutils/coreutils-5.2.1-1.aix5.1.ppc.rpm), 
they provide some useful GNU commands like df :

$ /usr/linux/bin/df --help
[...]
  -l, --local           limit listing to local filesystems
[...]

I'm using this with BB clients on AIX :

DF="/usr/linux/bin/df -h -l"

Regards,

-- 

Frédéric Mangeant

Steria EDC Sophia-Antipolis

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 user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid> RECOVERED NOTICE
 I then tested disabling the cpu service for a host, and I received an email with the disable message:
From: user-d5279360b102@xymon.invalid <mailto:user-d5279360b102@xymon.invalid>
Sent: Wednesday, November 09, 2005 5:01 PM
To: user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid>
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

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 user-b75305ea6ec0@xymon.invalid 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 user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid> RECOVERED NOTICE
 I then tested disabling the cpu service for a host, and I received an email with the disable message:
From: user-d5279360b102@xymon.invalid <mailto:user-d5279360b102@xymon.invalid>
Sent: Wednesday, November 09, 2005 5:01 PM
To: user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid>
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

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 user-b75305ea6ec0@xymon.invalid 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 user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid> RECOVERED NOTICE
 I then tested disabling the cpu service for a host, and I received an email with the disable message:
From: user-d5279360b102@xymon.invalid <mailto:user-d5279360b102@xymon.invalid>
Sent: Wednesday, November 09, 2005 5:01 PM
To: user-b75305ea6ec0@xymon.invalid <mailto:user-b75305ea6ec0@xymon.invalid>
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