Custom Agent : Confusing behavior of Monitoring Core for automatic MO registration

Document ID : KB000086697
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Affects Release version(s): 5

Error Message :
On the open agent log, we find this kind of errors when performing the automatic declaration at startup:
############################
oamostatus - AutoDeclare - Monitored Object 'windows_small_group_sldmgtspm03' failed to be updated on Management Server 'vmstm2k881.domain.com:9901'.
oamostatus - AutoDeclare - Monitored Object 'all_os_demo01' failed to be updated on Management Server 'vmstm2k881.domain.com:9901'.
oamostatus - AutoDeclare - Monitored Object 'all_servers_qa_paris' failed to be updated on Management Server 'vmstm2k881.domain.com:9901'.
oamostatus - AutoDeclare - Monitored Object 'all_servers_sldmgtspm03' has been successfully updated on Management Server 'vmstm2k881.domain.com:9901'.
############################

Patch level detected:Sysload Agent Custom 5.80 (designed with Sysload Studio)
Product Version: Sysload 5.8.0

Description :Collector takes the Monitored Object's list in sections but not in the Monitored Objects list.
Commented sections in the configuration file are taken into account in the automatic declaration.
 
Environment:
OS: All
 
Cause:
Cause type:
Defect
Root Cause: N/A
 
Resolution:
In order to workaround the problem, simply remove from the Management Server the MOs that are no longer used by a multi-MO agent.

Fix Status: Released

Fix Version(s):
Component: Agents
Version: Sysload 5.8.0
 
Additional Information:
Workaround :
N/A