My Oracle Support Banner

[PCA/OVM] Oracle VM Server rsyslogd Incompatible with the 'kill -HUP' During Syslog Rotation (Doc ID 2444783.1)

Last updated on JULY 14, 2020

Applies to:

Private Cloud Appliance - Version 2.3.2 and later
Oracle VM - Version 3.4.1 and later
Linux x86-64

Symptoms

Compute nodes root filesystem gets full due to growing syslog file, syslog never gets rotated. 

Changes

The behavior of rsyslogd changes after version rsyslog-5.8.10-2.el6, kill -HUP {syslog.pid} is no longer a valid way to allow a new log file to be created.

Instead, the rsyslogd needs to be restarted, this also explains why (weekly) does not work, because the original logs file handle is now not released.

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.