Article ID: 6172, created on Mar 20, 2009, last review on Nov 13, 2014

  • Applies to:
  • Plesk 9.0 for Linux/Unix


The following errors exists in maillog:

Mar 12 11:27:14 plesk relaylock: /var/qmail/bin/relaylock: Unable to query ip addresses from smtp_poplocks, smtp-poplock will not work: not
an error
Mar 12 11:27:20 plesk relaylock: /var/qmail/bin/relaylock: Unable to delete expired smtp_poplocks: database is locked

What does it mean and how to fix it?


In Parallels Plesk Panel 9 several mail modules (authpsa, relaylock) work with sqlite database /var/lib/plesk/mail/poplock/poplock.db at the same time. Currently they work simultaneously: while one module is working with the database another one tries to update it and fails. And the errors below are shown in maillog.

In case relaylock (SMTP authorization) was unable to delete expired smtp-poplocks from the database:

Unable to delete expired smtp_poplocks: database is locked

In case authpsa (POP3/IMAP authorization) was unable to update the database with new IP addresses and user:

Unable to update smtp-lock database, smtp-lock will not work: database is locked

The problem affects SMTP after POP3-Lock Authorization that may fail for several sections. It does not work if authpsa was unable to update the database.

You may disable the POP3-Lock Authentication method and leave SMTP Authentication checked to make the error does not appear in maillog.

The problem will be fixed in future update of Parallels Plesk Panel that is going to be released after version 9.2. Workability of mail modules will be synchronized to avoid simultaneous connection to the database.
There is no workaround for Parallels Plesk Panel version 9.0.

4f57df935e9acf8d18830757d2346419 a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 6ef0db7f1685482449634a455d77d3f4 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF