• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

logrotate.conf not running

B

Bertan Linson

Guest
It appears as though my /usr/local/psa/etc/logrotate.conf is not running. My maillog is HUGE and I am getting errors because of it.

My logrotate.conf looks like this. Files are not rotating, they are just getting bigger!

include /usr/local/psa/etc/logrotate.d

/usr/local/psa/var/log/xferlog.processed {
missingok
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/var/log/maillog.processed {
missingok
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/var/log/psi.log {
missingok
daily
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/admin/logs/*_log {
weekly
rotate 12
missingok
notifempty
copytruncate
compress
}

/usr/local/psa/var/webalizer.cache {
missingok
rotate 0
size 512M
nocreate
}

Where can I look to insure this runs?
 
Last edited by a moderator:
Plesk Maillog Error - Logs Not Rotated As Expected

I have two CentOS 5.4 servers, both running Plesk 8.6 with identical conf scripts and completely up-to-date via YUM UPDATE. However, one has a huge mail log file that has never been rotated and the other behaves normally. Since both are exclusively managed by Plesk, there seems to be a bug in the server #2 Plesk load. How do I remedy the problem [i.e., get rid of the huge log file that appears to be bogging my system down]?

Details are as follows:

One has a maillog file as expected:
[root@server1 ~]# ls -l /usr/local/psa/var/log/maillog
-rw-r----- 1 root root 1403965 Dec 13 14:21 /usr/local/psa/var/log/maillog
[root@server1 ~]# ls -l /usr/local/psa/var/log/maillog.processed
-rw-r----- 1 root root 3616348 Dec 13 05:17 /usr/local/psa/var/log/maillog.processed

The second server has an enormous log file and no "maillog.processed":
[root@server2 ~]# ls -l /usr/local/psa/var/log/maillog
-rw-r----- 1 root root 612050521 Dec 13 14:07 /usr/local/psa/var/log/maillog
[root@server2 ~]# ls -l /usr/local/psa/var/log/maillog.processed
ls: /usr/local/psa/var/log/maillog.processed: No such file or directory

The config files "/usr/local/psa/etc/logrotate.conf" are identical:

include /usr/local/psa/etc/logrotate.d

/usr/local/psa/var/log/xferlog.processed {
missingok
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/var/log/maillog.processed {
missingok
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/var/log/psi.log {
missingok
daily
rotate 3
size 10M
compress
nocreate
}

/usr/local/psa/admin/logs/*_log {
weekly
rotate 12
missingok
notifempty
copytruncate
compress
}

/usr/local/psa/var/webalizer.cache {
missingok
rotate 0
size 512M
nocreate
}
 
Back
Top