AIQUM MySQL Service Crashes Frequently
Applies to
- ActiveIQ Unified Manager (AIQUM) 9.6+
- MySQL
Issue
- AIQUM GUI is inaccessible/unresponsive
- A reboot temporarily resolves the issue
- MySQL service is found in a not running state
- MySQL
error.log:
[ERROR] [MY-010934] [Server] Out of memory (Needed 27240544 bytes)
[ERROR] [MY-010934] [Server] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
..
..
[ERROR] [MY-013190] [InnoDB] [FATAL] Some (1659055039) threads are still active Unable to allocate memory of size 16488.
[ERROR] [MY-013183] [InnoDB] Assertion failure: memory.cc:305:ib::fatal triggered thread 8312 - Frequent crashes may eventually lead to InnoDB corruption:
[ERROR] [MY-013190] [InnoDB] [FATAL] Some (1659055039) threads are still activeUnable to allocate memory of size 16488.
[ERROR] [MY-013183] [InnoDB] Assertion failure: memory.cc:305:ib::fatal triggered thread 8312
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/...-recovery.html
InnoDB: about forcing recovery.
mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x26d9e459070
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...