[Nagios-users] How to find MIB for OpenVMS
Hello, I have some VMS servers that I have implemented SNMP service on. I am able to successfully do an snmpwalk from my Nagios server. However my SNMP plugin is looking for a MIB that is apparently different than the one that these VMS servers use. Question: how do I find the MIB value for these VMS servers? I have a mix of OpenVMS Alpha's and Mini-Vax's. Thanks, Chris -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient wrong password
From: trm asn [mailto:trm.nag...@gmail.com]
Sent: 29 November 2010 10:48
To: Nagios Users List
Subject: Re: [Nagios-users] nsclient wrong password
On Mon, Nov 29, 2010 at 8:28 PM, Maxime Alarie mala...@processia.com
wrote:
From: trm asn [mailto:trm.nag...@gmail.com]
Sent: 27 November 2010 05:20
To: Nagios Users List
Subject: Re: [Nagios-users] nsclient wrong password
check nsc.ini for the password set the same password in nagios
command.cfg file
On Sat, Nov 27, 2010 at 2:53 AM, Maxime Alarie mala...@processia.com
wrote:
Hi, I keep getting this error and I don't know why.. When I install
nsclient on a windows macine, I provide the nagiosadmin password in the
client, as well as my nagios server IP address. For some reason, I
keep having the Invalid password error message both on nsclient.log and
on the server logs, on th e server I also have Connection Refused.
Nsclient.log:
\NSClientListener.cpp:160: Invalid password (None).
Server:
[1290806215] SERVICE ALERT: Penang;C:\ Drive
Space;UNKNOWN;HARD;4;NSClient - ERROR: Invalid password.
[1290806215] SERVICE NOTIFICATION: root;Penang;C:\ Drive
Space;UNKNOWN;notify-service-by-email;NSClient - ERROR: Invalid
password.
[1290806227] EXTERNAL COMMAND:
SCHEDULE_FORCED_HOST_CHECK;Penang;1290806226
[1290806235] SERVICE ALERT: Penang;W3SVC;UNKNOWN;HARD;4;NSClient -
ERROR: Invalid password.
[1290806235] SERVICE NOTIFICATION:
root;Penang;W3SVC;UNKNOWN;notify-service-by-email;NSClient - ERROR:
Invalid password.
[1290806275] SERVICE ALERT: Penang;CPU Load;UNKNOWN;HARD;4;NSClient -
ERROR: Invalid password.
[1290806275] SERVICE NOTIFICATION: root;Penang;CPU
Load;UNKNOWN;notify-service-by-email;NSClient - ERROR: Invalid password.
[1290806335] SERVICE ALERT: Penang;Explorer;UNKNOWN;HARD;4;NSClient -
ERROR: Invalid password.
[1290806335] SERVICE NOTIFICATION:
root;Penang;Explorer;UNKNOWN;notify-service-by-email;NSClient - ERROR:
Invalid password.
[1290806515] SERVICE ALERT: Penang;C:\ Drive
Space;CRITICAL;HARD;4;Connection refused
[1290806515] SERVICE NOTIFICATION: root;Penang;C:\ Drive
Space;CRITICAL;notify-service-by-email;Connection refused
[1290806535] SERVICE ALERT: Penang;W3SVC;CRITICAL;HARD;4;Connection
refused
[1290806535] SERVICE NOTIFICATION:
root;Penang;W3SVC;CRITICAL;notify-service-by-email;Connection refused
[1290806575] SERVICE ALERT: Penang;CPU Load;CRITICAL;HARD;4;Connection
refused
[1290806575] SERVICE NOTIFICATION: root;Penang;CPU
Load;CRITICAL;notify-service-by-email;Connection refused
What am I doing wrong here?
I don't have any password in my commands.cfg looks like this:
cat /etc/nagios3/commands.cfg
###
# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
###
# NOTIFICATION COMMANDS
# 'notify-host-by-email' command definition
define command{
command_name notify-host-by-email
command_line /usr/bin/printf %b * Nagios
*\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState:
$HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time:
$LONGDATETIME$\n | /usr/bin/mail -s ** $NOTIFICATIONTYPE$ Host Alert:
$HOSTNAME$ is $HOSTSTATE$ ** $CONTACTEMAIL$
}
# 'notify-service-by-email' command definition
define command{
command_name notify-service-by-email
command_line /usr/bin/printf %b * Nagios
*\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService:
$SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState:
$SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional
Info:\n\n$SERVICEOUTPUT$ | /usr/bin/mail -s ** $NOTIFICATIONTYPE$
Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **
$CONTACTEMAIL$
}
# HOST CHECK COMMANDS
# On Debian, check-host-alive is being defined from within the
# nagios-plugins-basic package
# PERFORMANCE DATA COMMANDS
# 'process-host-perfdata' command definition
define command{
command_name process-host-perfdata
command_line /usr/bin/printf %b
$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE
$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n
/var/lib/nagios3/host-perfdata.out
}
# 'process-service-perfdata' command definition
define command{
command_name process-service-perfdata
Re: [Nagios-users] nsclient wrong password
If you are using the standard Ubuntu apt-get install the comand
definitions are located in /etc/nagios-plugins/config you can modifiy
the check_nt command from there in the nt.cfg file
Greg Pangrazio
On Tue, Nov 30, 2010 at 8:56 AM, Maxime Alarie mala...@processia.com wrote:
From: trm asn [mailto:trm.nag...@gmail.com]
Sent: 29 November 2010 10:48
To: Nagios Users List
Subject: Re: [Nagios-users] nsclient wrong password
On Mon, Nov 29, 2010 at 8:28 PM, Maxime Alarie mala...@processia.com
wrote:
From: trm asn [mailto:trm.nag...@gmail.com]
Sent: 27 November 2010 05:20
To: Nagios Users List
Subject: Re: [Nagios-users] nsclient wrong password
check nsc.ini for the password set the same password in nagios command.cfg
file
On Sat, Nov 27, 2010 at 2:53 AM, Maxime Alarie mala...@processia.com
wrote:
Hi, I keep getting this error and I don’t know why.. When I install
nsclient on a windows macine, I provide the nagiosadmin password in the
client, as well as my nagios server IP address. For some reason, I keep
having the Invalid password error message both on nsclient.log and on the
server logs, on th e server I also have Connection Refused.
Nsclient.log:
\NSClientListener.cpp:160: Invalid password (None).
Server:
[1290806215] SERVICE ALERT: Penang;C:\ Drive Space;UNKNOWN;HARD;4;NSClient -
ERROR: Invalid password.
[1290806215] SERVICE NOTIFICATION: root;Penang;C:\ Drive
Space;UNKNOWN;notify-service-by-email;NSClient - ERROR: Invalid password.
[1290806227] EXTERNAL COMMAND: SCHEDULE_FORCED_HOST_CHECK;Penang;1290806226
[1290806235] SERVICE ALERT: Penang;W3SVC;UNKNOWN;HARD;4;NSClient - ERROR:
Invalid password.
[1290806235] SERVICE NOTIFICATION:
root;Penang;W3SVC;UNKNOWN;notify-service-by-email;NSClient - ERROR: Invalid
password.
[1290806275] SERVICE ALERT: Penang;CPU Load;UNKNOWN;HARD;4;NSClient - ERROR:
Invalid password.
[1290806275] SERVICE NOTIFICATION: root;Penang;CPU
Load;UNKNOWN;notify-service-by-email;NSClient - ERROR: Invalid password.
[1290806335] SERVICE ALERT: Penang;Explorer;UNKNOWN;HARD;4;NSClient - ERROR:
Invalid password.
[1290806335] SERVICE NOTIFICATION:
root;Penang;Explorer;UNKNOWN;notify-service-by-email;NSClient - ERROR:
Invalid password.
[1290806515] SERVICE ALERT: Penang;C:\ Drive
Space;CRITICAL;HARD;4;Connection refused
[1290806515] SERVICE NOTIFICATION: root;Penang;C:\ Drive
Space;CRITICAL;notify-service-by-email;Connection refused
[1290806535] SERVICE ALERT: Penang;W3SVC;CRITICAL;HARD;4;Connection refused
[1290806535] SERVICE NOTIFICATION:
root;Penang;W3SVC;CRITICAL;notify-service-by-email;Connection refused
[1290806575] SERVICE ALERT: Penang;CPU Load;CRITICAL;HARD;4;Connection
refused
[1290806575] SERVICE NOTIFICATION: root;Penang;CPU
Load;CRITICAL;notify-service-by-email;Connection refused
What am I doing wrong here?
I don’t have any password in my commands.cfg looks like this:
cat /etc/nagios3/commands.cfg
###
# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
###
# NOTIFICATION COMMANDS
# 'notify-host-by-email' command definition
define command{
command_name notify-host-by-email
command_line /usr/bin/printf %b * Nagios
*\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState:
$HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time:
$LONGDATETIME$\n | /usr/bin/mail -s ** $NOTIFICATIONTYPE$ Host Alert:
$HOSTNAME$ is $HOSTSTATE$ ** $CONTACTEMAIL$
}
# 'notify-service-by-email' command definition
define command{
command_name notify-service-by-email
command_line /usr/bin/printf %b * Nagios
*\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService:
$SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState:
$SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional
Info:\n\n$SERVICEOUTPUT$ | /usr/bin/mail -s ** $NOTIFICATIONTYPE$ Service
Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ ** $CONTACTEMAIL$
}
# HOST CHECK COMMANDS
# On Debian, check-host-alive is being defined from within the
# nagios-plugins-basic package
# PERFORMANCE DATA COMMANDS
# 'process-host-perfdata' command definition
define command{
command_name process-host-perfdata
command_line
Re: [Nagios-users] check scheduling when checks are inhibited.
Andreas, Thanks for your reply to my earlier message. I've done some testing and some more thinking on this since then: On 11/23/2010 03:50 AM, Andreas Ericsson wrote: On 11/22/2010 10:41 PM, Paul M. Dubuc wrote: We're using Nagios 3.2.3 for simulation of monitoring load in a load test environment as well as for monitoring production services. I've notices some interesting behavior in the way Nagios schedules checks when checks are inhibited either though the CGI Process Commands or by setting a check_period timeperiod that inhibits checks during regularly scheduled down times. Normally Nagios seems to spread out host and service checks evenly over time but when checks are stopped with the Process Command, Nagios seems to reschedule checks so that they are bunched up much closer together. This creates alternating periods of densely scheduled and more sparsely scheduled checks that seem to persist when checks are turned on again. It has a noticeable effect in our load testing. The only way--or the quickest way--to get Nagios to smooth out the schedule again is to stop the process completely until all the scheduled check times have passed. In testing Nagios monitoring of our production services, if I use the check_period to inhibit checks during our down times, I notice that as the downtime approaches, ALL checks are rescheduled for the exact time that the downtime ends (according to the check_period). This creates a big spike in monitoring activity after the downtime. One way to avoid this, I think, is to let checks run during the down times but inhibit notifications instead by using the timeperiod to define a notification_period. But I wonder if this bunching up of the schedule when using check_periods is ever a desirable behavior. I have some plans to make Nagios spread the checks with a randomized interleave factor so that a check scheduled to run once every 5 minutes can be run anywhere between 4m 30s and 5m 0s after it last ran. The 30 second random-spread would be the default and it would otherwise be configurable. Another thing worth looking into is to make services to the same host not run simultaneously, in case the checked server is expected to be loaded heavily it may not play nicely with 30-40 checks fired at it at once. Here's another suggestion: An option that would tell Nagios to stagger the scheduling of service checks when the check_period resumes. Instead of scheduling all the checks for the exact time that the next check_period begins, add an amount of time equal to the time past the check_period ending that the service would have run if the check_period hadn't disabled checks. For example, If I have a check period that is from 9:00 to 17:00 every day. A service running every 5 minutes that runs at 16:57:14 would normally run at 17:02:14 if the check_period did not end at 17:00. This check would be scheduled to run at 9:02:14 the next day instead of 9:00:00. This should keep all checks staggered by the same amount of time in the schedule once the check_period resumes. I think this would be an ideal solution to the problem. Using the auto_rescheduling options (discussed below) seems to help a little bit but not as much as I'd hoped. You really should be using scheduled downtime for regular downtime though. There are pre-hacked solutions to automagically reschedule re-occurring downtime. Ninja supports it out of the box as of the latest version (or possibly latest git). There are some cases where we really should not be running the checks during down times because of the extra load they put on our system when they fail. (Checks are still run during down times, if I'm not mistaken, only notifications are inhibited.) Many of our checks fail in this case by timing out and they use relatively scarce (shared) and resource intensive processes (web browser sessions run under SeleniumRC). Timeouts tend to be long for these checks so there is more contention for these processes when all the checks using them start failing, and they're run more often until they all go into a 'hard' failure state, etc. Maybe we can live with this, but it would be easier on the system to just inhibit checks we know are going to fail during certain regularly scheduled down times. These aren't critical issues for us since we can work around them procedurally. That's good to hear. But I wonder if there his a way to prevent the scheduled checks from getting bunched together like this if/when you need to inhibit checks for a time while keeping Nagios running. Maybe the auto_rescheduling options in the nagios.cfg are meant to address this, but they have a potentially negative effect on performance according to the comments around them in the file. The below text is what I'd call educated speculation after having thrown a quick glance at the code. I might be completely wrong, but I don't think so. Not
