ADDM: Reasoning service will not start: Failed to bind to address

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Discovery


    BMC Atrium Discovery and Dependency Mapping



    Symptoms: Reasoning service will not start. The following messages are observed:

    Starting Reasoning service: [FAILED]
    Thu Apr 21 12:31:30 2011 : tw_svc_reasoning started.
    omniORB: (0) 2011-04-21 12:31:30.469780: Failed to bind to address :: port 25035. Address in use?
    omniORB: (0) 2011-04-21 12:31:30.469850: Error: Unable to create an endpoint of this description: giop:tcp::25035

    Problem persists after a reboot.

    Applies To: BMC Atrium Discovery and Dependency Mapping 9.x, 10.x




    Legacy ID:KA347867




    Please do the following:

    1) Run /sbin/ifconfig -a. Verify that ethernet (eth0) is at the top of the ifconfig results, and note the ip address.

    2) Run cat /etc/hosts. Verify that there is a correct entry associated with the ip address. The ip address for the name of the appliance in /etc/hosts and the ip address reported by "/sbin/ifconfig -a" must match. Also confirm that there is no other entry with a different ip address for the same host name. If there is another entry before the correct one, the error will be produced because /etc/hosts is an "ordered file" (the first line that matches the hostname "wins"). In this case, edit /etc/hosts file as root and comment out any ip entries that do not match the correct address. Then reboot to clear up any leftover python processes.

    Related Products:  
    1. BMC Atrium Discovery and Dependency Mapping


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles