I thought of that, but I don't see where it could be getting into the mix. I'm running cURL directly on the application server and I'm connecting to the application via 127.0.0.1 — no DNS there. The database.yml is pointing to the database on 127.0.0.1 — no DNS there either. I'm not using memcached or anything else fancy that might need a DNS lookup.
I've checked all of the files in config/ and I don't see any host name entries. Is there anywhere else I should look for host name configuration? Is there any way I can trace exactly what's happening after the "Completed 200 OK in 12ms" log entry, to see what's hanging? ~Joe On Feb 2, 8:30 am, Walter Lee Davis <[email protected]> wrote: > > This kind of consistent delay sounds a lot like a DNS issue to me. > Some machine in the transaction (maybe the server, maybe the machine > that cURL is running on) is trying to look up its own name and > failing, and having to wait through the DNS timeout. That's the > direction I would start looking personally. > > Walter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
