Export migration fails repeatedly during media stage
-
I don’t even get an explanation or anything that can pinpoint the reason for the failure. All that happens is that it craps out during the media stage. Nothing to indicate why. Just “An unknown error occurred. Please check your PHP error log or contact support.”
The page I need help with: [log in to see the link]
-
Hi there!
WP Migrate Support Team here, Thanks for reaching out with your query we would be happy to assist
Can you try editing your wp-config.php file to replace this line –
define( ‘WP_DEBUG’, false );
With these lines –
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);
This means that any errors are logged to /wp-content/debug.log, because some errors are not visible on screen.
Can you try the process again and then send on the debug.log file if created please.
More details about that at https://codex.www.ads-software.com/Editing_wp-config.php#Debug
Thank you.Made the changes you indicated. Export crapped out again at 5%.
Where would I find the debug.log file?
Found it. Almost 3 MB of ASCII. Can’t paste it here. Is there an email address I can send it to?
Hi sol0712,
Could you check the debug.log file if you see any fatal errors around the time you were doing the migration?
If there are no fatal errors, could you check for us if there are any PHP warnings related to WP Migrate Lite?
Hi guys: Searching for “migrate” yields this:
[19-Oct-2023 02:19:30 UTC] WP Migrate – Failed to instantiate object for replacement. If the serialized object’s class is defined by a plugin, you should enable that plugin for migration requests. Class Name: GoogleSitemapGeneratorStatus
Hi @sol0712,
Thanks for the response.
Unfortunately, that shouldn’t interfere with the export.
Can you also please check your browser’s debugging console to see if there are any errors reported when the issue occurs? For instructions on how to do this, see
https://deliciousbrains.com/wp-migrate-db-pro/doc/debugging-browser-console-errors/
Also, would you be able to send me the debugging information from the Help tab on the site you’re having trouble with?
- Go to the Help tab of your local install
- Scroll down to the “Diagnostic Info & Error Log”
- Click the “Download” button and save to your computer
- Reply to this email and include the text file as an attachment
Please feel free to hide any sensitive info you might find there. We would just like to see your current site’s setup as well as any errors logged by our plugin.
Looking forward to hearing back!
Hello DB Support:
Here’s what happened in the Console with the latest failed export:
Unchecked runtime.lastError: The message port closed before a response was received.
tools.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
tools.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
tools.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
tools.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
tools.php:1 Unchecked runtime.lastError: The message port closed before a response was received.
5co63n4jqq:1 Unchecked runtime.lastError: The message port closed before a response was received.
5co63n4jqq:1 Unchecked runtime.lastError: The message port closed before a response was received.
5co63n4jqq:1 Unchecked runtime.lastError: The message port closed before a response was received.
5co63n4jqq:1 Unchecked runtime.lastError: The message port closed before a response was received.
jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 3.4.1
mtgm.js:92 [Deprecation] Listener added for a synchronous ‘DOMNodeInserted’ DOM Mutation Event. This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types) and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.
(anonymous) @ mtgm.js:92
Show 1 more frame
Show less
mtgm.js:92 [Deprecation] Listener added for a synchronous ‘DOMNodeInserted’ DOM Mutation Event. This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types) and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.
(anonymous) @ mtgm.js:92
Show 1 more frame
Show less
pipedream.wistia.com/mput?topic=metrics:1Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
simpleMetrics.js:25
Uncaught (in promise) TypeError: Failed to fetch at u (simpleMetrics.js:25:10) at simpleMetrics.js:80:21
distillery.wistia.com/x:1
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
pipedream.wistia.com/mput?topic=metrics:1
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
metrics.js:62
Uncaught (in promise) TypeError: Failed to fetch at p (metrics.js:62:10) at metrics.js:45:17
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
/wp-json/mdb-api/v1/mf-transfer-files:1
Failed to load resource: the server responded with a status of 500 ()
Also, you’ll need to be a little more specific about where I find the Diagnostic Info & Error Log. It’s not under the Help button for Chrome, the Console, or WordPress.
Sol
Hi @sol0712,
Thank you for your response.
It sounds like you are getting a server error during your migration. Information about server errors and why they occur can be found in this doc: https://deliciousbrains.com/wp-migrate-db-pro/doc/500-internal-server-errors/
As for the diagnostic info, it can be found on the Help tab in the plugin. See:
Kindly send it in, so we can understand your current setup.
We look forward to your response!
Diagnostic info?
site_url(): https://urbaneer.com
home_url(): https://urbaneer.com
site_path(): /home/urbaneer/public_htmlDatabase Name: urbaneer_wp01
Table Prefix: wp_qb3xiwdvsh_WordPress Version: 6.3.2
WP Migrate DB: 2.6.9
Web Server: ………………… LiteSpeed
PHP: ………………………. 7.4.33
WP Memory Limit: ……………. 40M
PHP Time Limit: …………….. 360
Blocked External HTTP Requests: None
fsockopen: …………………. Enabled
OpenSSL: …………………… OpenSSL 1.1.1p 21 Jun 2022
cURL: ……………………… Enabled
Enable SSL verification setting: No
Opcache Enabled: ……………. EnabledMySQL: ………………. 5.5.5-10.5.22-MariaDB
ext/mysqli: ………….. yes
WP Locale: …………… en_CA
DB Charset: ………….. utf8
WPMDB_STRIP_INVALID_TEXT: NoDebug Mode: … No
Debug Log: …. No
Debug Display: Yes
Script Debug: No
PHP Error Log: error_logWP Max Upload Size: 384 MB
PHP Post Max Size: 384 MBWPMDB Bottleneck: …… 1 MB
Compatibility Mode: …. Yes
Delay Between Requests: 0WP_HOME: ……. Not defined
WP_SITEURL: …. Not defined
WP_CONTENT_URL: https://urbaneer.com/wp-content
WP_CONTENT_DIR: /home/urbaneer/public_html/wp-content
WP_PLUGIN_DIR: /home/urbaneer/public_html/wp-content/plugins
WP_PLUGIN_URL: https://urbaneer.com/wp-content/pluginsMedia Uploads
Transfer Bottleneck: …… 384 MB
Upload Folder Permissions: 755Themes & Plugins
Transfer Bottleneck: ……… 384 MB
Themes Permissions: ………. 755
Plugins Permissions: ……… 755
Must-Use Plugins Permissions: 755
WP-Content Permissions: …… 755
WP-Core Permissions: ……… 750Active Theme Name: WordHerd Theme
Active Theme Folder: /home/urbaneer/public_html/wp-content/themes/wordherd-impreza
Parent Theme Folder: ImprezaActive Plugins
- Gravity Forms (v2.7.15) by Gravity Forms
- Admin Page Spider (v3.20) by J7Digital
- Advanced Custom Fields PRO (v6.2.0) by WP Engine
- Akismet Anti-spam: Spam Protection (v5.3) by Automattic – Anti-spam Team
- API KEY for Google Maps (v1.2.9) by AyeCode Ltd
- Buttons to Edit Next/Previous Post (v1.2) by Aftab Muni
- Classic Editor (v1.6.3) by WordPress Contributors
- Custom Post Type UI (v1.14.0) by WebDevStudios
- Duplicate Page (v4.5.3) by mndpsingh287
- Site Kit by Google (v1.111.1) by Google
- XML Sitemap Generator for Google (v4.1.13) by Auctollo
- GravityWP – CSS Selector (v1.0.2) by GravityWP
- WPCode Lite (v2.1.3.1) by WPCode
- Jetpack (v12.7) by Automattic
- WPBakery Page Builder (v7.0) by Michael M – WPBakery.com
- LiteSpeed Cache (v5.7) by LiteSpeed Technologies
- Safe SVG (v2.2.0) by 10up
- Similar Posts (v3.1.6) by Shareaholic
- Simple Lightbox (v2.9.3) by Archetyped
- SiteOrigin CSS (v1.5.8) by SiteOrigin
- Stylish Links (v1.0.3) by Industrial Themes
- UpSolution Core (v8.18.5) by UpSolution
- Username Changer (v3.2.2) by Widgit Team
- What The File (v1.6.0) by Never5
- WP Categories Widget Pro (v1.2) by WP-EXPERTS.IN TEAM
- WP Categories Widget (v2.3) by WP-EXPERTS.IN TEAM
- WP Migrate Lite (v2.6.9) by WP Engine
- WP-PageNavi (v2.94.1) by Lester ‘GaMerZ’ Chan
- YellowPencil (v7.6.0) by WaspThemes
Must-Use Plugins
- index.php
- Force Strong Passwords – WPE Edition (v1.6.4) by Jason Cosper
- WP Migrate Lite Compatibility (v1.3) by Delicious Brains
Log date: 2023/10/16 22:52:55
Migration ID: 4ae32d68-136e-4ecc-aa2e-c14eb8880c67
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231016203638-7i8ef.zip does not existLog date: 2023/10/17 01:52:21
Migration ID: e5ab3d06-8310-4c17-a755-647d7cdd74ae
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231017012808-3x42u.zip does not existLog date: 2023/10/17 02:20:52
Migration ID: 3b4c2ce6-4c80-4a1e-b9a9-1653eaf17343
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231017020029-xyfdu.zip does not existLog date: 2023/10/17 16:34:12
Migration ID: 77f82184-23fc-40f8-8adb-27c39425b63b
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231017153410-crigt.zip does not existLog date: 2023/10/18 20:54:16
Migration ID: 86e031bc-b00f-4b51-8993-d3cdf883c010
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231018202816-blqrk.zip does not existLog date: 2023/10/19 02:43:26
Migration ID: 3bf5a41d-ca22-498d-ba0f-6e6efd9baeb6
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231019021927-4vbjm.zip does not existLog date: 2023/10/23 15:42:19
Migration ID: 0811c078-7036-4ad4-ad58-d32f70a556b8
Intent: savefile
Stages: tables | media_files | theme_files | plugin_files | core_files
Action: cancel
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231023151408-ajhb6.zip does not existHi @sol0712,
Thanks for sending that in. Regarding this error:
Error: ZIP Archive /home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/urbaneer-20231023151408-ajhb6.zip does not exist
It seems WP Migrate Lite couldn’t find the export file in the wp-migrate-db directory. Could you check for us if the directory below is writeable? The folder permission should something like 755.
/home/urbaneer/public_html/wp-content/uploads/wp-migrate-db/
Also, could you confirm for us that you have enough free storage space on your server?
- The topic ‘Export migration fails repeatedly during media stage’ is closed to new replies.