Take the 2-minute tour ×  Recently one of our servers has ran
out of memory and crashed. After reviewing the munin graphs, it
appears that the only metric (other than memory usage) that
peaked just before the crash was the MySQL throughput. However
we were expecting to see a corresponding increase in number of
MySQL queries which didn't happen:  enter image description here
enter image description here  Also from below graph, you can see
that the MySQL throughput has reached an abnormally high value,
nowhere near any other value reached before:  enter image
description here  We're completely in the dark as to how we
should proceed, hence the below question:  How to perform a
"postmortem" investigation of a MySQL throughput increase?
share|improve this question You simply can't if you have no
(other) data! –  pfo Apr 19 '12 at 10:21 That we figured out :)
We have the bin logs in /var/log/mysql/, the error logs in
/var/log/mysqld.log, we just have know idea as to how going
about them, except based on timestam