My Oracle Support Banner

EM13c: Log File Monitor Metric Does Not Work Correctly. (Doc ID 2592340.1)

Last updated on SEPTEMBER 06, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Log File Monitor Metric Does Not Work Correctly.

<agent_inst>/sysman/log/emagent_perl.trc confirm following output:

parse-log1.pl: <TIMESTAMP>: ERROR:  updateGC: /var/log/messages is not readable
parse-log1.pl: <TIMESTAMP>: ERROR:  updateGC: /var/log/messages is not readable
parse-log1.pl: <TIMESTAMP>: ERROR:  updateGC: /var/log/messages is not readable
parse-log1.pl: <TIMESTAMP>: ERROR:  updateGC: /var/log/messages is not readable
parse-log1.pl: <TIMESTAMP>: ERROR:  updateGC: /var/log/messages is not readable
parse-log1.pl: <TIMESTAMP>: WARN:  em_warning= Following files are not readable: /var/log/messages, /var/log/messages, /var/log/messages, /var/log/messages, /var/log/messages

/var/log/messages:

-rw-------. 1 root root XXX <TIMESTAMP> messages --- Has 640

Agent owner cannot read this,if customer can change the ownership granting
sudo to the logfile monitor  and can read /var/log/messages without changing
ownership of the log file at the OS level but there is no feasible in em to
make sudo to specific metric collection.

 

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
References


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