Hi Team,
Is there any other way or plugin available to monitor drivers of a LDAP server.
Regards,
Hoegh
LDAP Monitoring in Nagios
Re: LDAP Monitoring in Nagios
check_dxml_drvstate is the only one I found that is designed specifically for driver state. The script is just a wrapper for the dxcmd command so I would try running the dxcmd command directly and there may be options you can pass it to get the information desired and edit the script accordingly.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: LDAP Monitoring in Nagios
Our Nagios is installed on Linux Based Machine & LDAP Server is installed on Windows OS.cdienger wrote:check_dxml_drvstate is the only one I found that is designed specifically for driver state.
Just for clearification, willl this plugin check_dxml_drvstate work in our scenario.
Or this plugin work only for LDAP servers installed on LInux Based Machine.
Also tried to view its coding, we found that there are Linux Based file system directories are used for LogFiles etc.
& one more LIne was there
SERVER = 127.0.0.1
probably this may be the reason due to which whenever we run this command on our Linux Based Nagios, It tries to find dxcmd command on Nagios server instead of LDAP server.
Code: Select all
[root@OSLMSnagios libexec]# ./check_dxml_drvstate -s oslsec015
which: no dxcmd in (/usr/java/jre1.8.0_181/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
which: no ndsconfig in (/usr/java/jre1.8.0_181/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
./check_dxml_drvstate: line 330: get: command not found
./check_dxml_drvstate: line 334: get: command not found
Driver could not be checked due to an UNKNOWN ERROR (Error code 127)
Few code of Plugin just to clarify my points:
Code: Select all
VERSION="2.1, 2014-03-18"
PROGNAME=`basename $0`
CMDLINE="$0 $*"
DXCMD=`which dxcmd`
NDSCONFIG=`which ndsconfig`
STATFILE="/tmp/$PROGNAME.tmp"
INVERT=false
INVERTMSG='.'
OUTPUT=LONG
BR=" "
NL=
STATE_OK=0
STATE_WARNING=1
STATE_CRITICAL=2
STATE_UNKNOWN=3
STATE_DEPENDENT=4
TREE=
TAODIR=
HBATTR_LDAPNAME="aieLastHeartbeat"
TJATTR_LDAPNAME="aieLastTrigger"
# uncomment the following line when using the schema extension from versions 1.x
#HBATTR_LDAPNAME="nagiosLastHeartBeat"
SERVER=127.0.0.1
EDIR_PORT=524
LDAP_MODE=TLS
LDAP_PORT=
LDAP_ONLY=false
LOGFILE="/var/log/$PROGNAME.log"
OVERWRITE=false
TRACE_LEVEL=0Thanks
Höegh
Höegh
Re: LDAP Monitoring in Nagios
check_dxml_drvstate is meant to be run from a server that has the dxcmd command installed on it, you'll likely need to run from the LDAP server through NRPE or another agent OR install the package that installs dxcmd on the XI server (I would personally do it through NRPE so you don't need to maintain the packages you install).
The optional server argument still uses the dxcmd to connect so those are really the only options.
The optional server argument still uses the dxcmd to connect so those are really the only options.
Re: LDAP Monitoring in Nagios
Hi Team,
As we're using Windows server, so we wrote powershell script on Server & used NRPE to get Driver state.
So everything is done now,
So please close this thread.
Thanks
Hoegh
As we're using Windows server, so we wrote powershell script on Server & used NRPE to get Driver state.
So everything is done now,
So please close this thread.
Thanks
Hoegh
Thanks
Höegh
Höegh
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: LDAP Monitoring in Nagios
great!hoegh wrote:Hi Team,
As we're using Windows server, so we wrote powershell script on Server & used NRPE to get Driver state.
So everything is done now,
So please close this thread.
Thanks
Hoegh
Locking thread