ispconfig does not resopnd on new server after migration

Please do not post such logs; they can contain passwords, and yours did. I removed the log file now and I was the first one who viewed it according to the forum software, so it should be ok. If you need help with the migration tool, please email us at support at ispconfig dot org or use the support contact form on the website ispconfig.org. To find out why the new server rejected the mysql dump from the old one, you can us this command on the new server:

Code:

gunzip -c /tmp/migrate-import-tmp.sql.gz | mysql --max_allowed_packet=1G -h 'localhost' -D c1arevan -u 'root' -p

it will ask for the mysql root password.

 

Then, you might have restarted the server or run the tool again, which cleared the /tmp folder. Or you looked into /tmp on the wrong server, you must check the new server. Run the migration tool again, and when it stops, check /tmp folder on the new server (not the old server).

That's not from ISPConfig nor the Migration Tool.

 

You seem to be using an old version of the Migration Tool as a workaround for this MariaDB problem has already been implemented. I mentioned in post #18 of this thread a few days ago that you must re-download the tool. Please remove the old version of the Migration Tool by deleting the whole /root/migrate directory, then download the tool again and start it.

 

The latest version is 2.2.13, and it is from September 19 and several clients already reported that the fix in that version works for this issue. Did you really delete it before downloading it again on the old server? I've seen it several times that people accidentally use an old version again by not fully deleting it.

 

Nothing is missing there. That line is fine. What you see there is escaping a char by pretending a backslash.

We can't really help you when you post here in the forum instead of contacting the Migration Tool support as we require the full logs, everything else is just guesswork. I asked you already in post #22 to do that. Please run the tool with debug mode (add the --debug config option) and then send us an email with the complete migrate.log file the tool created to support at ispconfig dot org so we can see what is causing your issue.

 

Thank you for sending the log; it shows that the command to filter out the line is run, so you use the right version, and it filters out the line from MariaDB documentation, which is what other users have, too. But for some reason, your line seems to be different from what the official MariaDB docs say. May you please double-check that the line in your SQL dump file is this:

/*M!999999\- enable the sandbox mode */

the important part that differs is the M inside the string. Is that M really there? because normally and according to mariaDB docs, the line that needs to be filtered out is this:

/*!999999\- enable the sandbox mode */

 

Ok, then we will have to adjust the filter. Hopefully they do not come IP with more variations of this without describing them in their docs.

 

Just as info, a new version of the Migration Tool has been released which contains a fix for the MariaDB import issue when the source MariaDB version is newer than the target.