hi guys - i figured this out, turned out someone or something had applied an overly strict iptables rule best, paul
On 1/25/08, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > You didn't say what your command line looked like - e.g., whether you > were selecting a db as part of it. > > Assuming you were, this sounds like a corrupted db problem. > > To pinpoint the problem a little, try a: > > mysqlshow <-u ... -p ... as necessary> > > at the command line (with no database specified). > > I suspect that that will hang as it's trying to run through them all. > If it does, then specify a database, one at a time, running through > the your list of databases. The one(s) that hang are likely corrupted. > > If that "works", i.e., turns up one db that the show hangs on, but > others seem ok, then you can focus recovery/restore options on that > database. > > > - Rick > > > ------------ Original Message ------------ > > Date: Friday, January 25, 2008 08:07:32 AM -0500 > > From: Paul Berry <[EMAIL PROTECTED]> > > To: mysql@lists.mysql.com > > Subject: mysql - debug connections dropping/not accepted > > > > hey guys - overnight our sql server apparantly got hit hard, and > > started dropping connections > > it was restarted and now this morning even though its showing 0 > > processes running, seems > > completely healthy on all tests, mysqld restarted with no sign of > > problems - none of the > > web servers can connect to it. you can also not connect if you log > > into one of those > > servers and try the same connect, it quickly asks for the password > > prompt and then seems to hang forever with out any responses > > > > any clues for this? what type of commands should i run to diagnose? > > i've never seen this one before > > thanks > > paul > > ---------- End Original Message ---------- > >
