Re: How monitor MSMQ
Posted: Fri May 13, 2016 4:23 pm
See attached log file and config file
Nagios Support Forum
Support for Nagios products and services
https://support.nagios.com/forum/
How monitor MSMQ
Page 2 of 4
Re: How monitor MSMQ
Posted: Mon May 16, 2016 2:42 am
What is the value in the $ARG1$ field?
Re: How monitor MSMQ
Posted: Mon May 16, 2016 4:21 am
Below is the value
MessageCount DIRECT=OS:jus2k8app02\private$\CRMHistory_2 100 200
MessageCount DIRECT=OS:jus2k8app02\private$\CRMHistory_2 100 200
Re: How monitor MSMQ
Posted: Mon May 16, 2016 9:00 am
What happens if you escape the \'s with another \, or put it in quotes ""?
Re: How monitor MSMQ
Posted: Mon May 16, 2016 10:53 am
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
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
Re: How monitor MSMQ
Posted: Mon May 16, 2016 11:52 am
I'm looking at your NSC.ini, and you have:
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.
Code: Select all
;NRPEListener.dllTry to uncomment that, and restart the NSClient service.
Re: How monitor MSMQ
Posted: Mon May 16, 2016 3:06 pm
Thank you the port is now open, but now getting a different error
see attached log file
see attached log file
Re: How monitor MSMQ
Posted: Mon May 16, 2016 3:22 pm
Try changing your current configuration from this:
To this:
... and restart the NSClient service one more.
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=0Code: 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=1Re: How monitor MSMQ
Posted: Tue May 17, 2016 3:20 am
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
No handler for command
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
No handler for commandRe: How monitor MSMQ
Posted: Tue May 17, 2016 10:01 am
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