ARS 8.x - Escalations running on multiple servers and Logging specified on one Server populates to other servers in server group

Version 2
    Share:|

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


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System Server


    APPLIES TO:

    All versions



    PROBLEM:

    Symptoms

    1)    Escalations running on all servers
    2)    Logging specified on one server is reflecting same logging on all other servers including same log file name causing logging not to enable properly.  Attempts to enable server group logging will not enable on any server.  You can manually enable other logging (ie escalation, api) by modifying the ar.cfg/ar.conf then running the 'arsignal -c servername:Port#' command.

     


    CAUSE:

    These symptoms are due to incorrect configuration with Server-Connect-Name parameter. The Server-Connect-Name parameter in the ar.cfg file set to primary server name on all servers in server group.


    SOLUTION:

    Modify the Server-Connect-Name to the local remedy server name on all servers. 

    Shutdown all servers and restart them.   Test/Modify an escalation to fire.  Confirm escalation fires on primary escalation server.  Escalation logging should reflect escalation activity. 

    Check server group logging and operations were all owned by correct server as ranked in the AR System Server Group Operation Ranking form.

    Enable Remedy logging and it should now work properly where as before it was not enabling or same logging and log file name was reflected on other servers in server group.


    Article Number:

    000120562


    Article Type:

    Solutions to a Product Problem



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