Comments - Mariab not hanging when trying start
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
The errors before "128M" above are because an existing instance of mariadb is still running.
After the "128M" is showing "Cannot allocate memory" which is because memory isn't available. This is likely because an existing mariadb instance is still running.
The reason why its stopping are going to be earlier in the log file, before where the mariadb instance is restarted.
Given two instance cannot allocate 2x128M of innodb buffer pool it might be you are running out of ram on the failure. Look at `dmesg` output on your ec2 instance.
MariaDB-10.2.10 is coming up to 3 years old and between then and the currently 10.2.32 version there are a significant number of bug fixes, one of which might be causing your crash.
Thanks, Daniel. It was indeed out of memory because of multiple instances running. Now it is up and running.