Is it perhaps a *server* dns lookup delay?
I've typically seen 60s delays when a reverse lookup fails, so 20s seems odd - but when you first mentioned it, that's the little flag that waved in my head.
'course I could be totally stupid, high, or huffing glue or something
- but thought I'd throw that out there.
-Greg
MP> On 11/14/2013 11:32 AM, Benny Pedersen wrote:
Marc Perkel skrev den 2013-11-14 05:25:
My AUTH depends only on MYSQL. There's no DNS involved. At least not that I can see there should be. So why would localhost take 10-15 seconds to do the login part and coming into the servers IP address is instant. And in both cases the connection itself is instant. It's when I type in the LOGIN command that the delay occurs.
i cant see what in sql.conf here, never mind, but localhost is a hostname so it needs dns to find the ip, change the hostname in sql.conf to 127.0.0.1 or use socket file instaed of dns
if that its, give me a hand ?
MP> That would be understandable if the delay were connecting, but it's not. MP> The connection is instand. And localhost resolves instantly. The delay MP> is after I type in the login command. That's what I don't understand.