1.12.35 update getting error 500

Hi,

At what point do you get the 500 error? e.g backup, restore etc

Best Wishes,

Ashley

Also – what’s logged in your server PHP and Apache error logs at the time of the error?

David

sorry, i wrote “update” in the title and should have put that in the body too. the error is when upgrading.

Here ya go David…

2017-03-07 00:29:55 Error 208.69.242.80 500 POST /wp-admin/admin-ajax.php HTTP/1.0 https://kootenaydentalarts.com/wp-admin/plugins.php Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 1.57 K Apache access

2017-03-07 00:30:35 Warning 208.69.242.80 mod_fcgid: read data timeout in 40 seconds, referer: https://kootenaydentalarts.com/wp-admin/plugins.php Apache error

2017-03-07 00:30:36 Error 208.69.242.80 End of script output before headers: admin-ajax.php, referer: https://kootenaydentalarts.com/wp-admin/plugins.php Apache error

2017-03-07 00:30:51 Error 208.69.242.80 503 POST /wp-admin/admin-ajax.php HTTP/1.0 https://kootenaydentalarts.com/wp-admin/plugins.php Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 593 Apache access

After that i was getting 503 errors because the upgrade never exited from maintenance mode.

Hi,

It appears that the update is being timed out by the FastCGI ‘mod_fcgid’ module on the server.

Please could you ask your hosts/server admin if they can increase the time limit of the mod_fcgid ‘FcgidIOTimeout’ directive?

After looking at this more closely, we noticed that of the 3 websites that we have on this vps, only this one had a problem updating. The other 2 updated successfully to the same version of the plugin that failed to update on the site mentioned above. From our end it does not look like a server setting is influencing this.

The error message indicates that WordPress is taking longer than your configured fcgid timeout to do the update.

When WP updates a plugin, the plugin itself isn’t involved; WP is just doing this (and you can update by manually doing these steps yourself – it makes no difference): 1) Downloads the zip from www.ads-software.com 2) Unzips it 3) Moves it into wp-content/plugins, replacing the previous directory.

Hi David,

We are looking further into this.

While i agree with you that the actual update process does not run the plugin, if you update it manually on the plugins page i do believe it gets loaded after the update and any error would then show. Also, of course, it’s usually loaded when a page loads (after updating) and can throw an error then.

I’ve certainly seen my share of plugins that fail immediately after i update them from the plugins page, before i’ve left the plugins page. If a plugin is not loaded right after upgrade, what good would the upgrader_process_complete hook be?

In this case i arrived on the plugins page to discover a red error message at the top of the page, indicating that an error 500 had taken place earlier.

I then re-uploaded the previous version of UpdraftPlus by FTP and tried the update manually (the first time was an automatic update). I then got another error 500 that displayed inline with the plugin on the plugins page. In that case WordPress was left in maintenance mode and the site was down.

While it’s not clear to me whether this is a plugin or server problem, i think it’s a bit misleading to suggest/imply that this error could not be caused by UpdraftPlus.

Does your plugin try to communicate with the outside world right after an update? or rely at that time on any service that could possibly not respond quickly enough?

What I do not understand is that I have full access to php and server settings and they have long time outs and max avail resources to WordPress – furthermore I have never had an issue with previous Updraft updates – until now.