DB restore always fails!

  • Resolved m107

    (@m107)


    1 month, 4 weeks ago

    DB restore always fails, here is the last lines from the log:

    0003.362 () Old table prefix: dpu_ 0003.362 () UpdraftPlus plugin slug: updraftplus/updraftplus.php 0003.362 () Site information: multisite=0 0003.362 () Site information: sql_mode=NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION 0003.363 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.363 () New table prefix: i1_ 0003.439 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.441 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0003.442 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.464 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0003.551 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.555 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0003.564 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.565 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0003.566 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.569 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0003.569 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0003.588 () Processing table (InnoDB): dpu_icl_string_translations - will restore as: i1_icl_string_translations 0004.469 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.469 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0004.491 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.492 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0004.690 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.778 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0004.796 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.809 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; 0004.814 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.828 () Skipped execution of SQL statement (unwanted or internally handled type=18): /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; 0004.935 () Google Drive: ERROR: Have not yet obtained an access token from Google (has the user authorised?) (Invalid request (refresh token not present).) (no_refresh_token) 0004.935 () An error condition has occurred for the first time during this job 0077.234 () Unlocking database and leaving maintenance mode 0077.234 () Disabling Maintenance mode…

    how can I troubleshoot this? I tested backup and restore with another plugins and it worked just fine.+, but I prefer to stay with Updraft.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter m107

    (@m107)

    I gave all the logs to Chatgpt and the answer was this:

    The log file begins with an overview of the environment, including:

    • UpdraftPlus Version: 1.24.12
    • WordPress Version: 6.7.1
    • PHP Version: 8.2.26
    • MySQL Version: 8.0.40
    • Server: nginx/1.26.2
    • Max Packet Size: 64MB
    • Multisite: No

    I’ll analyze the full log content to identify any errors related to database restore failures. Let me proceed. ??

    The log entries indicate the restore process is initializing but does not provide clear error messages specific to database failures in the lines reviewed. Some potential issues:

    1. AJAX Calls for Restore: The restore process depends on AJAX, which can fail due to timeouts or server configuration issues.
    2. File Handling: The system is attempting to process multiple parts of the backup (e.g., uploads parts). If there are missing parts or corrupt files, this could interrupt the restore.
    3. WP_Filesystem Setup: While the setup appears to be successful, any subsequent errors here could impede restoration.

    Let me search deeper in the logs for explicit database-related failures. ??

    The log does not explicitly report a failure related to the database restoration process in the reviewed lines. However, several possibilities could explain persistent restore failures:

    1. Server Limits:
      • The log mentions the max execution time (900 seconds) and memory limits. If the database restore exceeds these limits, it could fail.
    2. File Integrity:
      • If any database backup files are incomplete or corrupted, the restore will fail. Ensure the backup files are complete and valid.
    3. MySQL Configuration:
      • The MySQL max packet size is 64MB. Large database files exceeding this limit might fail to restore. Consider increasing this limit temporarily for restoration.
    4. Timeout Issues:
      • AJAX-based processes are prone to timeout issues, especially for large databases. Check if the restore halts after a specific duration.

    Suggested Actions:

    • Verify the integrity of the backup files.
    • Temporarily increase server limits:
      • Max execution time.
      • MySQL max packet size (max_allowed_packet).
    • Use manual database restoration via tools like phpMyAdmin or the MySQL command line if UpdraftPlus continues to fail.
    Plugin Support nrobertsudp

    (@nrobertsudp)

    Hi there,

    The first thing I noticed in your log files is the following message:

    0004.935 () Google Drive: ERROR: Have not yet obtained an access token from Google (has the user authorised?) (Invalid request (refresh token not present).) (no_refresh_token)

    Are you attempting to restore from a backup on your Google Drive?
    The message indicates you would need to reauthorize Drive access.

    Best regards,

    Nick

    Thread Starter m107

    (@m107)

    the backup was restored either from ftp or lical, notjing to do with Google drive.

    • This reply was modified 1 month, 4 weeks ago by m107.
    • This reply was modified 1 month, 4 weeks ago by m107.
    Plugin Support nrobertsudp

    (@nrobertsudp)

    Hi there,

    That’s a bit strange as the log file is referring to Google Drive for some reason.
    Can you please attempt the restore again and provide me with the full log file?

    Best regards,

    Nick

    Thread Starter m107

    (@m107)

    @nrobertsudp how can I send you all the logs safely?

    Plugin Support nrobertsudp

    (@nrobertsudp)

    Hi there,

    Normally people share logs using Pastebin or a similar service.

    Best regards,

    Nick

    Thread Starter m107

    (@m107)

    I want it to be private, only for you AND I want to send about 20 logs.

    Plugin Support nrobertsudp

    (@nrobertsudp)

    Hi there,

    There are restrictions in place on the forum which prevent sharing email addresses.
    You could use a search and replace to remove any info you consider to be sensitive.

    Best regards,

    Nick

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.