[Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Good evening from Singapore,
Here is my solution:
# systemctl start mariadb.service
# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> quit Bye
# systemctl enable mariadb.service
===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===
Am 19.10.18 um 13:17 schrieb Turritopsis Dohrnii Teo En Ming:
Good evening from Singapore,
Here is my solution:
# systemctl start mariadb.service
# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> quit Bye
# systemctl enable mariadb.service
what has this to do with a crash? you simply forgot to enable the service and rebootet
Good afternoon from Singapore,
My MariaDB SQL Database Server really crashed. I did not reboot my virtual server at all. It has crashed twice already.
Here is the output of /var/log/mariadb/mariadb.log.
[root@ip-10-0-0-76 mariadb]# tail -n 50 mariadb.log 181018 5:43:33 [Note] Server socket created on IP: '0.0.0.0'. 181018 5:43:33 [Note] Event Scheduler: Loaded 0 events 181018 5:43:33 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 181018 7:22:34 [Warning] IP address '31.184.193.100' could not be resolved: Name or service not known 181018 7:55:41 [Warning] IP address '58.218.213.3' could not be resolved: Name or service not known 181018 12:58:57 [Warning] IP address '113.4.133.5' could not be resolved: Name or service not known 181018 19:59:04 [Warning] IP address '196.52.43.89' could not be resolved: Name or service not known 181019 09:04:06 mysqld_safe Number of processes running now: 0 181019 09:04:06 mysqld_safe mysqld restarted 181019 9:04:06 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 15275 ... 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 128917504 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 96681984 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 72499200 bytes) 181019 9:04:06 InnoDB: The InnoDB memory heap is disabled 181019 9:04:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181019 9:04:06 InnoDB: Compressed tables use zlib 1.2.7 181019 9:04:06 InnoDB: Using Linux native AIO 181019 9:04:06 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137756672 bytes) failed; errno 12 181019 9:04:06 InnoDB: Completed initialization of buffer pool 181019 9:04:06 InnoDB: Fatal error: cannot allocate memory for the buffer pool 181019 9:04:06 [ERROR] Plugin 'InnoDB' init function returned error. 181019 9:04:06 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 181019 9:04:06 [Note] Plugin 'FEEDBACK' is disabled. 181019 9:04:06 [ERROR] Unknown/unsupported storage engine: InnoDB 181019 9:04:06 [ERROR] Aborting
181019 9:04:06 [Note] /usr/libexec/mysqld: Shutdown complete
181019 09:04:07 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended 181022 02:54:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 181022 2:54:37 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 22837 ... 181022 2:54:37 InnoDB: The InnoDB memory heap is disabled 181022 2:54:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181022 2:54:37 InnoDB: Compressed tables use zlib 1.2.7 181022 2:54:37 InnoDB: Using Linux native AIO 181022 2:54:37 InnoDB: Initializing buffer pool, size = 128.0M 181022 2:54:37 InnoDB: Completed initialization of buffer pool 181022 2:54:37 InnoDB: highest supported file format is Barracuda. 181022 2:54:37 InnoDB: Starting crash recovery from checkpoint LSN=94454915 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 181022 2:54:37 InnoDB: Starting final batch to recover 4 pages from redo log 181022 2:54:37 InnoDB: Waiting for the background threads to start 181022 2:54:38 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 94455139 181022 2:54:38 [Note] Plugin 'FEEDBACK' is disabled. 181022 2:54:38 [Note] Server socket created on IP: '0.0.0.0'. 181022 2:54:39 [Note] Event Scheduler: Loaded 0 events 181022 2:54:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===
From: Maria-discuss maria-discuss-bounces+turritopsis.dohrnii=teo-en-ming.com@lists.launchpad.net on behalf of Reindl Harald h.reindl@thelounge.net Sent: Friday, October 19, 2018 8:00 PM To: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Am 19.10.18 um 13:17 schrieb Turritopsis Dohrnii Teo En Ming:
Good evening from Singapore,
Here is my solution:
# systemctl start mariadb.service
# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> quit Bye
# systemctl enable mariadb.service
what has this to do with a crash? you simply forgot to enable the service and rebootet
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
It's failing to allocate memory the innodb buffer pool. Check your memory usage / total ram / add more ram
-----Original Message----- From: Maria-discuss [mailto:maria-discuss-bounces+rhys.campbell=swisscom.com@lists.launchpad.net] On Behalf Of Turritopsis Dohrnii Teo En Ming Sent: 22 October 2018 11:49 To: Reindl Harald h.reindl@thelounge.net; maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Good afternoon from Singapore,
My MariaDB SQL Database Server really crashed. I did not reboot my virtual server at all. It has crashed twice already.
Here is the output of /var/log/mariadb/mariadb.log.
[root@ip-10-0-0-76 mariadb]# tail -n 50 mariadb.log 181018 5:43:33 [Note] Server socket created on IP: '0.0.0.0'. 181018 5:43:33 [Note] Event Scheduler: Loaded 0 events 181018 5:43:33 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 181018 7:22:34 [Warning] IP address '31.184.193.100' could not be resolved: Name or service not known 181018 7:55:41 [Warning] IP address '58.218.213.3' could not be resolved: Name or service not known 181018 12:58:57 [Warning] IP address '113.4.133.5' could not be resolved: Name or service not known 181018 19:59:04 [Warning] IP address '196.52.43.89' could not be resolved: Name or service not known 181019 09:04:06 mysqld_safe Number of processes running now: 0 181019 09:04:06 mysqld_safe mysqld restarted 181019 9:04:06 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 15275 ... 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 128917504 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 96681984 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 72499200 bytes) 181019 9:04:06 InnoDB: The InnoDB memory heap is disabled 181019 9:04:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181019 9:04:06 InnoDB: Compressed tables use zlib 1.2.7 181019 9:04:06 InnoDB: Using Linux native AIO 181019 9:04:06 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137756672 bytes) failed; errno 12 181019 9:04:06 InnoDB: Completed initialization of buffer pool 181019 9:04:06 InnoDB: Fatal error: cannot allocate memory for the buffer pool 181019 9:04:06 [ERROR] Plugin 'InnoDB' init function returned error. 181019 9:04:06 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 181019 9:04:06 [Note] Plugin 'FEEDBACK' is disabled. 181019 9:04:06 [ERROR] Unknown/unsupported storage engine: InnoDB 181019 9:04:06 [ERROR] Aborting
181019 9:04:06 [Note] /usr/libexec/mysqld: Shutdown complete
181019 09:04:07 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended 181022 02:54:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 181022 2:54:37 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 22837 ... 181022 2:54:37 InnoDB: The InnoDB memory heap is disabled 181022 2:54:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181022 2:54:37 InnoDB: Compressed tables use zlib 1.2.7 181022 2:54:37 InnoDB: Using Linux native AIO 181022 2:54:37 InnoDB: Initializing buffer pool, size = 128.0M 181022 2:54:37 InnoDB: Completed initialization of buffer pool 181022 2:54:37 InnoDB: highest supported file format is Barracuda. 181022 2:54:37 InnoDB: Starting crash recovery from checkpoint LSN=94454915 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 181022 2:54:37 InnoDB: Starting final batch to recover 4 pages from redo log 181022 2:54:37 InnoDB: Waiting for the background threads to start 181022 2:54:38 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 94455139 181022 2:54:38 [Note] Plugin 'FEEDBACK' is disabled. 181022 2:54:38 [Note] Server socket created on IP: '0.0.0.0'. 181022 2:54:39 [Note] Event Scheduler: Loaded 0 events 181022 2:54:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===
From: Maria-discuss maria-discuss-bounces+turritopsis.dohrnii=teo-en-ming.com@lists.launchpad.net on behalf of Reindl Harald h.reindl@thelounge.net Sent: Friday, October 19, 2018 8:00 PM To: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Am 19.10.18 um 13:17 schrieb Turritopsis Dohrnii Teo En Ming:
Good evening from Singapore,
Here is my solution:
# systemctl start mariadb.service
# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> quit Bye
# systemctl enable mariadb.service
what has this to do with a crash? you simply forgot to enable the service and rebootet
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Good evening from Singapore,
My virtual server is an Amazon AWS Linux instance. I only gave it 1 GB of RAM.
How much RAM/memory do I need to support MariaDB SQL database server without crashing?
Giving my virtual server more than 1 GB of RAM will cost me more money.
________________________________ From: Rhys.Campbell@swisscom.com Rhys.Campbell@swisscom.com Sent: Monday, October 22, 2018 6:22 PM To: Turritopsis Dohrnii Teo En Ming; maria-discuss@lists.launchpad.net Subject: RE: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
It's failing to allocate memory the innodb buffer pool. Check your memory usage / total ram / add more ram
-----Original Message----- From: Maria-discuss [mailto:maria-discuss-bounces+rhys.campbell=swisscom.com@lists.launchpad.net] On Behalf Of Turritopsis Dohrnii Teo En Ming Sent: 22 October 2018 11:49 To: Reindl Harald h.reindl@thelounge.net; maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Good afternoon from Singapore,
My MariaDB SQL Database Server really crashed. I did not reboot my virtual server at all. It has crashed twice already.
Here is the output of /var/log/mariadb/mariadb.log.
[root@ip-10-0-0-76 mariadb]# tail -n 50 mariadb.log 181018 5:43:33 [Note] Server socket created on IP: '0.0.0.0'. 181018 5:43:33 [Note] Event Scheduler: Loaded 0 events 181018 5:43:33 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 181018 7:22:34 [Warning] IP address '31.184.193.100' could not be resolved: Name or service not known 181018 7:55:41 [Warning] IP address '58.218.213.3' could not be resolved: Name or service not known 181018 12:58:57 [Warning] IP address '113.4.133.5' could not be resolved: Name or service not known 181018 19:59:04 [Warning] IP address '196.52.43.89' could not be resolved: Name or service not known 181019 09:04:06 mysqld_safe Number of processes running now: 0 181019 09:04:06 mysqld_safe mysqld restarted 181019 9:04:06 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 15275 ... 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 128917504 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 96681984 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 72499200 bytes) 181019 9:04:06 InnoDB: The InnoDB memory heap is disabled 181019 9:04:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181019 9:04:06 InnoDB: Compressed tables use zlib 1.2.7 181019 9:04:06 InnoDB: Using Linux native AIO 181019 9:04:06 InnoDB: Initializing buffer pool, size = 128.0M InnoDB: mmap(137756672 bytes) failed; errno 12 181019 9:04:06 InnoDB: Completed initialization of buffer pool 181019 9:04:06 InnoDB: Fatal error: cannot allocate memory for the buffer pool 181019 9:04:06 [ERROR] Plugin 'InnoDB' init function returned error. 181019 9:04:06 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 181019 9:04:06 [Note] Plugin 'FEEDBACK' is disabled. 181019 9:04:06 [ERROR] Unknown/unsupported storage engine: InnoDB 181019 9:04:06 [ERROR] Aborting
181019 9:04:06 [Note] /usr/libexec/mysqld: Shutdown complete
181019 09:04:07 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended 181022 02:54:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 181022 2:54:37 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 22837 ... 181022 2:54:37 InnoDB: The InnoDB memory heap is disabled 181022 2:54:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins 181022 2:54:37 InnoDB: Compressed tables use zlib 1.2.7 181022 2:54:37 InnoDB: Using Linux native AIO 181022 2:54:37 InnoDB: Initializing buffer pool, size = 128.0M 181022 2:54:37 InnoDB: Completed initialization of buffer pool 181022 2:54:37 InnoDB: highest supported file format is Barracuda. 181022 2:54:37 InnoDB: Starting crash recovery from checkpoint LSN=94454915 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... 181022 2:54:37 InnoDB: Starting final batch to recover 4 pages from redo log 181022 2:54:37 InnoDB: Waiting for the background threads to start 181022 2:54:38 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 94455139 181022 2:54:38 [Note] Plugin 'FEEDBACK' is disabled. 181022 2:54:38 [Note] Server socket created on IP: '0.0.0.0'. 181022 2:54:39 [Note] Event Scheduler: Loaded 0 events 181022 2:54:39 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.60-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===
From: Maria-discuss maria-discuss-bounces+turritopsis.dohrnii=teo-en-ming.com@lists.launchpad.net on behalf of Reindl Harald h.reindl@thelounge.net Sent: Friday, October 19, 2018 8:00 PM To: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Am 19.10.18 um 13:17 schrieb Turritopsis Dohrnii Teo En Ming:
Good evening from Singapore,
Here is my solution:
# systemctl start mariadb.service
# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 2 Server version: 5.5.60-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> quit Bye
# systemctl enable mariadb.service
what has this to do with a crash? you simply forgot to enable the service and rebootet
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
On Mon, 22 Oct 2018 10:28:31 +0000 Turritopsis Dohrnii Teo En Ming turritopsis.dohrnii@teo-en-ming.com wrote:
Good evening from Singapore,
My virtual server is an Amazon AWS Linux instance. I only gave it 1 GB of RAM.
How much RAM/memory do I need to support MariaDB SQL database server without crashing?
You've allocated 128M of ram to innodb buffer pool and its still failing. While you can set it less, its ultra small already and won't be useful if its less than your active data size.
You've undoubtedly got other memory consuming processes running. Tune their memory usage down.
Giving my virtual server more than 1 GB of RAM will cost me more money.
Sometimes you can't run a real service on less memory than your phone.
Am 22.10.18 um 23:12 schrieb Daniel Black:
Giving my virtual server more than 1 GB of RAM will cost me more money.
Sometimes you can't run a real service on less memory than your phone
+1
with 1 GB you just survive basic operations and system-upgrades, below 768 MB you even don't surivive memory spikes of a "dnf upgrade"
and yes, i remember the times when i had run MS Windows Advances Server with LAMP, Office, Photoshop, CorelDraw and a tiny Linux VM on a machine with 192 MB RAM but sadly that times are gone by lazy developers wating ressources
frankly i had seen page allocation errors leading to VMware HA trigger in 2015 on Fedora guests wth just 1 GB RAM doing *nothing* than rsync backups, that got better but doing anything useful with 1 GB RAM is a bad job and shows lack of any expirience as well as the orginal post did talking about crahses while not show any single sing of them but talk about "sytemctl start/enable" which has nothing to do with crashes
Good morning from Singapore Reindl Harald,
The 1st time my MariaDB SQL Database Server crashed in my Experimental WooCommerce Online Store, I was TOO LAZY to check system logs /var/log/mariadb/mariadb.log
The 2nd time my MariaDB SQL Database Server crashed in my Experimental WooCommerce Online Store, I have NO CHOICE but to check system logs /var/log/mariadb/mariadb.log
I am very sorry for my laziness.
________________________________ From: Maria-discuss maria-discuss-bounces+turritopsis.dohrnii=teo-en-ming.com@lists.launchpad.net on behalf of Reindl Harald h.reindl@thelounge.net Sent: Tuesday, October 23, 2018 5:39 AM To: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] My Solution to MariaDB Database Server Crashed in Experimental Online Store
Am 22.10.18 um 23:12 schrieb Daniel Black:
Giving my virtual server more than 1 GB of RAM will cost me more money.
Sometimes you can't run a real service on less memory than your phone
+1
with 1 GB you just survive basic operations and system-upgrades, below 768 MB you even don't surivive memory spikes of a "dnf upgrade"
and yes, i remember the times when i had run MS Windows Advances Server with LAMP, Office, Photoshop, CorelDraw and a tiny Linux VM on a machine with 192 MB RAM but sadly that times are gone by lazy developers wating ressources
frankly i had seen page allocation errors leading to VMware HA trigger in 2015 on Fedora guests wth just 1 GB RAM doing *nothing* than rsync backups, that got better but doing anything useful with 1 GB RAM is a bad job and shows lack of any expirience as well as the orginal post did talking about crahses while not show any single sing of them but talk about "sytemctl start/enable" which has nothing to do with crashes
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Maria Discuss in Launchpadhttps://launchpad.net/~maria-discuss launchpad.net Discussions about usage questions of the Maria project. Development discussions are done in the maria-developers group. (http://launchpad.net/~maria-developers) Commits are done by the Maria Captains (http://launchpad.net/~maria-captains)
Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss Maria Discuss in Launchpadhttps://launchpad.net/~maria-discuss launchpad.net Discussions about usage questions of the Maria project. Development discussions are done in the maria-developers group. (http://launchpad.net/~maria-developers) Commits are done by the Maria Captains (http://launchpad.net/~maria-captains)
More help : https://help.launchpad.net/ListHelp
Am 22.10.18 um 11:48 schrieb Turritopsis Dohrnii Teo En Ming:
My MariaDB SQL Database Server really crashed. I did not reboot my virtual server at all. It has crashed twice already.
in your first message you only mentioned systemctl start mariadb.service systemctl enable mariadb.service
at at least when you pretend that enable a service solved your porblemn and don't provide any useful informations what do you think?
http://www.catb.org/esr/faqs/smart-questions.html#beprecise
181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 128917504 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 96681984 bytes) 181019 9:04:06 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
reduce innodb_buffer_pool_size and look with mysqltuner which per-thread-buffers which you thougfht are per instance are pervertly high which is a often made mistake and last but not least it tells you the highest to expect memory usage from mysqld with your config where you need in mind that the OS and other applications needs memory too
anyways, 1 GB is a joke for a server doing more than sitting around
participants (4)
-
Daniel Black -
Reindl Harald -
Rhys.Campbell＠swisscom.com -
Turritopsis Dohrnii Teo En Ming