<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
Hi List,
<br />
<br />Here is a small update/solution to my Wordpress auto-update problems.
<br />
<br />Until I found the solution I just added extra code (Curl options) to the class-http.php wordpress file. This worked fine but took a long time on all the websites and after a wordpress core update I would have to do it all again...
<br />
<br />After seaching some more forums I finaly found the solution. It was the timeout directive of apache! I checked my settings with the settings that Apache recomments (https://httpd.apache.org/docs/2.0/mod/core.html#TimeOut). They talk about a standard timeout setting of 300.
<br />On my 5108R installs (checked with 3 of my 5108R servers) it was 2x 60 sec and 1x 120 sec. I've bumped it up to 300 sec and now my auto-updates inside wordpress are working like a charm!
<br />
<br />So now come a few new questions? I don't remember changing the timeout directive of Apache myself on these servers, what could make 3 servers have different timeouts? Also would a future update of apache change the timeout again? I suppose making httpd.conf immutable is not the right option here. What is de default timeout used in BO? Am I overlooking a possible problem when bumping the value up to 300 sec?
<br />
<br />With kind regards,
<br />
<br />Wisja
<br />
<br />
<br /><font size="2"><b>On Fri, 28 Jun 2013 15:11:24 +0200, Wisja.net Computers wrote</b>
<br />> Hi
list,
<br />>
<br />>
We have 2 servers (identical) with many WordPress installations. The updates
there
<br />>
always worked correctly. Suddenly, a few months back all updates of major (!)
plugins
<br />>
(like Jetpack, WPML) including the WordPress core upgrade itself fail at:
<br />>
<br />>
Downloading update from http://...
<br />>
<br />>
Now this does not seem to be a regular update issue:
<br />>
* The PHP memory limit is high enough (256MB). Also the memory has been
sufficient until
<br />>
now.
<br />>
* The access writes are OK. We can check them via SSH. And many other minor
plugins can
<br />>
be updated without problems.
<br />>
* The update file is downloaded alright each time. We can see it in the system
tmp
<br />>
folder. It is there in full size, but with "tmp" exception. Also (as I
will explain
<br />>
later) the process has not got to the point of unpacking it yet, so it is not an
unzip
<br />>
problem (and, remember, the minor plugins are updated correctly, so unzip works
for them).
<br />>
* This happens in all our WordPress installations in this server regardless of
their
<br />>
version. Ranging from 2.9 to 3.5. - We do not believe that our IP is somewhere
<br />>
blacklisted. We can wget the files from the console and (as mentioned above) we
see the
<br />>
temporary files being downloaded. Also (again) minor plugins are updated
correctly.
<br />>
<br />>
So the problem gets a little crazy. So we start hacking into the core code of
WordPress.
<br />>
We put debugging messages through every single step of the update process and we
get
<br />>
down to this:
<br />>
<br />>
The process gets to a point where (in file /wp-includes/class-http.php, around
line
<br />>
1140) it executes a PHP curl command to download the update. It does a
curl_init, then
<br />>
many curl_setopt calls and, finally a curl_exec.
<br />>
<br />>
Well this curl_exec never returns.
<br />>
<br />>
Then we try to debug the curl download so, after several tries, we add a
progress
<br />>
callback to it like this:
<br />>
<br />>
---
<br />>
<br />>
curl_setopt($handle, CURLOPT_NOPROGRESS, false);
<br />>
<br />>
---
<br />>
<br />>
And then, after this addition, the curl_exec finishes fine and the upgrade goes
on
<br />>
successfully!
<br />>
<br />>
PHP version 5.3.3 (stock), cURL version 7.19.7 (stock)
<br />>
<br />>
Any ideas? Is it possible to upgrade cURL, last update is 7.31?
<br />>
<br />>
Wisja
<br />>
_______________________________________________
<br />>
Blueonyx mailing list
<br />>
Blueonyx@mail.blueonyx.it
<br />>
<a target="_blank" href="http://mail.blueonyx.it/mailman/listinfo/blueonyx">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a>
<br />
<br />
<br />
</font>
</BODY>
</HTML>