Terminated Imports & Server Errors
This means that your server is stopping the import process before it can complete. WP All Import processes records piece by piece to help prevent this from happening.
Sometimes you can prevent your server from terminating the import simply by lowering the records per iteration. Other times the reason for the termination has nothing to do with the records per iteration.
No matter the cause, the troubleshooting process always starts the same:
Lower the records per iteration. You can control how many records are processed in each iteration in Import Settings ▸ Advanced Options ▸ Iterative, Piece-by-Piece Processing. If your import is still being terminated with 1 record per iteration, then you’ll need to modify your server settings so it will allow WP All Import to run.
Contact your host and have them check your server’s error log. They will be able to see exactly why your server is terminating the import and they will know exactly how to fix it. There isn’t anything we can do to help until your host has checked the error log and we know exactly what the issue is.
Servers have a number of settings that place hard limits on how long processes are allowed to run before they are terminated.
There are the two very common hard limits that our users run in to:
Maximum Execution Time (PHP): This is set in php.ini with max_execution_time. It determines how long a process is allowed to run before it’s terminated. You can ask your host to increase the limit, but this should be considered a last resort.
FCGID Timeouts (Apache): This is set in httpd.conf with FcgidIOTimeout.It determines how long mod_fcgid will wait while trying to perform a read or write. It should be set as high as your host will allow. In our experience 90 seconds is sufficient.
When servers are misconfigured or trying to do things that require more resources than are available, they will throw an error. The error message is usually just a 3-digit number. The number can give you some information about what the nature of the error. For example:
500 Internal Server Error: This often occurs when something in your WordPress theme or one of the plugins has some sort of issue.
503 Service Unavailable: This often occurs when the server is overloaded. It can also indicate that the security system on your server is blocking WP All Import.
504 Gateway Timeout: This is often related to the server being overloaded.
Our support team will not be able to help you troubleshoot these errors. You will need to contact your host to check your server's error log.
Check Your Server's Error Log
You'll need to contact your host's support team and ask them to look for error log entries around the time the error occurred. To help your host's support team be sure to include the following information in your support request:
- The exact time the error occurred, including the timezone. If you're not sure when it occurred, please take the steps necessary to reproduce the error.
- Your IP address. Visit http://www.whatismyip.com/ for help.
- A screenshot of the error, including the URL in your browser.
If your server is throwing errors it is your host's responsibility to make sure it is logged. If your host is unable to find any relevant entries in the error, have them make sure that error logging is enabled and that they are checking the relevant error log. There are usually at least three places errors are logged on your server:
- Web Server (Apache or NGINX)
- Database (MySQL or MariaDB)
We will not be able to help you find, read, or interpret your server's error log. Even if we were able to do so, you'd still need to contact your host to make the necessary changes to resolve the error. This is why you pay for hosting, and problems like these are where good hosts stand out from bad ones.
For a list of hosts that work great with WP All Import, see our recommended hosts page.