• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

After 11.0.9->11.5.30 Plesk stopped renaming maillog as maillog.processed

burnley

Regular Pleskian
This seems so far to be isolated to one particular server. The file /usr/local/psa/var/log/maillog hasn't been renamed as .processed since 22nd of August and now it's 516MB in size. Where can I look and how do I fix it?
 
Yes, this is most probably related, since both tasks are invoked from Daily Maintenance script. Check that relevant cron jobs are present, e.g. (location may differ depending on OS) via:

# grep -r Daily /etc/cron*
/etc/cron.daily/50plesk-daily:/opt/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
/etc/cron.monthly/50plesk-monthly:/opt/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php monthly >/dev/null 2>&1
/etc/cron.weekly/50plesk-weekly:/opt/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php weekly >/dev/null 2>&1
 
Nikolay, here's the output on the server:
grep -r Daily /etc/cron*
/etc/cron.daily/50plesk-daily:/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
/etc/cron.monthly/50plesk-monthly:/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php monthly >/dev/null 2>&1
/etc/cron.weekly/50plesk-weekly:/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php weekly >/dev/null 2>&1

At the moment I'm suspecting some sort of timeout that kicks in and prevents the job completion.
 
Try running the script manually. Check the output for errors.

# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
 
Nikolay, that's exactly what I've done yesterday morning and after more than 24 hours I had to gave it the CTRL+C salute cause it just wouldn't finish.

# time /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
2013-09-03T09:19:17+10:00 ERR (3) [panel]: Error during calculation disk usage for mailnames on service node local : Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory
Unable to calculate Maildir++ size: No such file or directory
System error 2: No such file or directory



real 1556m56.210s
user 0m2.100s
sys 0m1.085s
 
Judging by errors this looks like inconsistency between DB and file system. Don't know why it works so long, but the script may work pretty long if there are many entities in Plesk.

I suggest you contact support team so they can resolve the issue directly on your server.
 
That's what I've done and they helped me to get it fixed. For the archives, I had to run "/usr/local/psa/admin/sbin/mchk --with-spam", followed by re-running the daily maintenance script again manually.
 
Back
Top