EM 13c: Enterprise Manager Cloud Control Agent Install Fails at Initialization Step With Error: SSH daemon (sshd) is not running on port 22 (Doc ID 1488159.1)
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Enterprise Manager Base Platform - Version 13.1.0.0.0 and later
Information in this document applies to any platform.
SYMPTOMS
Enterprise Manager (EM) Cloud Control Agent install fails at initialization step with error message "SSH daemon (sshd) is not running on port 22".
+ oms/sysman/prov/agentpush/<TIMESTAMP>/applogs/<hostname>_deploy.log
2012-06-13_13-46-32:INFO: Jsch Valdation Failed Problem :SSH server check failed Recommendation: Verify the value of SSH_PORT in the /oms/oui/prov/resources/Paths.properties file. Ensure that it is the same as the port on which the sshd is running on the remote host.
2012-06-13_13-46-32:INFO:Updating Action SSHValidationswith Status FAILED and error Message :SSH daemon (sshd) is not running on port "22" and problem SSH server check failed and recommendation Verify the value of SSH_PORT in the /var/app/oracle/em/oms/oui/prov/resources/Paths.properties file. Ensure that it is the same as the port on which the sshd is running on the remote host.
CAUSE
This error can occur due to one of the following reasons:
SSH port 22 is blocked by proxy / firewall on the Target machine
SSH is not running on the Target machine
SSH daemon is running on non-default port (other than 22)
Note: This error is also commonly encountered on Windows target host when Cygwin is not installed.
SOLUTION
1. Verify that the SSH port 22 is not blocked from the OMS host using the following command (a blocked port will be indicated, a free port will result in no response):
telnet <target host> 22
2. Verify that SSH is running on the target host using
ps -ef | grep ssh
netstat -anp | grep 22
The Prerequisites for 12c Agent installation using Push Method clearly states that the SSH daemon should be running on the default port (that is, 22) on all the destination hosts.
Enterprise Manager Cloud Control Basic Installation Guide
Release 13.5
Chapter 6 Installing Oracle Management Agents 13c Release 5
6.2 Installing Management Agents Using Agent Gold Images
6.2.2 Installing a Standalone Oracle Management Agent 13c Release 1 Using Add Host Targets Wizard or EM CLI
6.2.2.3 Meeting the Generic Prerequisites for Installing Standalone Management Agents Using Add Host Targets Wizard or EM CLI
Table 6-1 General Prerequisites for Installing Standalone Oracle Management Agent
3. If SSH on the target host is running on a non-default port, then update the SSH_PORT property in $<OMS_HOME>/oui/prov/resources/Paths.properties as below:
SSH_PORT=<port number>
If you are installing on target A where SSH is running on port 99; then you would need to make the above change. If the next Agent Deployment is on target B where SSH is running on default port 22; then you will need to revert the changes to set SSH_PORT= or SSH_PORT=22 in $<OMS_HOME>/oui/prov/resources/Paths.properties file.
You cannot install Agents on target X and target Y at the same time, if they have SSH running on different ports.
|