Remedy - Flashboards - FB Server is not collecting any data into the FB:History form

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


    APPLIES TO:

    Remedy AR System Flashboards v.9.1.x, v.9.1.03



    PROBLEM:

    Old records are deleted from the FB:History form prior an upgrade of the ARSystem to v9.1.03
    After a successful upgrade there is no new data being set into the FB:History form related to KPI's.

     


    CAUSE:

    Incorrect Flashboards Server ranked and not having the FB service running for the correct ranked server.


    SOLUTION:

    1- Go to Applications > AR System Administration > AR System Administration Console

              User-added image

    2- Select System > General > Flashboard Server Configuration

              User-added image

    3- Make sure of the following:
         - The correct server is selected. If there is a server group environment, make sure the selected server is the one which is ranked as 1 for Flashboards.
         - Set the Log To: FILE
         - Set the Debug Level: DEBUG
         - Press Apply and then Close.

              User-added image


    4- Restart the Flashboard service and then open the arfbserver.log to find more information of the activities being performed by the Flashboards server.

    Example of the log file as per the behavior explained on this article:
    .....................................
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-13 12:06:40,741> <
    The server is already suspended. Suspend operation is ignored.>
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-13 12:11:40,763> <
    The server is already suspended. Suspend operation is ignored.>
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-13 12:16:40,781> <
    The server is already suspended. Suspend operation is ignored.>
    .....................................

    The above message indicates that the server selected in the Flashboard Configuration form is not actually the one ranked as 1 therefore the Flashboards activity is not being carried out.

    5- To actually be sure go to the AR System Server Group Operation Ranking form and perform a search for the Flashboards operation for example ranked as 1

              User-added image

    6- The actual result which explains the message observed in the arfbserver.log file and which is the reason for the original behavior observed is in the fact as mentioned earlier, the server ranked as 1 for Flashboards is a different server and not the one which was selected to check if data was being collected.

              User-added image

    7- Make sure the correct server is selected on step-3 and the Flashboards Server service is running on that server.
    After having done so the log file shows now the expected data and the FB:History form should be filled as expected.
    .....................................
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:30:03,823> <Reference time is:   Tue Sep 19 18:30:03 IST 2017
    Collect time after adjustment is: Tue Sep 19 18:31:03 IST 2017>
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:30:03,823>
    <FlashScheduler Adding job HistoryCollectorJob for flash>
    <FlashScheduler> <FlashServer> <2017-09-19 18:30:03,823> <FlashScheduler11821 millisecs to execute job "Checking config file server.conf for changes">
    <FlashScheduler> <FlashServer> <2017-09-19 18:30:15,644> <FlashScheduler Adding job "Checking config file server.conf for changes" to the worker's execute queue.>
    <FlashScheduler> <FlashServer> <2017-09-19 18:30:15,644>
    <FlashScheduler47356 millisecs to execute job HistoryCollectorJob for flash>
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:30:15,644> <FlashScheduler-Worker-0 Executing job "Checking config file server.conf for changes">
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:30:15,648> <FlashScheduler Adding job "Checking config file server.conf for changes">
    <FlashScheduler> <FlashServer> <2017-09-19 18:30:15,648> <FlashScheduler47352 millisecs to execute job HistoryCollectorJob for flash>
    <FlashScheduler> <FlashServer> <2017-09-19 18:31:03,002>
    <FlashScheduler Adding job HistoryCollectorJob for flash to the worker's execute queue.>
    <FlashScheduler> <FlashServer> <2017-09-19 18:31:03,002> <FlashScheduler12642 millisecs to execute job "Checking config file server.conf for changes">
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:31:03,002>
    <FlashScheduler-Worker-0 Executing job HistoryCollectorJob for flash>
    <FlashScheduler-Worker-0> <FlashServer> <2017-09-19 18:31:03,050> <AddHourOfDayOffset -- Hour found: 18>
    .....................................





     


    Article Number:

    000142330


    Article Type:

    Solutions to a Product Problem



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