[Case 44609,44690] Errors on migration from Plesk to cPanel after 11.28 update

zeki79

Member
Sep 17, 2010
20
1
53
hello

on 11.26 i dont had problems. now with 11.28.27 i transfered a domains from my old plesk server 9.x to the cpanel server iand have this issues:

1. users was created as "account\_glr" -> why this backslash?!
2. the useraccount is not listed under "Mysql Services, Change MySQL DB Owner Password"
3. i cant delete the useraccounts with the \ in the username
- i cant start phpmyadmin as user ( i think point 2 is the problem)
4. the weird useraccount -> i cant see it on the mysql server, only cpanel list it..

any others with issues with migrations from plesk?

thanks
zek
 

zeki79

Member
Sep 17, 2010
20
1
53
others inputs:

1. i saw, that this domain is the only one that the account name have more than 8 letters. can this be the problem? its possible to rename the account?

2. why cpanel dont cut it down to 8 letters on the migration, like i older versions?

greets
zeki
 

zeki79

Member
Sep 17, 2010
20
1
53
next inputs:

1. i migrated another domain. on the cpanel server i have the sql databases/usernames correct but i have a database called "*" and all sql userlogins have access to it. whats that?

2. the user cant login to his phpmyadmin (i think its the same error like i described above. i dont see the user in whm under mysql, "change mysql user owner password"

anyone from cpanel intrested to debug these bugs in 11.28?

greets
zeki
 

zeki79

Member
Sep 17, 2010
20
1
53
thats the only messages i see on the creation of the account after the data is transfered to the cpanel server:


--
Restoring MySQL privs

Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.


Database or database user has no prefix and the system is configured to use prefixes.

--
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
Hello Zeki,

Please open a ticket about these issues so we can investigate further. If possible, it would be great to terminate the account experiencing these issues on the cPanel machine before opening the ticket, then we can try to re-transfer it to the cPanel machine to see the results.

To open a ticket, please either use WHM > Support Center > Contact cPanel or the link in my signature.

Thank you.
 

JoshuaBusby

Registered
Apr 7, 2009
2
1
53
Houston, TX
Hello Zeki,

I have received your ticket and I am looking into it the issue, we'll continue the troubleshooting through your open ticket 1026302.

Thank you
 

jdistad

Member
Nov 15, 2010
5
0
51
I am experiencing almost the exact same DB issues when doing account copies from version 11.28.35 to 11.28.35

The account creation process seems to go fine but in the end all that is created for the db is one named * that is 0mb in size. I am not getting any db or user from the move. I also get the log message saying "Database or database user has no prefix and the system is configured to use prefixes."

If I create the db/user combo and do a export/import all works fine but thats a hassle I would rather not have to do each time. Is there any new "news" on this at all yet?

thanks in advance
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
You will need to disable prefixing on the cPanel server in WHM > SQL Services > Disable Database Prefix area for these databases to import over correctly. Once you've done that change, the databases will copy over during the account transfer and you shouldn't have to make changes to your connection scripts like used to be required in the past.

For the * named database, we have an internal bug case (44609) opened about the creation of that incorrect database name type.
 

jdistad

Member
Nov 15, 2010
5
0
51
Thanks for the reply, I saw that selection in there but the message concerned me, where it says:

"Once done, this is not reversible.

You also will not be able to downgrade to a version of cPanel/WHM that does not support Database Mapping."

Are there benefits to leaving this on that would outweigh the hassle of manually exporting and importing about 10 databases? (I have already done about 10 this way)

thanks for your input.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
The one portion about being unable to downgrade won't be applicable soon as STABLE will be going to 11.28. 11.26 is the version of cPanel/WHM that doesn't support database mapping with prefixing off.

As for the benefits versus the cons to disabling prefixing, the benefit would be that you can easily transfer Plesk to cPanel accounts at any point to the machine without having to make changes to the database connections. They should transfer seamlessly with prefixing off.

The con would be that prefixing will no longer exist for any accounts going forward for database creation, so users can create databases without their username prefixed to the database name or database user's name, so you won't have user1_dbname for the database nor user1_dbuser for the database users. You can still determine who owns which databases in /var/cpanel/databases area as that will contain a listing of the mapped databases via the dbindex.db and users.db files.
 

jdistad

Member
Nov 15, 2010
5
0
51
OK, thanks for the info... the part I don't get is that all the accounts I am transferring are coming from WHM/cPanel (same version even) and all databases have prefixes. why would it be telling me that I need to disable prefixes when the db's are already setup that way?
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
Ah, I didn't realize these were both cPanel machines, although you did state 11.28.35 initially and I missed that. Could you please open a ticket about these transfers? You could use WHM > Support Center > Contact cPanel or the link in my signature. If both cPanel machines are the same version and both have prefixing enabled (so it isn't disabled), then you shouldn't be receiving this message. We'd need to see what's happening in this instance.

Please post the ticket number here after you've opened it for reference.

Thanks!
 

jdistad

Member
Nov 15, 2010
5
0
51
Ticket #1028737 has been submitted.



Ah, I didn't realize these were both cPanel machines, although you did state 11.28.35 initially and I missed that. Could you please open a ticket about these transfers? You could use WHM > Support Center > Contact cPanel or the link in my signature. If both cPanel machines are the same version and both have prefixing enabled (so it isn't disabled), then you shouldn't be receiving this message. We'd need to see what's happening in this instance.

Please post the ticket number here after you've opened it for reference.

Thanks!
 

zeki79

Member
Sep 17, 2010
20
1
53
You will need to disable prefixing on the cPanel server in WHM > SQL Services > Disable Database Prefix area for these databases to import over correctly. Once you've done that change, the databases will copy over during the account transfer and you shouldn't have to make changes to your connection scripts like used to be required in the past.

For the * named database, we have an internal bug case (44609) opened about the creation of that incorrect database name type.
hi
on my system it has no effect to disable the prefix. i have the same erros :(
the migration support is analyzing waht can be the error

btw: it is possible to reenable prefix, when no users have created a database or useraccount?

greets
zek
 

jdistad

Member
Nov 15, 2010
5
0
51
This is really starting to get frustrating...

I received an email from support telling me that the bug was resolved and that I could upgrade to the latest build of 11.28.39

so I did that on both servers, tried a transfer and got the SAME result... the bug that was fixed was the "creating a database named *" and not the "bug" I am having an issue with.

I then emailed them back, telling them that this was the case... so they went in and created an account and transfered it... well, that worked.. so it must have something to do with existing (old) accounts because whenever I try to transfer an account I get no DB, no user and the error message about prefixes.

I am also having issues terminating accounts now on the new server, it just hangs indefinitely at "Sending Contacts" in a little popup box... I have to get all the sites off the old server and onto this new one by tomorrow morning so I would really really appreciate some input on what I should do next.
 

zeki79

Member
Sep 17, 2010
20
1
53
wow - the bug with "*" databse is fiex with 11.28.39
Case 44609: transfer creates "*" in mysql user yaml

you are really fast with bugfixing! thatts great!


now lets fix the other point (2 and 3) see obove
details are in ticket ID# 1026302

thanks
zeki
 

zeki79

Member
Sep 17, 2010
20
1
53
hello
last update from support

after reseting the password of the account in whm (not in cpanel) the mysql userlist gets updated and phpmyadmin works. a good workarround. the bug is fiex in a future release case 44690

point 1 still here. i update this thread wh i know how to remove this "false transfered account" from the database.


greets
zeki
 

cPanelJesse

Director of Technical Support
Staff member
Sep 19, 2007
52
7
133
Houston
cPanel Access Level
Root Administrator
hello
last update from support

after reseting the password of the account in whm (not in cpanel) the mysql userlist gets updated and phpmyadmin works. a good workarround. the bug is fiex in a future release case 44690

point 1 still here. i update this thread wh i know how to remove this "false transfered account" from the database.


greets
zeki
The fix for case 44690 is now available in CURRENT and RELEASE.