• Resolved baker@alanbaker.net

    (@bakeralanbakernet)


    Hi Yani,

    I’ve used All-In-One WP Migration many many times and it has worked great. But today restoring my usual template instance hangs at 0% complete while restoring the database. I’ve reinstalled WordPress and done new exports, but import always hangs.

    The environment: Hostmonster, WordPress 6.01 on fresh installation, PHP 8.1.4, All-in-One WP Migration 7.62

    The error log has dozens of lines like:

    Aug 13 2022 01:33:46
    {“type”:8192,”message”:”Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice”,”file”:”\/home3\/sirinctw\/public_html\/branch95t\/wp-includes\/Requests\/Utility\/CaseInsensitiveDictionary.php”,”line”:91}

    Suggestions, please?

    Alan

    The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)
  • I have the same issues, nor I’m not getting any error. any idea where I can see an error log or the reason why ?
    Any special permissions needed ?

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    The error log is located at
    wp-content/plugins/all-in-one-wp-migration/storage/error.log
    and it’s world-readable.

    Do the messages in your error log refer to CaseInsensitiveDictionary.php?

    What PHP version are you using? Tools > Site Health > Info > Server

    Plugin Author Yani

    (@yaniiliev)

    How large is the file that you are trying to import?
    The error looks like a deprecation warning – it might not be the culprit.
    Try waiting for some time and see if the database restore progresses.
    Also, you can try to export just the database and import it to see if the problem is in the database.

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    Yes, those messages in the error log look like deprecation warnings. There are no other messages there.

    The .wpress file I was trying to import was 166 MB. I tried exporting and importing just the database (2MB) with the same result.

    So I exported an altogether different WordPress site (234 MB). I get the same result when I tried to import it–hangs at 0% while attempting to restore the database. I let it run for an hour.

    Other ideas?

    Alan

    Plugin Author Yani

    (@yaniiliev)

    Try to open a new tab and load the website.
    If it is white screen, enable WP_DEBUG in wp-config.php by setting it to true.
    Do you see any errors?

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    PHP memory was 512M. The debug.log showed

    `[15-Aug-2022 23:02:10 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 77
    [15-Aug-2022 23:02:10 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-includes/class-wp-fatal-error-handler.php on line 73`

    so in wp-config.php I added

    define(‘WP_MEMORY_LIMIT’, ‘640M’);

    Then the debug.log showed

    [15-Aug-2022 23:40:33 UTC] PHP Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 64
    [15-Aug-2022 23:40:33 UTC] PHP Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

    It’s been running fine in 512M for a long time. What could have changed?

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    Similar results with 7.63. How can I help resolve this?

    [17-Aug-2022 13:11:32 UTC] PHP Fatal error:  Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 64
    [17-Aug-2022 13:11:32 UTC] PHP Fatal error:  Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0
    [17-Aug-2022 13:11:42 UTC] PHP Fatal error:  Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 64
    [17-Aug-2022 13:11:42 UTC] PHP Fatal error:  Allowed memory size of 671088640 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0
    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    I reverted the PHP version from 8.1 to 7.4 and increased memory to 704 MB, but the result is the same.

    [17-Aug-2022 16:39:17 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 77
    [17-Aug-2022 16:39:17 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-includes/class-wp-fatal-error-handler.php on line 73
    [17-Aug-2022 16:39:38 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 69
    [17-Aug-2022 16:39:39 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-includes/class-wp-fatal-error-handler.php on line 73
    [17-Aug-2022 16:40:02 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/database/class-ai1wm-database-utility.php on line 69
    [17-Aug-2022 16:40:02 UTC] PHP Fatal error:  Allowed memory size of 738197504 bytes exhausted (tried to allocate 20480 bytes) in /home3/sirinctw/public_html/branch95t/wp-includes/class-wp-fatal-error-handler.php on line 73

    I don’t know why this thread is marked as resolved.

    Plugin Author Yani

    (@yaniiliev)

    There is a large object stored in your database. When the plugin tries to unpack this object, the server runs out of memory. You need to increased the available memory (try 2G) or clean the database from this object.

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    OK. The .wpress file is 166MB and I have imported it many times before (it’s a minimal starter instance).

    I increased memory to 2GB and this time the import did not exhaust the memory. I let it run for 3.5 hours and the database restore never progressed beyond 0% complete. The debug.log contained only deprecation warnings and the following database errors.

    [17-Aug-2022 19:04:23 UTC] WordPress database error Table 'sirinctw_br59t.br95_actionscheduler_groups' doesn't exist for query SELECT group_id FROM br95_actionscheduler_groups WHERE slug='wpforms' made by require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WPForms\WPForms->WPForms\{closure}, WPForms\Tasks\Tasks->init, WPForms\Emails\FetchInfoBlocksTask->__construct, WPForms\Emails\FetchInfoBlocksTask->init, WPForms\Tasks\Task->register, WPForms\Tasks\Task->register_recurring, as_schedule_recurring_action, ActionScheduler_ActionFactory->recurring, ActionScheduler_ActionFactory->store, ActionScheduler_DBStore->save_action, ActionScheduler_DBStore->get_group_id
    [17-Aug-2022 19:07:24 UTC] WordPress database error Table 'sirinctw_br59t.br95_actionscheduler_claims' doesn't exist for query SHOW FULL COLUMNS FROM <code>br95_actionscheduler_claims</code> made by do_action('wp_ajax_as_async_request_queue_runner'), WP_Hook->do_action, WP_Hook->apply_filters, WP_Async_Request->maybe_handle, ActionScheduler_AsyncRequest_QueueRunner->handle, do_action('action_scheduler_run_queue'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_QueueRunner->do_batch, ActionScheduler_DBStore->stake_claim, ActionScheduler_DBStore->generate_claim_id
    [17-Aug-2022 19:07:24 UTC] WordPress database error Table 'sirinctw_br59t.br95_actionscheduler_logs' doesn't exist for query INSERT INTO <code>br95_actionscheduler_logs</code> (<code>action_id</code>, <code>message</code>, <code>log_date_gmt</code>, <code>log_date_local</code>) VALUES (577, 'action ignored via Async Request', '2022-08-17 19:07:24', '2022-08-17 19:07:24') made by do_action('wp_ajax_as_async_request_queue_runner'), WP_Hook->do_action, WP_Hook->apply_filters, WP_Async_Request->maybe_handle, ActionScheduler_AsyncRequest_QueueRunner->handle, do_action('action_scheduler_run_queue'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_QueueRunner->do_batch, ActionScheduler_Abstract_QueueRunner->process_action, do_action('action_scheduler_execution_ignored'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_Logger->log_ignored_action, ActionScheduler_DBLogger->log
    [17-Aug-2022 20:47:04 UTC] WordPress database error Table 'sirinctw_br59t.br95_actionscheduler_logs' doesn't exist for query SHOW FULL COLUMNS FROM <code>br95_actionscheduler_logs</code> made by require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WPForms\WPForms->WPForms\{closure}, WPForms\Tasks\Tasks->init, WPForms\Emails\FetchInfoBlocksTask->__construct, WPForms\Emails\FetchInfoBlocksTask->init, WPForms\Tasks\Task->register, WPForms\Tasks\Task->register_recurring, as_schedule_recurring_action, ActionScheduler_ActionFactory->recurring, ActionScheduler_ActionFactory->store, ActionScheduler_DBStore->save_action, do_action('action_scheduler_stored_action'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_Logger->log_stored_action, ActionScheduler_DBLogger->log
    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    Hi Yani,

    I get the same issue when importing an altogether different website. How do I proceed?

    Alan

    Plugin Author Yani

    (@yaniiliev)

    Try to export with plugins disabled. Then import.
    After import, enable plugins one by one.
    It could be a plugin incompatibility.

    Thread Starter baker@alanbaker.net

    (@bakeralanbakernet)

    Hi Yani,

    Good call. It was a plugin incompatibility on the import side. Hostmonster automatically installs WPForms Lite with each new instance and that conflicted with WPAIOM at import time. Deactivating WPForms Lite allowed the import to complete normally.

    In the past, the imported site completely replaced the original site. Today when I imported the site, both the original site’s and the imported site’s plugins and themes remained in the new site. Is this the expected behavior?

    Plugin Author Yani

    (@yaniiliev)

    In the past, the imported site completely replaced the original site. Today when I imported the site, both the original site’s and the imported site’s plugins and themes remained in the new site. Is this the expected behavior?

    Yes, this is the expected behavior. If you’d like a clean slate, start with an empty WordPress site and import from it.
    We will introduce an option to clean a website before import in future versions of the plugin.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Restoring database hangs at 0% complete’ is closed to new replies.