How monitor MSMQ

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
azam101
Posts: 50
Joined: Fri Mar 18, 2016 6:01 am

Re: How monitor MSMQ

Post by azam101 »

See attached log file and config file
You do not have the required permissions to view the files attached to this post.
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: How monitor MSMQ

Post by Box293 »

What is the value in the $ARG1$ field?

Image
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
azam101
Posts: 50
Joined: Fri Mar 18, 2016 6:01 am

Re: How monitor MSMQ

Post by azam101 »

Below is the value

MessageCount DIRECT=OS:jus2k8app02\private$\CRMHistory_2 100 200
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: How monitor MSMQ

Post by rkennedy »

What happens if you escape the \'s with another \, or put it in quotes ""?
Former Nagios Employee
azam101
Posts: 50
Joined: Fri Mar 18, 2016 6:01 am

Re: How monitor MSMQ

Post by azam101 »

it makes no difference

When I do a nmap xxxxx -p 5666 , I get 5666/tcp closed nrpe

but this is in test environment which does not have any firewalls and I can telnet from server that I am trying to monitor to port 5666.


Should I log this with nagios support? we have bought support
You do not have the required permissions to view the files attached to this post.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: How monitor MSMQ

Post by hsmith »

I'm looking at your NSC.ini, and you have:

Code: Select all

;NRPEListener.dll
Notice the semicolon in front of it. It is commented out. Nothing is currently listening on port 5666.

Try to uncomment that, and restart the NSClient service.
Former Nagios Employee.
me.
azam101
Posts: 50
Joined: Fri Mar 18, 2016 6:01 am

Re: How monitor MSMQ

Post by azam101 »

Thank you the port is now open, but now getting a different error

see attached log file
You do not have the required permissions to view the files attached to this post.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: How monitor MSMQ

Post by hsmith »

Try changing your current configuration from this:

Code: Select all

[External Script]
;# COMMAND TIMEOUT
;  This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off.
;command_timeout=60
;
;# COMMAND ARGUMENT PROCESSING
;  This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
;allow_arguments=0
To this:

Code: Select all

[External Script]
;# COMMAND TIMEOUT
;  This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off.
;command_timeout=60
;
;# COMMAND ARGUMENT PROCESSING
;  This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
allow_arguments=1
... and restart the NSClient service one more.
Former Nagios Employee.
me.
azam101
Posts: 50
Joined: Fri Mar 18, 2016 6:01 am

Re: How monitor MSMQ

Post by azam101 »

I have made the changes but still same issue

see attached logs file and config

Also im trying now with the powershell script as well check_psmsmq,

And I also tried the changing to the below :

[NRPE]
;# NRPE PORT NUMBER
; This is the port the NRPEListener.dll will listen to.
;port=5666
;
;# COMMAND TIMEOUT
; This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off.
;command_timeout=60
;
;# COMMAND ARGUMENT PROCESSING
; This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
allow_arguments=1
;
;# COMMAND ALLOW NASTY META CHARS
; This option determines whether or not the NRPE daemon will allow clients to specify nasty (as in |`&><'"\[]{}) characters in arguments.
allow_nasty_meta_chars=1

Then go the error NSClient++.cpp:1195: No handler for command
You do not have the required permissions to view the files attached to this post.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: How monitor MSMQ

Post by rkennedy »

Under the NRPE section, please uncomment this part -

Code: Select all

;# COMMAND ARGUMENT PROCESSING
;  This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed.
;allow_arguments=0
Former Nagios Employee
Locked