On Sun, 11 May 2008 15:07:02 -0400, Barry Margolin wrote
(in article <barmar-DA793E.15070111052008@[EMAIL PROTECTED]
>):
> In article <g05tkv02e36@[EMAIL PROTECTED]
>,
> John Drako <jbravo556@[EMAIL PROTECTED]
> wrote:
>
>> Suddenly, today, out of nowhere something changed on my system and I
>> can't explain it.
>>
>> I happen to use cURL extensively directly and in some applescripts that
>> I created.
>>
>> The change is that now, for some reason, each transaction with curl is
>> slow to initiate. It doesn't start before 30 seconds elapse. It's
>> slowing my work considerably. Some of the applescripts that I used
>> initiate several curl sessions in a row to send files to multiple
>> servers. So add 30 seconds exactly to each connection and I'm wasting a
>> lot of time waiting around.
>>
>> I tracked a possible cause of the problem to a dead DNS server that I
>> had in my network preferences and in the Air****t's config.
>>
>> I removed the DNS server from both and I rebooted the computer (intel
>> iMac with 10.5.2); I restarted the Air****t Extreme that I have (latest
>> model), I even unplugged it for more than 20 minutes and shutdown my
>> computer. I cleared the DNS cache on the computer more than once. All
to
>> no avail.
>>
>> The other thing affected is the speed of sftp connections in
Interarchy.
>> Those are slow to initiate too, but once the first connection works,
>> subsequent sftp transfers start fast.
>>
>> Browsing, email, nntp are all working as usual. The only thing affected
>> are sftp and cURL.
>>
>> Any suggestions? is there some cache that I couldn't find?
>
> To see if it's still a DNS problem, open a Terminal and type:
>
> host -t a <servername>
>
> where <servername> is one of the FTP servers you're having trouble with.
>
> A while ago I was also seeing slowness like this due to problems with
> reverse DNS. If the above lookup isn't slow, take the IP address
> returned by the above command, and do:
>
> host <address>
Tried that, it works at normal speed.
Now it's got even weirder.
The same setup that I have (iMac 10.5.2 connecting though an air****t
extreme of the same type), 500 miles away (completely different ISPs)
started suffering from the exact same symptom as the setup that I have.
curl waiting 30 seconds to respond as if something is timing out before
it could do its job.
I would have thought it was something on my server causing it, but when
doing a "curl -I <URL>" and ANY url, not just my server, any URL, times
out for 30 seconds before it responds.
I tried the following:
curl -I "http://www.apple.com"
curl -I "http://www.google.com"
curl -I "http://www.yahoo.com"
curl -I "http://www.microsoft.com"
curl -I "http://www.mymacinations.com"
Each of the above took the exact same time -30.5 seconds- to get
results. Of course, at first I thought it was something on my system
causing, but what could possibly explains the exact same symptom on the
same setup 500 miles away? I must be something in the setup.
But I didn't change anything knowingly in my setup and my colleague says
that he didn't change anything. We've both been working with this exact
same setup with no new software installed or reconfigured since 10.5.2
came out.
Please, anybody willing to help that has 10.5.2 and an air****t extreme
with firmware version 7.3.1 (configured to connect using PPoE), please
try one or more of the above curl commands and let me know how long to
get results.
|
