• 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.

Resolved No Transaction (Log) Written In Maillog

armanmisdar

New Pleskian
Server operating system version
CentOS Linux 7
Plesk version and microupdate number
Plesk Obsidian Version 18.0.42
I used to monitor the content of my maillog via tail -f /var/log/maillog

However, today there's no transaction or any log written into that file anymore. It just stopped. What I can read is only the following:

[root@plesk ~]# tail -f /var/log/maillog
Oct 19 14:42:52 plesk spamd[19566]: spamd: server killed by SIGTERM, shutting down
Oct 19 14:42:52 plesk courier-authdaemon: stopping authdaemond children
Oct 19 14:42:52 plesk postfix/postfix-script[26976]: stopping the Postfix mail system
Oct 19 14:42:52 plesk postfix/master[19934]: terminating on signal 15
Oct 19 14:42:52 plesk plesk_saslauthd[26922]: master status fd activity, exiting
Oct 19 14:42:52 plesk psa-pc-remote[559]: PleskFilter: private data not NULL
Oct 19 14:42:52 plesk psa-pc-remote[559]: PleskFilter: private data not NULL
Oct 19 14:42:52 plesk psa-pc-remote[559]: PleskFilter: private data not NULL
Oct 19 14:42:53 plesk psa-pc-remote[559]: PleskFilter: mi_stop=1

I've restarted the server but the same problem still happening. Email is working fine, I can receive and send without any issue.

Please advise. Thanks!
 
Back
Top