-
제목
"Error. Check logs." message in red is displayed for each agent in Agent Status dashboard -
설명
"Error. Check logs." in red text in the Agent Status dashboard, for every agent in the "Collecting Data" column.
Errors in the FMS logs (schedule id may vary):
WARN [http-exec-144] com.quest.wcf.portal.components.table.TableUtils - Error renderering cellcom.quest.wcf.core.module.runtimevalue.RuntimeValueException: com.quest.wcf.publicapi.code.FunctionInvocationException: Error executing script id=system:administration_agents_agent_status.getAgentDataCollectionStatus name="'Get Agent Data Collection Status' from the System module Administration/Agents/Agent Status"message: com.quest.nitro.service.sl.interfaces.scripting.ScriptingException: com.quest.nitro.service.sl.interfaces.scripting.ScriptAbortException: com.quest.nitro.service.sl.interfaces.schedule.ScheduleNotFoundException: com.quest.nitro.service.schedule.service.ScheduleNotFoundException: Schedule with id 98268e6a-b0ee-4e15-b064-d9470fa855e7 is not defined----script start------package system._administration_agents_agent_status.scripts;def agentBlackouts = server.AgentBlackoutService.findAllAgentBlackouts().findAll{ it.getAgent().getId() == agent.get("realId", null) && it.getAgent().getRemoteClientId() == agent.get("remoteClientId", null)};def inScheduleBlackouts = agentBlackouts.findAll{blackout ->return blackout.getSchedules().any{scheduleId->def schedule = server.ScheduleService.getSchedule(scheduleId);return schedule != null && schedule.isIncluded()}}if(inScheduleBlackouts.isEmpty()){return agent.get("isCollectingData", null)? "COLLECTING_DATA":"NOT_COLLECTING_DATA";}else{return "NOT_COLLECTING_DATA_BLACKOUT";}---- script end ------ -
원인
This issue is caused by having agent blackouts associated to non-existent schedules.
-
해결 방안
Find out which agents that are using this schedule from the command line by using this command (replace user and password with the appropriate values):
$FMSHOME/bin/fglcmd.sh -usr foglight -pwd foglight -cmd agent:showschedule
You should get an output similar to this:
ID: 164Host: FGLAM1Name: hostname-instanceType: DB_OracleStatus: Not activeBlackout Schedules:[invalid] (id: 98268e6a-b0ee-4e15-b064-d9470fa855e7)------------------------------------ID: 249Host: FGLAM1Name: other_name_of_agent-forms#1Type: OracleASStatus: Not activeBlackout Schedules:[none]------------------------------------ID: 31Host: FGLAM1Name: DEV_other_name_of_agentType: WebLogicStatus: Not activeBlackout Schedules:[invalid] (id: 98268e6a-b0ee-4e15-b064-d9470fa855e7)------------------------------------[...]In the example above, Agents 164 and 31 have a blackout with the invalid schedule. In order to remove these invalid schedules you can run this commands:
$FMSHOME/bin/fglcmd.sh -usr foglight -pwd foglight -cmd agent:setschedule -agentid 164 -scheduleid 98268e6a-b0ee-4e15-b064-d9470fa855e7 -remove;
$FMSHOME/bin/fglcmd.sh -usr foglight -pwd foglight -cmd agent:setschedule -agentid 31 -scheduleid 98268e6a-b0ee-4e15-b064-d9470fa855e7 -remove;
After clearing all agents from this blackout schedule, the error should be cleared from the UI.