Question Plesk Email Security Pro - 421 4.3.2 Service shutting down, closing channel - Mails are stuck in the queue

[mcac]

Server operating system version

Almalinux 8.10

Plesk version and microupdate number

18.0.68 #1

Hi, 2 independent Plesk servers are with the same issues at the same time today. Many mails are stuck in the queue. I found the article https://support.plesk.com/hc/en-us/...*MTc0MTg1MDIyOC4yMS4xLjE3NDE4NTAzNTIuMjEuMC4w so I deinstall and reinstall Plesk Email Security Pro. The issues resolved this. But it is very strange that 2 servers have the same problem at the same time. Did others have the same problem today? Perhaps certain spam that is circulating today is causing the problem.

 

[ollosolucions]

Same problem here today

 

[Beulenfred]

Hi,

we observed filling mailqueues on Centos7 and Almalinux8 servers since the march 12th update of E-Mail Security.

Cause was a wrong path in the E-Mail Security Config, preventing Amavisd connecting to MariaDB:

connect_to_sql: unable to connect to DSN 'DBI:mysql:database=emailsecurity;mysql_socket=/var/run/mysqld/mysqld.sock': Can't connect to local MySQL server
TROUBLE in process_request: connect_to_sql: unable to connect to any dataset at (eval 146) line 253.


Setting the correct path to the .sock in /etc/amavisd/email-security.conf and restarting amavisd fixed it.

I also recommend to requeue the mails:
postsuper -r ALL
or
postqueue -f

edit: In one case the amavisd service was not even running and not enabled.

 

[ollosolucions]

After uninstall and reinstall, the problem returns:

Mar 13 10:22:32 xxxx amavis[248377]: (248377-01) (!)connect_to_sql: unable to connect to DSN 'DBI:mysql:database=emailsecurity;mysql_socket=/var/run/mysqld/mysqld.sock': Can't connect to local server through socket '/var/run/mysqld/mysqld.sock' (2)
Mar 13 10:22:32 xxxx amavis[248377]: (248377-01) (!!)TROUBLE in process_request: connect_to_sql: unable to connect to any dataset at /usr/share/perl5/vendor_perl/Amavis/Out/SQL/Connection.pm line 255.
Mar 13 10:22:32 xxxx amavis[248377]: (248377-01) (!)Requesting process rundown after fatal error

 

[Ohya]

The problem is that Amavis is searching for the wrong mysqls.sock.


Simply edit the socket in /etc/amavisd/email-security.conf and restart Amavisd.service.


Search for and replace /var/run/mysqld/mysqld.sock with your correct mysql.sock path (e.g., /var/lib/mysql/mysql.sock or any other path used on your system).

 

[Raul A.]

A KB article was published for this issue: https://support.plesk.com/hc/en-us/...urity-mysql-socket-var-run-mysqld-mysqld-sock

 

[mcac]

Thanks for this information. Right, in logs were many errors like "connect_to_sql: unable to connect to DSN 'DBI:mysql:database=emailsecurity;mysql_socket=/var/run/mysqld/mysqld.sock': Can't connect to local server through socket '/var/run/mysqld/mysqld.sock'".
After reinstall the Email Security Pro no logs like this happend.
After reinstall I also cannot find a row like "mysql_socket=/var/run/mysqld/mysqld.sock" in file /etc/amavisd/email-security.conf described in

https://support.plesk.com/hc/en-us/articles/30609832237591-Unable-to-receive-email-with-Plesk-Email-Security-extension-installed-connect-to-sql-unable-to-connect-to-DSN-DBI-mysql-database-emailsecurity-mysql-socket-var-run-mysqld-mysqld-sock?_gl=1*2eyt8s*_gcl_au*NDQ5MzcwMTg0LjE3Mzg2NzU0MjQ.*_ga*MTU0MDc0OTA5LjE3MzY5NDg2OTc.*_ga_5SX3L7KZCY*MTc0MTg2MjUwOC4yMy4xLjE3NDE4NjMwMzkuNjAuMC4w

So it seems reinstall is also a resolution for this issue.

 

[AmaZili Communication]

Thanks for your help.
Removing plesk email security add-on and re-enabling it did the trick for our servers too.

 

[ollosolucions]

Thanks for all! Now is activated and it's working.

 

[mcac]

Oh no, all blacklists and whitelists are deleted now. It is definitively not a good way to remove and reinstall the Plesk Security. We have Plesk backups of system but there is of course no function to restore this configurations. Have anybody an idea, how can I restore this? Thanks Plesk for the bug, thanks Plesk for the resolution.

 

[Sebahat.hadzhi]

Hello, everyone. The fix is released in Plesk Email Security version 1.5.12-5258:

Plesk Email Security - Plesk Extensions

ext.plesk.com