SSH problem connecting to Linux server - v11

I upgraded one of my servers to v11. After I did so I have 6 Linux servers that fail SSH connection. The SiteScope is installed on a Windows 2008 server and it is trying to SSH connect to a remote Linux machine. This connection worked fine with v10 and only started failing with v11 (with no changes made to the remote server connection).

Has anyone seen issues begin with their v11 installation? Is there a configuration parameter or something? I have other SSH connections that are working fine - just these 6 specifically. I checked with the sysadmin and the logs are showing authentication accepted. But the result on SiteScope is that v1 and v2 SSH failed.

Re: SSH problem connecting to Linux server - v11

Hello, Edward. What kind of problem you can find in SiteScope logs? Timeouts or something else? Error reading, for example? Could you please provide some parts of logs? What about test of remotes - can it be executed succesfully? Do you have issues with all monitors or some specific monitors were affected? For example, CPU monitor or Log Monitor? Thanks,Sergey

Re: SSH problem connecting to Linux server - v11

I have looked in the logs and all I see if the failed monitors which is being caused by the inability to connect to the server. I am running on a Windows platform and have 34 Linux remote servers defined. Of those only 5 are failing to connect. These 5 connected fine with v10.12. When I say they fail to connect I mean if I go to the remote server entry and ask for a test the connection fails with the error "remote command error timed out reading (-996)" for 4 of the servers. The fifth is getting a different error - "remote command error unable to connect to server (-998)".

As I mentioned - these worked fine with v10.12. And the sys admin says his logs show a successful connection. I have tried changing the setting from Red Hat Linux to just Linux but get the same results.

Re: SSH problem connecting to Linux server - v11

1. For each Red Hat connection, enable the option SSH Only2. Go to master.config file and add the following parameter a the end of the file: _numberOfRepeatExecForSSHConnection=43. Restart SiteScope service4. Test your connections.

Re: SSH problem connecting to Linux server - v11

Enable the SSH debug in order to get more information about the error.

- Stop the SiteScope service.- Rename the error.log (Example: error.log.old)- Create another error.log file (empty)- Go to and open the /conf/core/Tools/log4j/PlainJava/log4.propierties file.- Check the parameters loglevel = ERROR and monitor.loglevel = ERROR.- Be sure the following lines have the DEBUG word:

Re: SSH problem connecting to Linux server - v11

I am using sis11.20. When I trying to connect ilo3. I get the "remote command error unable to connect to server (-998)".

after enalbe track I get log:

com.mercury.sitescope.util.ssh.exception.SSHV2ReadFailedException: Unknown error while reading from server, returned from reading without readComplete flag being true. Unknown error while reading from server, returned from reading without readComplete flag being true.

Re: SSH problem connecting to Linux server - v11

Issues in v.11 are commonly caused by Korn Shell (ksh), SiS gets along with Bash; remote command errors are related to this. Check if you can resolve this issue by putting this in "initialize shell environment" field /bin/bash or /bin/bash; sttyecho. An even better solution is to make sure SiS user is assigned to bash as default shell in target server user configs.

Kenneth GonzalezHP Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

Re: SSH problem connecting to Linux server - v11

Enable the SSH debug in order to get more information about the error.

- Stop the SiteScope service.- Rename the error.log (Example: error.log.old)- Create another error.log file (empty)- Go to and open the /conf/core/Tools/log4j/PlainJava/log4.propierties file.- Check the parameters loglevel = ERROR and monitor.loglevel = ERROR.- Be sure the following lines have the DEBUG word: