• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Log rotation question

TomBoB

Silver Pleskian
Now CentOS 6.5, Plesk 12.0.18#15; previously Plesk 11.5

have/had a few issues with log rotation which I'm now repairing thanks to jtroher suggestion at http://forum.parallels.com/showthread.php?288001-Log-rotation-not-work&highlight=log+rotation

While doing above repair I noticed a small missmatch.
All domains created on Plesk 11.5 have the following usr/local/psa/etc/logrotate.d config file (as long as it wasn't deleted for whatever reason):

#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
/var/www/vhosts/system/example.com/logs/*.processed {
size=5242880
rotate 4
compress
missingok
}
/var/www/vhosts/system/example.com/logs/error_log {
size=5242880
rotate 4
compress
missingok
copytruncate
}

whereas domains created new under Plesk12 (and also pre-12 domains that had the logrotate.d config file missing and are being repaired by off/on log files) have the following config file:

#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
/var/www/vhosts/system/example.com/logs/*.processed {
size=5242880
rotate 4
compress
missingok
}
/var/www/vhosts/system/example.com/logs/error_log {
size=5242880
rotate 4
compress
missingok
copytruncate
}
/var/www/vhosts/system/example.com/logs/proxy_error_log {
size=5242880
rotate 4
compress
missingok
copytruncate
}

Question is did Plesk during the upgrade from 11.5 to 12 kind of forget to adjust/add the proxy_error_log section to existing logrotate.d config files or may this have been created by changes to Plesk afterwards and is unrelated to the upgrade?

Excuse my lack of in-depth knowledge :)
 
Back
Top