If your mysql server is hung, crashed or otherwise unreacheable (as you
first posted), you can't connect to it and request it's status and
processlist - it's threaded and thus all inline.
You could use GDB or something similar to go look in the execution stack, as
Raj said, and if you have full query logging enabled, you can parse your
logs and see what was happening at the time of the crash - although I
suspect that only completed queries get logged, so the one causing the crash
may not be in there.
Generally, it's a good idea to use Munin, Cacti or similar tools to graph
performance data all the time, so you can have a post-mortem look at stuff
like "did the number of connections increase in the moments before ?"
On Tue, May 18, 2010 at 9:28 AM, James Corteciano <james@stripped>wrote:
> I found some tools to capture the MySQL processlist, log errors, etc.
> MySQLReport <http://hackmysql.com/mysqlreport> and
> mytop<http://jeremy.zawodny.com/mysql/mytop/>apps. My goal is to grab
> the logs of mysql including the processlist to help
> me assist in diagnosis of faults.
> What tool/apps do you use?
> On Tue, May 18, 2010 at 5:06 AM, Raj Shekhar <rajlist@stripped>
> > In infinite wisdom James Corteciano <james@stripped> wrote:
> > > [1 <text/plain; ISO-8859-1 (7bit)>]
> > > Hi All,
> > >
> > > What is the other way to get the *processlist* and *status* of mysql
> > server
> > > on event that the mysql server cannot be able to reach due to hung or
> > > crashed?
> > GDB <http://poormansprofiler.org/>
> > --
> > Raj Shekhar
> > -
> > If there's anything more important than my ego around, I want it
> > caught and shot now.
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe:
> > http://lists.mysql.com/mysql?unsub=1
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel