● mysqld.service - MySQL Server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2025-07-15 11:18:35 CST; 1min 30s ago Docs: man:mysqld(8) http://dev.mysql.com/doc/refman/en/using-systemd.html Process: 26003 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=127) Main PID: 4124 (code=exited, status=1/FAILURE)
Jul 15 11:18:35 VM-4-15-centos systemd[1]: Starting MySQL Server... Jul 15 11:18:35 VM-4-15-centos systemd[1]: mysqld.service: control process exited, code=exited status=127 Jul 15 11:18:35 VM-4-15-centos systemd[1]: Failed to start MySQL Server. Jul 15 11:18:35 VM-4-15-centos systemd[1]: Unit mysqld.service entered failed state. Jul 15 11:18:35 VM-4-15-centos systemd[1]: mysqld.service failed.
Initial system error:
1 2 3 4 5 6 7 8 9 10 11
2025-06-13T09:50:55.998093Z 3340 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead' 2025-06-13T11:27:55.122940Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36) starting as process 4124 2025-06-13T11:27:55.188306Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2025-06-13T11:27:55.232892Z 0 [Warning] [MY-012681] [InnoDB] page_aligned_alloc mmap(137236480 bytes) failed; errno 12 2025-06-13T11:27:55.233033Z 1 [ERROR] [MY-012956] [InnoDB] Cannot allocate memory for the buffer pool 2025-06-13T11:27:55.233069Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2025-06-13T11:27:55.233110Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2025-06-13T11:27:55.233255Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2025-06-13T11:27:55.233274Z 0 [ERROR] [MY-010119] [Server] Aborting 2025-06-13T11:27:55.234540Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36) MySQL Community Server - GPL
Thought it was caused by insufficient memory pool, but checking the cloud service backend showed more than 50% memory space unused. Still, following the article’s advice, I modified the my.conf parameter to 64M and increased SWAP memory size.
1 2 3
innodb_buffer_pool_size = 32M
However, the error persisted:
1 2 3 4 5
Jul 15 10:15:08 VM-4-15-centos systemd[1]: Unit mysqld.service entered failed state. Jul 15 10:15:08 VM-4-15-centos systemd[1]: mysqld.service failed. Jul 15 10:15:08 VM-4-15-centos polkitd[691]: Unregistered Authentication Agent for unix-process:12036:302109437 (system bus name :1.80437, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus) Jul 15 10:15:08 VM-4-15-centos sudo[12034]: pam_unix(sudo:session): session closed for user root Jul 15 10:15:08 VM-4-15-centos systemd-logind[705]: Removed session 40031.
At this moment, I suddenly remembered that when VSC couldn’t log in via ssh earlier, I upgraded glib to version 2.28, and yum had some issues, so:
1
sudo yum update -y
Error:
1 2 3 4 5 6 7 8
sudo yum update -y error: rpmdb: BDB0113 Thread/process 2314/139854510331136 failed: BDB1507 Thread died in Berkeley DB library error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main:
After updating everything, the mysql service started normally. The reason should be that my rpm database corruption caused the process failure, leading to website inaccessibility, unrelated to memory or permissions.
