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

Document ID : KB000018223
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:


 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 ----

Solution:

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.