<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How-to Fix WP HTTP Error: name lookup timed out</title>
	<atom:link href="http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/</link>
	<description>The FatLab Music Blog</description>
	<lastBuildDate>Fri, 13 Apr 2012 14:50:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: agus</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-568</link>
		<dc:creator>agus</dc:creator>
		<pubDate>Sat, 11 Dec 2010 12:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-568</guid>
		<description>thank&#039;s for share it, i will try to my blog</description>
		<content:encoded><![CDATA[<p>thank&#8217;s for share it, i will try to my blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro Avila</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-535</link>
		<dc:creator>Pedro Avila</dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-535</guid>
		<description>Thanks man!

My problem was solved.</description>
		<content:encoded><![CDATA[<p>Thanks man!</p>
<p>My problem was solved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jez</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-532</link>
		<dc:creator>jez</dc:creator>
		<pubDate>Fri, 23 Oct 2009 09:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-532</guid>
		<description>Hi,

I pretty much have the same problem and after following your advise I am now getting &quot;An Unexpected HTTP Error occurred during the API request.&quot; - will let you know if I find a work around</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I pretty much have the same problem and after following your advise I am now getting &#8220;An Unexpected HTTP Error occurred during the API request.&#8221; &#8211; will let you know if I find a work around</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol Star</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-524</link>
		<dc:creator>Carol Star</dc:creator>
		<pubDate>Wed, 02 Sep 2009 06:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-524</guid>
		<description>Thanks a ton for this blog.I was also going with the same error but this information helps in getting away from that problem.</description>
		<content:encoded><![CDATA[<p>Thanks a ton for this blog.I was also going with the same error but this information helps in getting away from that problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brent</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-523</link>
		<dc:creator>brent</dc:creator>
		<pubDate>Tue, 25 Aug 2009 15:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-523</guid>
		<description>Hmm... a few thoughts:

Do you still get the timeout error with wp-includes/http.php lines 1276-1277 commented out?

If removing those lines allows the connections to happen, then you prolly just need to figure out what your actual timeout number should be.  It might just need to be higher than 15 seconds.  That being said, if your server is taking longer than 15 seconds per cURL request, there&#039;s prolly something nastier going on somewhere else and all this is doing is masking the symptoms.

But, to find out your adequate timeout number, you could try enabling Core Control&#039;s &quot;HTTP Access Logger Module&quot;.  It&#039;s in Tools &gt; Core Control (Main Page).  Once you enable the module, don&#039;t forget to also go into the External HTTP Access Logger &quot;tab&quot; and click the &quot;Enable HTTP Logging&quot; button.  Click thru a few pages in the WP dashboard that generate the timeout error, then check back and see what the logger has to report.  It might tell you something new.

A more hardcore way would be to catch your cron results in an error_log file.  Instead of the line 1325 debug code you see above, add this instead to wp-includes/http.php:
&lt;pre lang=&#039;php&#039; line=&#039;1325&#039;&gt;error_log(print_r(curl_getinfo($handle),TRUE));&lt;/pre&gt;

Naturally, wrapping &lt;code&gt;curl_getinfo()&lt;/code&gt; in &lt;code&gt;error_log()&lt;/code&gt; is nicer to your users than just dumping the output to screen.  FYI, my error_log file ended up in the wp-admin folder.

Look in the file for values of [total_time], [namelookup_time], and so on.  If they are longer than 15, then change the plugin code to a higher number.</description>
		<content:encoded><![CDATA[<p>Hmm&#8230; a few thoughts:</p>
<p>Do you still get the timeout error with wp-includes/http.php lines 1276-1277 commented out?</p>
<p>If removing those lines allows the connections to happen, then you prolly just need to figure out what your actual timeout number should be.  It might just need to be higher than 15 seconds.  That being said, if your server is taking longer than 15 seconds per cURL request, there&#8217;s prolly something nastier going on somewhere else and all this is doing is masking the symptoms.</p>
<p>But, to find out your adequate timeout number, you could try enabling Core Control&#8217;s &#8220;HTTP Access Logger Module&#8221;.  It&#8217;s in Tools > Core Control (Main Page).  Once you enable the module, don&#8217;t forget to also go into the External HTTP Access Logger &#8220;tab&#8221; and click the &#8220;Enable HTTP Logging&#8221; button.  Click thru a few pages in the WP dashboard that generate the timeout error, then check back and see what the logger has to report.  It might tell you something new.</p>
<p>A more hardcore way would be to catch your cron results in an error_log file.  Instead of the line 1325 debug code you see above, add this instead to wp-includes/http.php:</p>

<div class="wp_syntax"><table><tr><td class="line_numbers"><pre>1325
</pre></td><td class="code"><pre class="php" style="font-family:monospace;"><span style="color: #990000;">error_log</span><span style="color: #009900;">&#40;</span><span style="color: #990000;">print_r</span><span style="color: #009900;">&#40;</span><span style="color: #990000;">curl_getinfo</span><span style="color: #009900;">&#40;</span><span style="color: #000088;">$handle</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">,</span><span style="color: #009900; font-weight: bold;">TRUE</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span></pre></td></tr></table></div>

<p>Naturally, wrapping <code>curl_getinfo()</code> in <code>error_log()</code> is nicer to your users than just dumping the output to screen.  FYI, my error_log file ended up in the wp-admin folder.</p>
<p>Look in the file for values of [total_time], [namelookup_time], and so on.  If they are longer than 15, then change the plugin code to a higher number.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://fatlabmusic.com/blog/2009/08/12/how-to-fix-wp-http-error-name-lookup-timed-out/comment-page-1/#comment-522</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 25 Aug 2009 10:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://fatlabmusic.com/blog/?p=300#comment-522</guid>
		<description>Hello,

I tried this solution and it doesn&#039;t work.  The plugin activates OK, but Core Control still shows me an error: 
An Error has occured: name lookup timed out

I have 5 wordpress sites stalled with the wp-o-matics not updating the RSS because the cURL doesn&#039;t work anymore.

(The sites are hosted at 1Dollar-webhosting and the tech support does not even ANSWER email, except intermittently every week or so, and then they answer with a non sequitur.)

Any help solving this hosting-related problem would be SUPER appreciated !!!



</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I tried this solution and it doesn&#8217;t work.  The plugin activates OK, but Core Control still shows me an error:<br />
An Error has occured: name lookup timed out</p>
<p>I have 5 wordpress sites stalled with the wp-o-matics not updating the RSS because the cURL doesn&#8217;t work anymore.</p>
<p>(The sites are hosted at 1Dollar-webhosting and the tech support does not even ANSWER email, except intermittently every week or so, and then they answer with a non sequitur.)</p>
<p>Any help solving this hosting-related problem would be SUPER appreciated !!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: fatlabmusic.com @ 2012-05-23 00:31:29 by W3 Total Cache -->
