Sometimes monitors bound to a service or service group fail and the error is not descriptive enough of why the monitor check failed. In such times if the monitor is a user customized monitor or any of the built-in monitors that use a Pearl script to run (such as LDAP, STOREFRONT,...etc.), then the nsumond.log can be checked for further details of the failure.

Instructions

1. Open an SSH session to the ADC where the issue is present.
2. At the SSH console type the below command to go to the shell prompt.

   shell

3. From the shell prompt type 

   more /var/nslog/nsumond/nsumond.log

4. You should see an output similar to the below with log entries for any monitor that is having failures:

   root@ns# more /var/nslog/nsumond/nsumond.log
   
   ./ntlm_mon.pl Script failed. Exit code : 1
   ./ntlm_mon.pl Exit Reason : Invalid ScriptArg format
   ./ntlm_mon.pl Script failed. Exit code : 1
   ./ntlm_mon.pl Script failed. Exit code : 1
   ./ntlm_mon.pl Exit Reason : Failed request - 401
   ./ntlm_mon.pl Script failed. Exit code : 1
   ./ntlm_mon.pl Exit Reason : Failed request - 401
   ./ntlm_mon.pl Script failed. Exit code : 1
    /netscaler/monitors/nsldap.pl Script failed. Exit code : 1
    /netscaler/monitors/nsldap.pl Exit Reason : (Failed to bind to server - Connection reset by peer