Error! MariaDB is not running on your system - database list could not be retrieved.
MariaDB error message: The full MariaDB error message was : DBI connect failed : Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111)
MySQL Error log:
220527 17:54:24 [Warning] IP address '205.210.31.129' could not be resolved: Name or service not known
220527 18:53:45 mysqld_safe Number of processes running now: 0
220527 18:53:45 mysqld_safe mysqld restarted
220527 18:53:45 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 20724 ...
220527 18:53:45 InnoDB: The InnoDB memory heap is disabled
220527 18:53:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
220527 18:53:45 InnoDB: Compressed tables use zlib 1.2.7
220527 18:53:45 InnoDB: Using Linux native AIO
220527 18:53:45 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137756672 bytes) failed; errno 12
220527 18:53:45 InnoDB: Completed initialization of buffer pool
220527 18:53:45 InnoDB: Fatal error: cannot allocate memory for the buffer pool
220527 18:53:45 [ERROR] Plugin 'InnoDB' init function returned error.
220527 18:53:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
220527 18:53:45 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
220527 18:53:46 [Note] Plugin 'FEEDBACK' is disabled.
220527 18:53:46 [ERROR] Unknown/unsupported storage engine: InnoDB
220527 18:53:46 [ERROR] Aborting
220527 18:53:46 [Note] /usr/libexec/mysqld: Shutdown complete
220527 18:53:46 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
220528 22:24:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
220528 22:24:21 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 16394 ...
220528 22:24:21 InnoDB: The InnoDB memory heap is disabled
220528 22:24:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
220528 22:24:21 InnoDB: Compressed tables use zlib 1.2.7
220528 22:24:21 InnoDB: Using Linux native AIO
220528 22:24:21 InnoDB: Initializing buffer pool, size = 128.0M
220528 22:24:21 InnoDB: Completed initialization of buffer pool
220528 22:24:21 InnoDB: highest supported file format is Barracuda.
220528 22:24:21 InnoDB: Starting crash recovery from checkpoint LSN=372208719
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
220528 22:24:21 InnoDB: Starting final batch to recover 1 pages from redo log
220528 22:24:22 InnoDB: Waiting for the background threads to start
220528 22:24:23 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 372212044
220528 22:24:23 [Note] Plugin 'FEEDBACK' is disabled.
220528 22:24:23 [Note] Server socket created on IP: '0.0.0.0'.
220528 22:24:23 [Note] Event Scheduler: Loaded 0 events
220528 22:24:23 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.68-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
220528 22:24:28 [ERROR] mysqld: Table './ibilling/sys_invoiceitems' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './ibilling/sys_invoiceitems'
220528 22:24:28 [ERROR] mysqld: Table './ibilling/sys_invoices' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './ibilling/sys_invoices'
220528 22:24:28 [ERROR] mysqld: Table './ibilling/sys_logs' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './ibilling/sys_logs'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_client_custom' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_client_custom'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_clients' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_clients'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_invoice_amounts' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_invoice_amounts'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_invoice_groups' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_invoice_groups'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_invoice_item_amounts' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_invoice_item_amounts'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_invoice_items' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_invoice_items'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_invoices' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_invoices'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_payments' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_payments'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_quote_amounts' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_quote_amounts'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_quote_item_amounts' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_quote_item_amounts'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_quote_items' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_quote_items'
220528 22:24:28 [ERROR] mysqld: Table './nkp_pisha/osssb_quotes' is marked as crashed and should be repaired
220528 22:24:28 [Warning] Checking table: './nkp_pisha/osssb_quotes'
============================================
/etc/my.cnf
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
symbolic-links=0
innodb_file_per_table = 1
[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid
!includedir /etc/my.cnf.d
I think the error is not related to configuration. I think your system is actually running out of RAM. I don’t know why that would be, as 8GB is plenty for most small scale web hosting needs. But…well, the error indicates it tried to allocate the 128MB and failed. I do not think increasing it (by a huge amount) will help here. I think it will make it more likely to fail to allocate that much memory.
I set for some Apllications this on 256MB , if testing i think is always better to do that in smaller steps and see if problems are less or later. While if a Programm BUG and you set the value much to high, you still get a suprise but later. ( is my opinion about this value) ( if starting in some programms migrations then i needed more in the past then the 256MB, but migrations you do once and a while so then only)
Nothing important will be erased. If only modifies configuration values, it won’t erase any data or mess with your sites.
But, I’m not confident that’s going to do anything useful here. I’d like to see evidence the database is where all your memory is going. Could be something else entirely. Check top or htop for clues.
Look, I’m telling you you need to figure out what’s consuming all your memory. To repeat: “I’d like to see evidence the database is where all your memory is going. Could be something else entirely. Check top or htop for clues.”
Increasing the pool size performed in chunks. I would suggest lowering the standard chunk size, alongside with raising pool instances. Most certainly, you must decrease pool size to 512M or even more down to 256M.
Why did you edit those default values in the first place? What made you do this? Did anything was failing to work?
That would have helped (changed anything) only if you didn’t add many more of other options manually. We configure specific options upon wizard, but innodb_buffer_pool_size is not one of them, thus re-running the wizard wouldn’t change anything.