✓ Solved

Mysqld stop working

cause of low memory i have (1GB, debian10) or something missing in the config files from mysql server? here are the logs

    sudo tail -f /var/log/mysql/error.log
    2021-07-26  7:56:28 0 [ERROR] InnoDB: mmap(137035776 bytes) failed; errno 12
    2021-07-26  7:56:28 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
    2021-07-26  7:56:28 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
    2021-07-26  7:56:28 0 [Note] InnoDB: Starting shutdown...
    2021-07-26  7:56:28 0 [ERROR] Plugin 'InnoDB' init function returned error.
    2021-07-26  7:56:28 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2021-07-26  7:56:28 0 [Note] Plugin 'FEEDBACK' is disabled.
    2021-07-26  7:56:28 0 [ERROR] Unknown/unsupported storage engine: InnoDB
    2021-07-26  7:56:28 0 [ERROR] Aborting
    sudo systemctl status mysqld
    ● mariadb.service - MariaDB 10.3.29 database server
       Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Mon 2021-07-26 07:56:28 BST; 10h ago
         Docs: man:mysqld(8)
      Process: 8689 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
      Process: 8692 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
      Process: 8696 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_rec
      Process: 8823 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILU
     Main PID: 8823 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    Jul 26 07:56:23 extdebian-lon systemd[1]: Starting MariaDB 10.3.29 database server...
    Jul 26 07:56:27 extdebian-lon mysqld[8823]: 2021-07-26  7:56:27 0 [Note] /usr/sbin/mysqld (mysqld 10.3.29-MariaDB-0+deb10u1) s
    Jul 26 07:56:28 extdebian-lon systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
    Jul 26 07:56:28 extdebian-lon systemd[1]: mariadb.service: Failed with result 'exit-code'.
    Jul 26 07:56:28 extdebian-lon systemd[1]: Failed to start MariaDB 10.3.29 database server.

Thanks in advance

3 Replies

✓ Best Answer

I’d assume that you’re running too much for the plan you have.

BUT…Check your swap file and memory usage. If your swap file is half or more used, you need to upgrade your plan.

It’s also possible that when you try to run your web server that it’s crashing due to lack of memory and therefore you might not see a memory issue currently.

Looks like you're running out memory. Check that you have swap space setup. It's possible that you need to upgrade to a higher memory plan.

Also, give us more details on what you are running.

Running 3 website (apache) on it with wordpress and a mumble server for our gamer.


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct