execution time error

Hi Aid,

Thanks for using Prime Mover plugin and sorry to hear you encountered a runtime error. Can you please click on the runtime error link to download the error log and sent it to us via this form? This way we will know the details of this error so we will if a workaround exists.

In addition – if you could no longer click the link or there is no log generated – please enable WordPress debugging mode and reproduce the issue again. Once the issue is reproduced – you should be able to generate the debugging logs needed. Please provide it to us by following the procedure on that tutorial.

Thanks again!

Cheers,

Emerson

hello,

There is no way to send a file through your contact form.

Thanks for the reply. You can either open the log and paste the contents on the form or zip the log (if it’s huge) and upload it to Gdrive or DropBox. And then send us the link to download link using the contact form.

If you can read the error (which mostly on top of the log) – you can check out our most common troubleshoot guides here: https://codexonics.com/prime_mover/prime-mover/#troubleshooting-guide just in case the error is already known and has a workaround.

If the error is something new or there is no mention of a workaround – please continue sending it to us. This way – we will know and can advise you further on the solutions.

Thanks again!

that is. thanks for your help.

• This reply was modified 7 months, 1 week ago by wotan6891.

Thanks, I have requested permission on the file – please grant it. Also these logs are not meant to be shared publicly on this forum – can you please remove the link on your reply? Thank you!

ok

? Thanks for the logs. Please give us time to analyze and reproduce the issue. In addition – would it be possible for?you to please send this file also via our contact form here?

/var/www/html/wp-content/mu-plugins/000-prime-mover-constants.php

?? Simply download that PHP file from your target server to your Desktop. And then open it with a text editor, copy all contents after <?php of that file and paste it to the contact form to send.

We would like to check and verify if some constants are set there. Thank you!

hello,

already sent

Thanks for all the logs, that was helpful! We managed to reproduce the issue by replicating the environment setup as your site (by analyzing those logs).

Your wp-config.php file does not have those anchor tags since it’s a bit customized. This is OK but the plugin didn’t handle that one correctly.

This is now fixed in our end. To confirm that it’s resolved also in your end, can you please try our latest Prime Mover 1.9.9-beta5 to see if it works? You can follow the testing steps as follows:

• Download our latest Prime Mover 1.9.9-beta FREE version.
• Deactivate Prime Mover 1.9.8 version in your site.
• Delete/uninstall all old Prime Mover versions in your /wp-content/plugins/
• Install and activate the latest Prime Mover 1.9.9-beta5 version (the one that you have downloaded in the first step).
• Try again restoring the package. You can save time restoring it by using the package manager approach instead of the direct browser uploading.
• Expected: You should be able to restore the package without the same runtime error as you have observed in this ticket.

Once you confirmed that it’s working – feel free to mark this ticket as resolved. Thanks!

hello,

3 times I have tried it freezes on this. and it takes 3 hours and goes on.

https://snipboard.io/IsCrgu.jpg

my file is 600 mb.

my file is 600 mb. Shouldn’t the upload mb be increased?

by the way, I work on localhost, using DDEV. then pass the file to the package area. and from there progress was made faster than yesterday, but it stagnates as seen in the photo.

• This reply was modified 7 months, 1 week ago by wotan6891.
• This reply was modified 7 months, 1 week ago by wotan6891.

Thanks for the update! From your screenshot it shows that the main issue on this ticket is resolved – you no longer see the runtime error when your start the restore – which is good.

Now for the second issue – we need to find out why. Prime Mover does not limit the package size – so 600 MB is doable and OK.

Can you please provide the WPRIME package that you have restored to your site? Please send the link to download via Google Drive link (just like how you shared your logs before) via this form.

We will try to reproduce your second issue using your WPRIME package in a test environment similar to yours. This way we will know if the problem is on your package or something related to your setup.

Hello,

I already sent you at this moment.

Thanks! I requested access to download the file since it’s restricted. Please grant. Please give us time to check this issue.

Thank you for the link to download the package. We tried importing the package but we are not able to reproduce it. The import is a success in first attempt. These are the environment tested:

================================
WordPress version: 6.5.2
PHP version: 8.1
OS: Linux
Locale: es_ES (Spanish)
Prime Mover version: 1.9.9-beta5
=================================

It was successfully restored after almost 3 hours (2.75 hours to be exact). Your database is so huge (100 MB+) that it took the most time in doing search and replace.
We have shared with you the screenshots of our testing – please refer to the email you used to share the package.We check your site front end and back-end – no issues found and it looks good.

Take note that we restore your package with a more strict environment (e.g. lower RAM, lower timeout, lower DB packet size value):

=================================
Database max allowed packet size
=================================

Your value: 268435456 (256MB)
Our test value: 67108864 (64MB)

===========================
RAM (Random access memory)
===========================

Your value: 1024M
Our test value: 256M

============================
Timeout / Server time limit
============================

Your value: no limit (unlimited)
Our test value: 30 seconds

Our test didn’t reproduce the issue on stuck on dB import. As a conclusion – your package is fine and Prime Mover was able to restore the site. The issue is most likely in your own server setup.

As a recommendation – please refer to the following tips to restore the package:

• Use Prime Mover latest version (e.g. Prime Mover 1.9.9-beta5 to restore your package).
• Reset your site to fresh WordPress installation (clear the uploads, clear plugins, use default WP theme, etc.).
• Leave only Prime Mover plugin activated and have the package ready for restoration.
• Restart your server and MySQL to clear out and reset all running processes.
• Double check your hard drive and make sure it’s not full.
• Proceed to restore. Don’t run another processes – so all processes are diverted to the restoration. In our test – it takes around 3 hours to fully restore the site – because your site database is big.
• Done.

Additional tips:

• If it still does not work in your DDEV environment – try other local development environment like FLywheel by Local and other options.
• We noticed that you have many of your source site database tables that are still using MyISAM engine. You might wish to upgrade this InnoDB storage engine which have better reliability and performance in terms of migration. You need to make this change in your source site before you migrate it with Prime Mover. Take note this is a big change – so if you wish to do this, make sure your backup and fully test your site first.

I hope that all tips should be helpful – you should be able to finally restore your site.