This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Reconciliation Engine logging issues

If the Reconciliation Engine contains incorrect log path settings or insufficient permissions to write to the log directory, or if the Reconciliation Engine stopped responding, logging might be abruptly stopped.

To troubleshoot Reconciliation Engine logging issues

  1. Log in to the BMC Atrium Core Console.
    For information about logging in to the console, see Navigating the interface.
  2. From the Application Launcher, click Reconciliation.
  3. Click Edit Server Configurationon the toolbar and configure the following settings on the Server Configuration Editor window.
    1. From the Logging Level list, select Info.
      Setting this option enables the log to capture information about warnings and error messages. This level also includes class level and dataset level information.
    2. In the Maximum Log File Size (kilobytes) list, type 1000.
      This sets the maximum size of the log file to 1000 KBs.
    3. In the Log File Path field, specify the correct log path.
      When you specify the log file path, make sure that:
      • The directory exists on the BMC Remedy AR System server.
      • It is a directory, not a file name.
      • The Reconciliation Engine has permissions to create files in that directory.
        For testing purposes, specify a short log file path with no spaces.
        On Microsoft Windows, for example, C:\RELog.
        On UNIX, for example, /tmp/RELog/.
        If you do not specify a log file path or if the log file path is empty, the Reconciliation Engine log is generated in the Db subdirectory of your AR System server installation directory by default. For more information about the log settings, see Reconciliation Engine logging.
  4. In the ar.cfg (ar.conf ) configuration file, verify that the settings you configured in step 3 are updated on the AR System server.
    The ar.cfg configuration file contains AR System server configuration changes. This file is located in the C:\Program Files\BMC Software\ARSystem\Conf subdirectory of your AR System server installation directory. For more information about the ar.cfg file, see ar.cfg or ar.conf in the BMC Remedy Action Request System online documentation.

    Tip

    You can also manually update the ar.cfg or ar.conf file to match the entries in the Modify Server Configuration window of the Reconciliation Manager and restart the Reconciliation Engine to configure the settings.

  5. If you configured the server configuration settings (see step 3) using the BMC Atrium Core Console and if these settings are not updated in the ar.cfg or ar.conf file, query the Application Pending form for records where 'Category' = "Reconciliation".
    This enables you to verify that the Application Pending form contains an Update-Config record for the Reconciliation Engine.
  6. On the AR System server, verify that:
    • The Reconciliation Engine is running.
      The process name for the Reconciliation Engine is arrecond.exe on Windows and arrecond on UNIX.
    • The value in the process ID field is not changing.

      Tip

      To verify that the process ID frequently changes, note its value every few minutes.

      When the Reconciliation Engine process stops abruptly, the armonitor configuration file restarts the process and a new process ID is assigned to it. Therefore, the changing process ID value indicates that the Reconciliation Engine is constantly restarted.

  7. Verify that the arrecond.log file exists on the AR System server.
    The Reconciliation Engine creates the arrecond.log and a log file named <reconciliationJobName_integer>.log, for example, BMCAsset - Identification_5.log. The arrecond.log tracks Reconciliation Engine scheduling. For more information about Reconciliation Engine logging, see Reconciliation Engine logging.
  8. Perform the following steps to verify that the ar.cfg (ar.conf) configuration file is set up correctly:
    1. Open the armonitor.cfg (armonitor.conf ) file on the AR System server.
      The armonitor.cfg file contains the commands that the armonitor binary executes. On Windows, this configuration file is located in the C:\Program Files\BMC Software\ARSystem\Conf subdirectory of your AR System server installation directory. On UNIX, it is located in the /etc/arsystem/<ARInstanceName>/ subdirectory. For more information about the armonitor.cfg file, see armonitor.cfg or armonitor.conf in the BMC Remedy Action Request System online documentation.
    2. In the configuration file, search for the line entry that runs the arrecond.exe executable (Windows) or arrecond.sh(UNIX).

      Tip

      To view the arrecond.sh script, open it in a UNIX editor.

    3. Note the value that is specified for the -i parameter.
      The value specified for this parameter is a directory name, which must be the same as the AR System server installation directory.
    4. If the directory name for the -i parameter is different than the AR System server installation directory, change it to match the AR System directory name.
Was this page helpful? Yes No Submitting... Thank you

Comments