Michael, you hit the nail on the head. We added
--skip-name-resolve and changed our connnection string
to use the IP instead of FQDN and now things are
working fine. It must have been something with our
DNS/ISP since we changed nothing and that stuff is out
of our control.
The other thing was captured from our PHP logs. Not
sure what that's on about. We'll just have to monitor
it and see if pattern develops.
Thanks for your help.
--- Michael Stassen <Michael.Stassen@stripped>
> Tripp Bishop wrote:
> > Hello all,
> > Suddenly in the last hour or so the connection
> > between our webserver and database server has
> > skyrocketed to the point that our site is no
> > usable! Just trying to connection via the mysql
> > takes a long time. Once the connection is
> > however, queries seem to execute in a timely
> > As far as we can tell the network connection
> > the two boxes is fine (at least testing by ping
> > and again, once connected everything seems fine.
> It's hard to be sure without knowing more, but if
> the network is working, and
> mysql works fine once connected, it sounds like it
> might be a DNS problem.
> Often the solution is to list hosts by IP rather
> than hostname in the mysql user
> table, and run mysqld with --skip-name-resolve. See
> about a third of
> the way down, for some hints about DNS problems.
> > We've seen some errors in our logs that state:
> > connect to local MySQL server through socket
> > '/var/lib/mysql/mysql.sock'. Why would php
> > mysql_connect be trying to connect to the local
> > Server? Our connection string should point it to
> > db server.
> Which logs? Are you sure this is the same problem?
> What is the connection
> string? Do you capture error messages from mysql in
> your php script?
> > We're using php 4.3.9 and MySQL 4.0.20.
> > Thanks for any help,
> > Tripp
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
Yahoo! Mail - PC Magazine Editors' Choice 2005