Article ID: 130421, created on Mar 13, 2017, last review on Mar 16, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

OSA platform has been upgraded from 6.0 to 7.0.

After the upgrade, /var/log/poa.log is not rotated and grows larger day by day.

/var/log/pa/core.log, which is the default log location on 7.0, does not exist.

Both /etc/syslog.conf and /etc/rsyslog.conf files co-exist and contain definition for osscore log file:

# grep local0 /etc/syslog.conf
local0.*                -/var/log/pa/core.log

# grep local0 /etc/rsyslog.conf
local0.*                -/var/log/poa.log

The actual service responsible for logging is rsyslog:

# chkconfig --list | grep syslog
rsyslog         0:off   1:off   2:on    3:on    4:on    5:on    6:off

Log rotation settings are also configured for the new log file location:

# cat /etc/logrotate.d/poa

# Parallels Automation log rotation
/var/log/pa/core.log {
        rotate 28
        daily

Cause

syslog service was replaced with rsyslog in the past, which resulted in duplicate log location settigs. Handling of such cases will be improved in scope of POA-110498.

Resolution

  1. Correct /etc/rsyslog.conf file to point local0 to /var/log/pa/core.log.
  2. Restart the services:

    # service pa-agent stop
    # service pau stop
    # service rsyslog restart
    # service pau start
    # service pa-agent start
    

Search Words

upgrade

huge

log

rotated

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF