After Plesk upgrade: logrotate error shows duplicate log entry for /var/log/plesk/panel.log

Written by Claudio Kuenzler - 0 comments

Published on July 22nd 2022 - Listed in Linux

After having updated Plesk from Onyx to Obsidian, the daily log rotation (launched by cron) started to throw errors.

Subject: Cron <root@a1> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/logrotate:
error: sw-engine:1 duplicate log entry for /var/log/plesk/panel.log

After taking a closer look inside /etc/logrotate.d, the log files in /var/log/plesk are indeed configured twice:

root@plesk ~ # grep "/var/log/plesk" /etc/logrotate.d/*
/etc/logrotate.d/plesk:/var/log/plesk/*.log /var/log/plesk/httpsd_access_log {
/etc/logrotate.d/plesk:/var/log/plesk/install/*.log {
/etc/logrotate.d/plesk-php56:/var/log/plesk-php56-fpm/*log {
/etc/logrotate.d/plesk-php70:/var/log/plesk-php70-fpm/*log {
/etc/logrotate.d/plesk-php72:/var/log/plesk-php72-fpm/*log {
/etc/logrotate.d/plesk-php73:/var/log/plesk-php73-fpm/*log {
/etc/logrotate.d/plesk-php74:/var/log/plesk-php74-fpm/*log {
/etc/logrotate.d/plesk-php80:/var/log/plesk-php80-fpm/*log {
/etc/logrotate.d/sw-engine:/var/log/plesk/panel.log

The sw-engine config file hasn't been modified for a couple of years and most likely is a relict from an older Plesk 12.5 setup and can be removed. With this change, the "duplicate loge entry" error should not happen anymore.

Add a comment

Comments (newest first)

No comments yet.