Failed to Start the OceanStor ReplicationDirector Agent in Windows

Log in to the host where database applications reside and check the operation logs of the OceanStor ReplicationDirector Agent.
Click the log folder in the installation path of the OceanStor ReplicationDirector Agent. Open rdagent.log.
In the log file, search "Starting service failed, because the port is used by other" or "bind failed". If the words are found, the communication port for the OceanStor ReplicationDirector Agent is occupied.
Run netstat –ano | findstr "\<59526\>, check whether the communication port for the OceanStor ReplicationDirector Agent is occupied.



If the information shown in the above figure is returned, port 59526 is occupied by the process whose ID is 1536.


Run tasklist | findstr 1536 to view the process name. If the process is not required by the current services, stop the process. Run the command in 2 to check whether the communication port for the OceanStor ReplicationDirector Agent is released. If the port is released, start the OceanStor ReplicationDirector Agent again.
If the process occupying the communication port for the OceanStor ReplicationDirector Agent is required for the current services, open configuration file /conf/rdagent.ini in the installation path of the OceanStor ReplicationDirector Agent, change the value of the port configuration item to an unoccupied port number, save the file, and start the OceanStor ReplicationDirector Agent again.
On the OceanStor ReplicationDirector server end, use the new port number to discover the host.

Scroll to top