• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Error in migration due to SQL problem

EnriqueR

Regular Pleskian
Server operating system version
Ubuntu 20.04.5
Plesk version and microupdate number
Plesk Obsidian Version 18.0.46 Update 2
I have a server running CentOS 6.10 Plesk Obsidian Version 18.0.31 Update 3. I want to migrate all subscriptions to another Server running Ubuntu 20.04.5 Plesk Obsidian Version 18.0.46 Update 2.

The problem is that when I give new migration, when trying to connect to the CentOS server, I get the following error:

Failed to generate migration list file
Cause: Command execution failed on the local server with non-zero exit code.
command: MYSQL_PWD="$(cat /etc/psa/.psa.shadow)" mysql --silent --skip-column-names -u admin psa -e 'SHOW VARIABLES LIKE '"'"'socket'"'"''
exit code: 7
stdout:
stderr: mysql: unknown variable 'wait_timeout=31536000'

That is a critical error, migration was stopped.

I have added the 'wait_timeout' tag to the my.cnf file (because it didn't exist), but it still gives me the same error. Can you help me to know the reason for this error?
 

Attachments

  • Captura.JPG
    Captura.JPG
    31.9 KB · Views: 3
Make sure that this variable 'wait_timeout=31536000' is enabled for some reasons in /etc/my.cnf config file.
Comment it and restart MySQL service.
 
Ok, the problem was that I understood that the change had to be made on the source server, but not is so, the change had to be made on the destination server, which in my case is Ubuntu.
 
Back
Top