If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
I'm having trouble setting up a Linux monitor from Sitescope.
Connecting using Putty from the Sitescope server works fine.
From Sitescope web it does not.
Error message::
Attempting SSH V1 connect.
SSH V1 connect failed
Attempting SSH V2 connect
SSH V2 connect failed
remote command error (-1)
remote command error (-1)
Here's the sshd_config of the Debian Linux server I want to monitor:
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
Attached is a screenshot of the settings in Sitescope.
Any ideas how to get this working?
BernhardKappler over 8 years ago in reply to BernhardKappler +2 verified
Hi, In an online session with Soderborg, we were able to identify and resolve the ssh connection issue. Here’s a summary of our findings: Looking at /var/log/auth.log on the Linux system, we found: sshd…
Sandeeps procedure is referring to key based authentication (authorized_hosts). As of your previous post this does not seem to be your issue. The initial key exchange refers to the host keys, which allows…
Hi, Your sshd_config looks good to me. Please double check that the RSA hosts keys on your Linux system exist (/etc/ssh/ssh_host_rsa_key). If not you need to create RSA host keys (ssh-keygen). You could…
remote command error (-1) means we could connect but couldn't execute or read the command output. Make sure you;re using bash shell for the user and you can run echo commands.
Thanks for your reply Kenneth,
Default shell for the user is Bash. (chsh -s /bin/bash)
Connecting using Putty and the sitescope credentials to the target machine, I can run echo-commands.
The error in the SiS log says Key Exchange failed for SSH v2 (which is the only one configured on the Linux sshd).
2015-10-28 14:11:20,862 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging
2015-10-28 14:11:22,445 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging
2015-10-28 14:11:22,460 [http-8080-Processor9] (SSHV1Connector.java:126) ERROR - internalConnectV1: Connection error occurred(V1): com.mercury.sitescope.util.ssh.SSHConnectionException: Couldn't start terminal!, Couldn't start terminal! connecting to host 64.18.215.174
2015-10-28 14:11:22,460 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging
2015-10-28 14:11:22,569 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging -->close ssh connection
2015-10-28 14:11:22,569 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging
2015-10-28 14:11:22,819 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging dI.notify false wFKC.waited false true wFKC.done
2015-10-28 14:11:22,819 [http-8080-Processor9] (RemoteCommandLine.java:263) INFO - rem: t_Staging -->close ssh connection
2015-10-28 14:11:22,819 [http-8080-Processor9] (RemoteCommandLine.java:128) ERROR - list of SSH retries -->
2015-10-28 14:11:22,819 [http-8080-Processor9] (RemoteCommandLine.java:129) ERROR - Wed Oct 28 14:11:22 CET 2015 SSH internalConnectV2: A Connection error occurred: Key exchange failed: I/O error3: unknown error (uc) dI dI.notify false wFKC.waited false true wFKC.done connecting to host 64.18.215.174
2015-10-28 14:11:22,819 [http-8080-Processor9] (RemoteCommandLine.java:130) ERROR -
This key exchange failure might be related to a corrupted key assigned to SiteScope server IP in the target side. These SSH keys are stored normally in /etc/ssh/ssh_known_hosts or, more likely, /home/
Removing the whole file or just the line assigned to the SiteScope server IP or hostname will force a new key exchange as in the first time attempted.
But where does Sitescope store these ssh-keys on a WIndows host?
The Sitescope service on the Windows host is running as SYSTEM and no specific user.