RE: [Nagios-devel] check_disk behaviour for SAN hiccups
Posted: Wed Jun 18, 2003 1:40 pm
Sorry, I should have specified the incantation.
Yes, I was specifying the specific partition.
jc
> -----Original Message-----
> From: Subhendu Ghosh [mailto:[email protected]]
> Sent: Wednesday, June 18, 2003 4:37 PM
> To: Carroll, Jim P [Contractor]
> Cc: [email protected]
> Subject: Re: [Nagios-devel] check_disk behaviour for SAN hiccups
>=20
>=20
>=20
> Were you asking for the specific partition with check_disk?
> If so - it should probably be a critical instead of warning...
>=20
> -sg
>=20
>=20
> On Wed, 18 Jun 2003, Carroll, Jim P [Contractor] wrote:
>=20
> > A firmware upgrade was applied to our Hitachi SAN last=20
> night. One of the hosts attached to it burped and didn't=20
> recover. Here's one of the alerts that Nagios gave us:
> >=20
> > [quote]
> > ***** Nagios 1.1 *****
> >=20
> > Notification Type: PROBLEM
> >=20
> > Service: Space on /ora_backup
> > Host: itdmln16
> > Address: itdmln16
> > State: WARNING
> >=20
> > Date/Time: Tue Jun 17 22:52:19 CDT 2003
> >=20
> > Additional Info:
> >=20
> > Disk /ora_backup not mounted or nonexistant
> > [end quote]
> >=20
> > Should this only be a 'warning'?
> >=20
> > When one of my peers tried to do an 'ls' on the root=20
> directory, he got the brief listing of the various files,=20
> directories and mount points. When he tried to do an "ls=20
> -l", he got a couple I/O errors and then the long listing for=20
> all the files, directories and mount points, minus the 2=20
> SAN-based mount points.
> >=20
> > Granted, this is a funky result for a single system; all=20
> the other hosts connected to the same SAN didn't have any=20
> such problem. Still, it would have been nice if the plugin=20
> had returned a 'critical' instead of a 'warning', as that=20
> notification would have also been sent to the on-call pager.
> >=20
> > jc
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU=20
> Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10%=20
> Monthly Commission!
> > INetU Dedicated Managed Hosting=20
http://www.inetu.net/partner/index.php
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>=20
--=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Yes, I was specifying the specific partition.
jc
> -----Original Message-----
> From: Subhendu Ghosh [mailto:[email protected]]
> Sent: Wednesday, June 18, 2003 4:37 PM
> To: Carroll, Jim P [Contractor]
> Cc: [email protected]
> Subject: Re: [Nagios-devel] check_disk behaviour for SAN hiccups
>=20
>=20
>=20
> Were you asking for the specific partition with check_disk?
> If so - it should probably be a critical instead of warning...
>=20
> -sg
>=20
>=20
> On Wed, 18 Jun 2003, Carroll, Jim P [Contractor] wrote:
>=20
> > A firmware upgrade was applied to our Hitachi SAN last=20
> night. One of the hosts attached to it burped and didn't=20
> recover. Here's one of the alerts that Nagios gave us:
> >=20
> > [quote]
> > ***** Nagios 1.1 *****
> >=20
> > Notification Type: PROBLEM
> >=20
> > Service: Space on /ora_backup
> > Host: itdmln16
> > Address: itdmln16
> > State: WARNING
> >=20
> > Date/Time: Tue Jun 17 22:52:19 CDT 2003
> >=20
> > Additional Info:
> >=20
> > Disk /ora_backup not mounted or nonexistant
> > [end quote]
> >=20
> > Should this only be a 'warning'?
> >=20
> > When one of my peers tried to do an 'ls' on the root=20
> directory, he got the brief listing of the various files,=20
> directories and mount points. When he tried to do an "ls=20
> -l", he got a couple I/O errors and then the long listing for=20
> all the files, directories and mount points, minus the 2=20
> SAN-based mount points.
> >=20
> > Granted, this is a funky result for a single system; all=20
> the other hosts connected to the same SAN didn't have any=20
> such problem. Still, it would have been nice if the plugin=20
> had returned a 'critical' instead of a 'warning', as that=20
> notification would have also been sent to the on-call pager.
> >=20
> > jc
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU=20
> Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10%=20
> Monthly Commission!
> > INetU Dedicated Managed Hosting=20
http://www.inetu.net/partner/index.php
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>=20
--=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]