• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Plesk Migrator problem 18.0.27 - database users

HMnet

Basic Pleskian
Hello!

I have a problem with the Migrator 2.19.4-921. I want to migrato from my Plesk 12.5.30 - Server to my new Ubuntu 18.04 with Plesk 18.0.27.

If there is a database with a user, that is connected to this db, the log says:

2020-05-24 14:18:55Info
log-collapse-icon.gif

START: Deploy databases
2020-05-24 14:18:55Info

Create database 'xxx' in subscription 'xxx.de'
2020-05-24 14:18:55Info

Create database 'xxx_TYPO3' in subscription 'xxx.de'
2020-05-24 14:18:56Info

Create database 'xxx_v2017' in subscription 'xxx.de'
2020-05-24 14:18:57Info
warning.png

log-collapse-icon.gif

START: Deploy database users
2020-05-24 14:18:57Warning

Database user 'xxx' belongs to database 'xxx' which is not registered in Plesk, but already exists in Plesk database server, so skip the database user
2020-05-24 14:18:57Warning

Database user 'xxxTYPO3' belongs to database 'xxx_TYPO3' which is not registered in Plesk, but already exists in Plesk database server, so skip the database user
2020-05-24 14:18:57Warning

Database user 'xxxV2017' belongs to database 'xxx_v2017' which is not registered in Plesk, but already exists in Plesk database server, so skip the database use

So the database users weren't migrated!

Yours
Thomas
 
Hi,

I have the same situation, I try to migrate from an old server 12.5 to latest Plesk.
Until now the only big issue is this error where database users are not copied at all.

@HMnet Did you find out any fix for this?

Thanks
 
Hey AndreiLx,

unfortunately not! I created the concerning database users manually.
The issue did not occure at every database...

Greetings!
 
Back
Top