My Oracle Support Banner

EM 13c: Metric Evaluation Error start - Node manager Incidents in Enterprise Manager 13.1 Cloud Control (Doc ID 2226681.1)

Last updated on JANUARY 24, 2024

Applies to:

Enterprise Manager for Fusion Middleware - Version 13.1.1.0.0 and later
Information in this document applies to any platform.

Symptoms

The following error occurs through incident generation periodically in Enterprise Manager (EM) 13c Cloud Control:

ERROR
-----------------------
Host=<HOST_NAME>
Target type=Oracle WebLogic Node Manager
Target name=<NodeManager_NAME>
Categories=Availability
Message=Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Timeout during collection: oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for weblogic_nodemanager:<NodeManager_NAME>:Response
Severity=Critical
Event reported time=<Date> <Timestamp> <TimeZone>
Platform=x86_64
Operating System=Linux
Associated Incident Id=21469
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Target Availability
Event name=Status
Availability status=Availability Evaluation Error
Rule Name=<MYRuleSet>,Incident creation Rule for target error
Rule Owner=SYSMAN
Update Details:
Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Timeout during collection: oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for weblogic_nodemanager:<NodeManager_NAME>:Response

 Another incident may be created with a similar message line:

Message=Failed to connect to WebLogic Node Manager. wlst nmresponse.py command timed out for Node Manager at <host name>:<port>

 

From .../agent_inst/sysman/log/emagent_perl.trc:

nmresponse.pl: 2016-12-05 15:06:07,679: ERROR:  em_error= Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at <agent host>/<agent address>:<Port>.

 

Note that this timeout symptom may also apply to other target types, for instance:

2017-11-17 02:50:59,043 [3592958:2C79F777:GC.Executor.63 (oracle_vm_server_pool:<pool name>:Response) (oracle_vm_server_pool:<pool name>:Response:Response)] INFO - Cancelled task oracle_vm_server_pool:<pool name>:Response:Response due to [oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for oracle_vm_server_pool:<pool name>:Response]
2017-11-17 02:50:59,220 [3592958:4E343A23:GC.Executor.63 (oracle_vm_server_pool:<pool name>:Response)] INFO - Target [oracle_vm_server_pool.<pool name>] is marked as in DOWN state

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.