On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Mail stuck in the queue in the server with Plesk: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)

Avatar
Benjamin Weßel
Updated
Follow
Plesk for Linux kb: technical ext: pes ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • E-Mails are stuck in the queue with below messages in /var/log/maillog:

    amavis[26892]: (26892-01) (!)connect_to_sql: unable to connect to DSN 'DBI:mysql:database=emailsecurity;host=localhost;port=3306': Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)
    amavis[26892]: (26892-01) (!!)TROUBLE in process_request: connect_to_sql: unable to connect to any dataset at (eval 132) line 253.
    amavis[26892]: (26892-01) (!)Requesting process rundown after fatal error

  • MariaDB upgrade has been performed recently on the server with SELinux enabled

Cause

MariaDB bug #MDEV-24941: SElinux incorrect label for server socket.

The SELinux context for the MariaDB socket file /var/lib/mysql/mysql.sock has been lost because of the above because of upgrade to MariaDB version affected by the bug.

Resolution

To workaround the problem until the bug is resolved, set up a scheduled task which frequently restores SELinux context on MariaDB mysql.sock file /var/lib/mysql/mysql.sock​:

  1. Log into Plesk

  2. Navigate to Tools & Settings > Scheduled Tasks (Cron jobs) and click Add Task

  3. Set up the new scheduled the task with the following values:

    • Run a command
    • Command: /usr/sbin/restorecon -v /var/lib/mysql/mysql.sock
    • Run: Cron-style: * * * * *​
    • System user: root
    • Description: Restore MariaDB socket SELinux MDEV-24941:
    • Notify: Do not notify

  4. Click OK

    The scheduled task will execute restorecon command to temporarily resolve the issue. It will run automatically once in a minute.

  5. Resend the stuck e-mails

The following alternative workarounds are also available:

Comments

2 comments

Sort by Date Votes
  • Avatar
    Jon Ireland

    I get the following error with this work around any ideas?

    Task "/usr/sbin/restorecon -v /var/lib/mysql/mysql.sock​" completed with error in 0 seconds, output:
    /usr/sbin/restorecon: lstat(/var/lib/mysql/mysql.sock​) failed: No such file or directory
    0
    Comment actions Permalink
  • Avatar
    Md Rasel Khan

    Number 5 step should I run one time right? No need to set cron job for this, right?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles