Hi , I'm setting up check_by_ssh to invoke a script via forced command on a remote server to check a service status. The script returns the correct status on the server where it lives, and when I run check_by_ssh on the command-line, all is well. Nagios runs the remote command (and displays the contents of stdout on the status detail page), but the status always comes back 'Unknown'. Command-line: [nagios@nagios1]$ libexec/check_by_ssh -H 149.152.10.183 -l remoteuser -i /path/to/rsa/identity_key -C 'LDAP' LDAP daemon is running. When nagios runs the service check, the same 'LDAP daemon is running.' message appears in the status information, but the status is nevertheless marked as hard 'UNKNOWN'. Here's checkcommands.cfg: define command{ command_name check-cp-ldap command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -l remoteuser -i /path/to/rsa/identity_key -C 'LDAP' } This is the status log entry: [1104169159] SERVICE;soluminis1;LDAP;UNKNOWN;3/3;HARD;1104169025;1104169205;ACTIVE; 1;1;1;1104157840;0;UNKNOWN;3706;335959;419;530;1104165074;2;1;0;1;1;0;0.00;0;1;1;1;LDAP daemon is running. Nagios is running on RH Linux, and the target host is Solaris 9. Nagios' SSH is OpenSSH and the Solaris box is running Sun_SSH_1.0, protocol versions 1.5/2.0. The remote script worked correctly when monitoring services on a Solaris 8 box which was running SSH Secure Shell (non-commercial license). Check_by_ssh is from nagios-plugins 1.4.0alpha1, version 1.18. What am I not seeing? It's probably some bonehead maneuver on my part, but has anyone else run into (and found their way around) this? Scott Zak Connecticut State University System.