Troubleshooting a problem where Reconciliation Engine logs not being created

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.


    PRODUCT:

    BMC Atrium CMDB Suite


    APPLIES TO:

    BMC Atrium CMDB Suite



    PROBLEM:

     

       

    Troubleshooting problems where Reconcilation Engine logs not being created

     


    SOLUTION:

     

    Legacy ID:KA337654

      
       

    If you have trouble enabling logs for the Reconcilation Engine 1.1, check the following steps:

     

    1. From the Reconcilation Configuration Console, click on the 'Server Settings' link and:

     

    a. Set 'Debug Mode' = True

     

    b. Specify 'Logging Level' = "Info" so it will capture normal operation too

     

    c. Specify a value of 'Maximum Log File Size (kilobytes)" = 300.

     

    d. Specify a value of 'Log File Path'. This value should be:

     

    - a directory on the server

     

    - a directory, NOT a file name

     

    - the arrecond process should have permissions to create files in that directory

     

    - on WIndows, it may be a good idea to put it in a short path, like C:\temp, rather than a long path with spaces in it.

     

    2. The configuration changes above are stored to the ar.cfg/ar.conf file on the server, so you can view the file directly to see if the changes took effect. You can also manually update the ar.cfg/ar.conf file and restart the Reconcilation Engine (by restarting the ARServer)

     

    3. Changes in the configuration above goes through the Application Pending form - so if the ar.cfg/ar.conf file is not updated, query on the Application Pending form where 'Category' = "Reconciliation" to see if there is an Update-Config record there.

     

     

     

    4. Verify the Reconciliation Engine is running on the server. The process name is arrecond.exe (Windows) or arrecond (UNIX). Verify that the process is running and that the process id (pid) is not changing.

     

    5. Reconcilation Engine creates a log file named arrecond.log (that tracks the scheduling aspect of RE) and a log file named for the reconciliation job. For example, there is a RE job named "Default Reconcilation Process", and with logging enabled, there is a file named "Default Reconciliation Process.log" created for it. Searching for these files on your server may reveal the logs are generated, just not in the expected location.

     

    6. The Reconciliation Engine finds the ar.cfg/ar.conf file in the conf directory under the directory specified in the -i parameter. Follow this process to verify it is set up correctly:

     

    - View the armonitor.cfg/armonitor.conf file on the server.

     

    - Find the line that runs arrecond. (On UNIX, the line will specify a script, arrecond.sh, so you should view that script).

     

    - Note the value for the -i parameter. This will be a directory, and it should be the ARServer install location.

     

    - Verify the directory exists, verify it has a conf subdirectory, and verify the ar.cfg (Windows) or ar.conf file (UNIX) exists in that directory.

     

    - Verify the owner of arrecond (UNIX) has read permission to the ar.conf file.

     


    Article Number:

    000090364


    Article Type:

    Solutions to a Product Problem



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