Remedy - Server - Error:"Error in failover monitor null" in the arerror.log in a Server Group environment

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


    APPLIES TO:

    Remedy AR System Server v9.x



    PROBLEM:

    The arerror.log shows a lot of errors like the one below in a Server Group:
    ..........
    Fri May 27 13:51:45.920 2016 Error in failover monitor null
    Fri May 27 13:52:45.926 2016 Error in failover monitor null
    Fri May 27 13:53:45.932 2016 Error in failover monitor null
    Fri May 27 13:54:45.939 2016 Error in failover monitor null
    Fri May 27 13:55:45.947 2016 Error in failover monitor null
    Fri May 27 13:56:45.953 2016 Error in failover monitor null
    Fri May 27 13:57:45.959 2016 Error in failover monitor null
    Fri May 27 13:58:45.964 2016 Error in failover monitor null
    ..etc...
    ..........


    CAUSE:

    Entries were added manually in the Fail-Over Whiteboard form.


    SOLUTION:

    Perform the below steps:

    1- (Note: This step needs to be done by accessing to each individual AR Server) Remove the servers from the server group.
         a) Go to Applications > AR System Administration > AR System Administration Console

              User-added image

         b) Select System > General > Server Information

              User-added image 

         c) In the Server Information form select the Configuration tab and make sure to uncheck the Server Group Member setting and press Apply and Ok.

              User-added image


    2- ( This step can be done accessing to any AR Server since the changes are done to the database).Remove the "Service Failover" operation from the AR System Server Group Operation Ranking form.
         a) Open the AR System Server Group Operation Ranking form and search for the "Service Failover" operation.

              User-added image

         b) The results will be displayed for the relevant servers of the group the ranking is defined to:
     
              User-added image

         c) Select each individual server entry and remove the "Service Failover" ranking for each server record by removing the current assigned ranking value:

              User-added image

           Result:

              User-added image 

    3- Backup and delete the records from AR System Service Failover Ranking form.

              User-added image


    4- Restart the AR System application on all servers to check if the error stills appearing (it should not).

    5- (This step needs to be done by accessing to each individual AR Server) Add the AR Servers in  the server group again and restart them again.
         Go to Applications > AR System Administration > AR System Administration Console > System > General > Server Information > Configuration tab and make sure to check the Sever Group Member setting and press Apply and OK.

    6- Add the rank to again for the "Service Failover" operation in the AR System Server Group Operation Ranking, restart the AR Servers and check again.

    Note: Errors like the following can still appear every minute in the arerror.log and armonitor.log if the entries in the AR System Service Failover Whiteboard form does not contain a LAST HEARTBEAT value:

    Example

      arerror.log:
      
      .....................
    Tue Sep 05 10:14:23.228 2017 Failover monitor checking service providers
    Tue Sep 05 10:14:23.231 2017 Error in failover monitor
    .....................
      
        
      
      armonitor.log:
      
      .....................
    Tue Sep 05 10:14:23.231 2017  Error in failover monitor null
    .....................
      
    Screenshot:

              User-added image

    Ensure that a valid value appears for a Last Heartbeat for each entry.


    Additional information:
    Remedy - Server/ITSM - How to Rank Operations in a Server Group

      

     


    Article Number:

    000115665


    Article Type:

    Solutions to a Product Problem



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