"Monitor the service with this command" Field gets truncated

[morser]

Hello,
I have a Windows server configured in Nagios XI and on the configure service screen the command to monitor services is as follows:

check_xi_service_nsclient!ExcP3rn0d!SERVICESTATE!-l MSExchangeADTopology,MSExchangeIS,MSExchangeMailboxAssistants,MSExchangeMonitoring,MSExchangeMailSubmission,MSExchangeRepl,MSExchangeSA,MSExchangeSearch,MSExchangeServiceHost,MSExchangeTransport,MSExchangeTransportLogSearch,msftesql-Exchange -d SHOWALL

Nagios XI reporting a critical alert, stating:

MSExchangeADTopology: Started - MSExchangeIS: Started - MSExchangeMailboxAssistants: Started - MSExchangeMonitoring: Started - MSExchangeMailSubmission: Started - MSExchangeRepl: Started - MSExchangeSA: Started - MSExchangeSearch: Started - MSExchangeServ

Is there a limit to the field? How can I monitor all the services on the server that I need to?

Thanks in advance.

[morser]

I added this Host using the canned Exchange Server Monitoring Wizard. Is this a limitation of that template?

[abrist]

I added this Host using the canned Exchange Server Monitoring Wizard. Is this a limitation of that template?

I do not believe so. Is there any long plugin output? Go to the details page for the service check. Does the output span multiple lines? If it does, could you post it here?

[morser]

I'm new to Nagios XI. We are trialing it.
There is a limit to the alert comment, NOT the actual field. the field in services is configured properly.
This seems to be an NSclient issue.

I have one host with services reporting properly as up. Looking at the NSclient.log on that one it is active with new entries etc.

On the host I am having trouble with, the log has only one entry. I tried a reinstall and a repair of the NSclient.
2013-11-07 15:15:47: e:D:\source\nscp\trunk\include\socket/server.hpp:165: Failed to bind: An attempt was made to access a socket in a way forbidden by its access permissions

Status of server:
Host
Service
Status
Duration
Attempt
Last Check
Status Information
caprgwlkwecas1Notifications are disabled for this host Exchange Core Services Critical 4h 45m 38s 5/5 2013-11-07 15:27:17 Connection refused
Exchange Web Services Critical 4h 45m 32s 5/5 2013-11-07 15:27:23 Connection refused
Messages Pending Routing Critical 4h 45m 21s 5/5 2013-11-07 15:27:15 Connection refused
Remote Queue Length Critical 4h 44m 57s 5/5 2013-11-07 15:27:00 Connection refused

[lmiltchev]

...Failed to bind:...

This is usually due to running two instances of NSClient++ (or another program using the same ports). Are you running NSClient++ in a test mode with having the NSClient++ service also running?