• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Issue migration of site failing - DB issue

weareimpulse

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update #2 Web Host Edition
hi, can anyone help me, i;m trying to migrate a website from an older server to a newer one using the PLESK migrate tool - I've done this a few times before, and never had an issue like this.

I think its due to the size of the DB, and i get this error in the 'details' view on the migration once i've run it.

Any idea please?
 

Attachments

  • Screenshot 2025-02-11 at 13.38.57.png
    Screenshot 2025-02-11 at 13.38.57.png
    51.6 KB · Views: 6
so i did the restart...
systemctl restart mysql || systemctl restart mariadb || systemctl restart mysqld


go these errors...

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.
 
Back
Top