• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk Log Performance

podman99

Basic Pleskian
Hi,

Looking at the usage stats on "pstorage top" I see a lot of writes constantly. Now this may just be our workload. However, I do notice that plesk logging is a little inefficient.

Is there a recommended way of modifying the mail logging to ensure that it logs once. Currently it appears to be logging to

/var/log/mail.* {log,err,info,warn}
/usr/local/psa/var/log/maillog
/var/log/syslog

I haven't looked into the Apache logging, however mail logging does indeed log more than it needs to.

the modifications will certainly be to the log daemon, however I wonder if there are implications to making the changes myself, or if there is a recommended modification I can make.
 
You should leave logging to maillog. Otherwise mail statistics collection (and some other features in more recent Plesk releases) will stop working.
 
Back
Top