Facebook
Twitter- Server operating system version
- Ubuntu 26.04.1
- Plesk version and microupdate number
- 18.0.81 #2
Hello,
I'm seeing the following fatal error repeatedly (many times per day) in journalctl / mail log:
postfix/postalias[...]: fatal: open database /var/spool/postfix/plesk/virtual.lmdb: No such file or directory
Checked main.cf: default_database_type = hash, and all Plesk-managed map references (virtual_alias_maps, alias_maps, transport_maps, tls_server_sni_maps, etc.) explicitly use hash:/var/spool/postfix/plesk/... pointing to existing, working .db files. postconf -m confirms lmdb is supported by this Postfix build.
It looks like one of the Plesk mail management tools (mailmng-core and related binaries under /opt/psa/admin/sbin/) is invoking postalias with a hardcoded lmdb: prefix regardless of the actually configured default_database_type/map type, so it fails trying to open a .lmdb file that was never created (since the real maps are in hash format).
Practical impact so far: existing mailboxes/aliases work fine (the live hash: database is untouched), but this would presumably break adding/editing mailboxes or aliases via the Plesk panel, since the database rebuild step fails every time.
plesk repair mail -n -v reports 0 errors/warnings, so the repair tool doesn't seem to catch this.
This looks related to the known bug PPPM-15128 ("Postfix LMDB database file becomes corrupted"), but in my case the file is missing entirely rather than corrupted, and I'm already on a newer version (18.0.81.2) than the one where PPPM-15128 was supposedly fixed (18.0.75). Could this be a new variant of the same underlying issue, specific to fresh Ubuntu 26.04 installs?
Happy to provide more logs/details if useful.
I'm seeing the following fatal error repeatedly (many times per day) in journalctl / mail log:
postfix/postalias[...]: fatal: open database /var/spool/postfix/plesk/virtual.lmdb: No such file or directory
Checked main.cf: default_database_type = hash, and all Plesk-managed map references (virtual_alias_maps, alias_maps, transport_maps, tls_server_sni_maps, etc.) explicitly use hash:/var/spool/postfix/plesk/... pointing to existing, working .db files. postconf -m confirms lmdb is supported by this Postfix build.
It looks like one of the Plesk mail management tools (mailmng-core and related binaries under /opt/psa/admin/sbin/) is invoking postalias with a hardcoded lmdb: prefix regardless of the actually configured default_database_type/map type, so it fails trying to open a .lmdb file that was never created (since the real maps are in hash format).
Practical impact so far: existing mailboxes/aliases work fine (the live hash: database is untouched), but this would presumably break adding/editing mailboxes or aliases via the Plesk panel, since the database rebuild step fails every time.
plesk repair mail -n -v reports 0 errors/warnings, so the repair tool doesn't seem to catch this.
This looks related to the known bug PPPM-15128 ("Postfix LMDB database file becomes corrupted"), but in my case the file is missing entirely rather than corrupted, and I'm already on a newer version (18.0.81.2) than the one where PPPM-15128 was supposedly fixed (18.0.75). Could this be a new variant of the same underlying issue, specific to fresh Ubuntu 26.04 installs?
Happy to provide more logs/details if useful.