* If SHOW ENGINE INNODB STATUS returned an error that was not privilege-related, MONyog reported MySQL as non-available. That could happen for instance if MySQL was started with –skip-innodb option. This bug was introduced in 3.71 with the support for InnoDB deadlock detection.
* A bug in the MONyog startup script could on Linux have the result that MONyog was still reported as running if it had been killed or had crashed.
