Recent content by nelteren

Alternate (slow) workaround: Do not migrate more than 10 subscriptions at once. After each 10, run `plesk repair mail -y` on the command line. Still goes wrong a bunch of the time, so delete and re-try failing subscriptions. It might take a few days instead of a few hours, but eventually you get...

As far as fixing this bug is concerned: I would suggest reverting to an older postfix db type such as hash or berkeley db rather than relying on this newfangled buggy lmdb thing, or even moving to SQL. Perhaps lmdb isn't buggy but postconf is doing_it_wrong in the way it uses the thing, or...

After installing some debug packages and doing some more digging, I've managed to reproduce a readable backtrace; Breakpoint 2.14, 0x00007ffff7e2d920 in write () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff7e2d920 in write () from /lib/x86_64-linux-gnu/libc.so.6 #1...

Did some more digging as to the cause of the bug; I briefly replaced the executable with a shell script that logs the stdin parameter so I could figure out the JSON I needed to send (rather than trying to understand all the python code behind the migration tool backend). This allowed me to...

I'm also seeing this issue (sometimes, more rarely), same library: [2026-02-26 13:09:05.431] 2710126:69a037da9a63b ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mailmng-core' '--add-domain' '--domain-name=buses.nl' '--disk-quota=0'] with exit code [1] An error occurred during domain...

Unfortunately for me, while reloading the mdb database does remove some of the issues the mdb tools seem to be having with this file, it doesn't actually help in resolving the issue. If I remove the subscriptions and re-try the migration for the offending ones only, they seem to still be...

One of the things I'm also dealing with, which is a bit of a bummer, is that when the migration does fail in this kind of way, that the destination server is left in a big mess. It partially creates a bunch of stuff, and so if you ask the migrator to re-do or re-sync the failed domains, it...

I've used the following to work around the issue. Note that I don't know if this could lead to some data loss. The trick is to dump, then re-load the mdb database. dir=/var/spool/postfix/plesk/ db=virtual printf -v date '%(%Y-%m-%d-%H-%M-%S)T\n' -1 mdb_dump -n ${dir}/${db}.lmdb >...

There's probably also something else I have to note about this strange issue: It's not consistent. It happens roughly 53.2% of the time (direct measurement). However, given that this is not too many samples, that figure isn't very accurate. It's fairly likely the real chance is just 50/50. (A...

A large proportion of migrations fail when migrating between servers with a sizeable number of domains (>100) with the following C error: stderr: [2026-02-24 16:37:15.295] 917424:699dc59ea1a8b ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mailmng-core' '--add-domain'...

I have to note that the invalid JSON issue appears to be transient: Hard-refreshing the page (CTRL+F5) is a workaround.

The next problem I encountered is with subdomains. Subdomains of a domain aren't properly migrated. The files are moved, the databases are moved, but the panel's awareness of them isn't. So their PHP settings and certificates are not assigned even if you migrate over the certificate to the new...

There are some technical problems with the Plesk Migrator tool if it's being used to migrate a domain from a 'higher tier' version of plesk to a 'lower tier' one; from a shared hosting server to a private hosting server that's only serving one domain and thus only requires the web admin edition...

I found another way around: Just running: will re-generate the apache config properly and include the 'lists' section. <VirtualHost 127.0.0.1:7080 127.0.0.1:7082> DocumentRoot "/var/www/vhosts/default/htdocs" ServerName lists ServerAlias lists.*...

I need to do this manually, so I need a complete list of what it does. I have a server with a bunch of migrated mailing lists but this step is not done correctly nor completely by the migration tool. Backing up the database table, re-installing mailman, and restoring (or re-migrating) also...