starting the SCM broker results in ERROR: Could not resolve node name _node
search cancel

starting the SCM broker results in ERROR: Could not resolve node name _node

book

Article ID: 18223

calendar_today

Updated On:

Products

CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

 rs43:/home/ha0m02m/opt/ca/harvest/log> more 20130402HBroker1196110.log
 HBroker | 20130402 10:46:23 | ERROR: Could not resolve node name _node
 HBroker | 20130402 10:46:23 | ERROR: Initialization fails
 HBroker | 20130402 10:46:23 | ---- stopped ----

 

 

 

Environment

Release: Harvest-Software Change Manager 12.x and newer
Component:

Resolution

The first thing to check in this situation is if the RTServer is already running.

Check Task Manager if on Windows or "ps -ef | grep rtserver" on Linux/Unix.

If a rtserver process is found, kill it and try again

The problem is most like related to the fact that the TCP port number is already open and SCM broker is unable to start on this port.

The solution is to release that port so it would be available for use by the broker.

One possible cause of this problem might be the agent running on the same machine that has been started on the same TCP port as the broker. In this case shutdown the agent process and start it on different port.