mysql – MariaDB crashed: Unknown/unsupported storage engine: InnoDB

I’ve a Debian GNU/Linux 9 (4GB, 2 CPUs) on Digitalocean. Tonight (I’ve done nothing) my DB (mariaDB) crashed with this errors. I ran a wordpress with InnoDB and myISAM tables:

2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Using mutexes to ref count buffer pool pages
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: The InnoDB memory heap is disabled
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Compressed tables use zlib 1.2.8
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Using Linux native AIO
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Using SSE crc32 instructions
2020-10-17  0:51:18 140430430813568 (Note) InnoDB: Initializing buffer pool, size = 500.0M
InnoDB: mmap(549126144 bytes) failed; errno 12
2020-10-17  0:51:18 140430430813568 (ERROR) InnoDB: Cannot allocate memory for the buffer pool
2020-10-17  0:51:18 140430430813568 (ERROR) Plugin 'InnoDB' init function returned error.
2020-10-17  0:51:18 140430430813568 (ERROR) Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-10-17  0:51:18 140430430813568 (Note) Plugin 'FEEDBACK' is disabled.
2020-10-17  0:51:18 140430430813568 (ERROR) **Unknown/unsupported storage engine: InnoDB**
2020-10-17  0:51:18 140430430813568 (ERROR) Aborting


My full DB conf:

#
# These groups are read by MariaDB server.
# Use it for options that only the server (but not clients) should see
#
# See the examples of server my.cnf files in /usr/share/mysql/
#

# this is read by the standalone daemon and embedded servers
(server)

# this is only for the mysqld standalone daemon
(mysqld)

#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket      = /var/run/mysqld/mysqld.sock
port        = 3306
basedir     = /usr
datadir     = /var/lib/mysql
tmpdir      = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address        = 127.0.0.1

#
# * Fine Tuning
#
key_buffer_size     = 16M
max_allowed_packet  = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam_recover_options  = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10

innodb_buffer_pool_instances = 1
innodb_buffer_pool_size = 500M
max_heap_table_size     = 25M
tmp_table_size          = 25M
#log_slow_queries        = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes

#
# * Query Cache Configuration
#
query_cache_limit   = 2M
query_cache_size        = 50M

#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Enable the slow query log to see queries with especially long duration
#slow_query_log_file    = /var/log/mysql/mariadb-slow.log
#long_query_time = 10
#log_slow_rate_limit    = 1000
#log_slow_verbosity = query_plan
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id      = 1
#log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size   = 100M
#binlog_do_db       = include_database_name
#binlog_ignore_db   = exclude_database_name

#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!

#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates you can use for example the GUI tool "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
#
# Accept only connections using the latest and most secure TLS protocol version.
# ..when MariaDB is compiled with OpenSSL:
# ssl-cipher=TLSv1.2
# ..when MariaDB is compiled with YaSSL (default in Debian):
# ssl=on

#
# * Character sets
#
# MySQL/MariaDB default is Latin1, but in Debian we rather default to the full
# utf8 4-byte character set. See also client.cnf
#
character-set-server  = utf8mb4
collation-server      = utf8mb4_general_ci

#
# * Unix socket authentication plugin is built-in since 10.0.22-6
#
# Needed so the root database user can authenticate without a password but
# only when running as the unix root user.
#
# Also available for other users if required.
# See https://mariadb.com/kb/en/unix_socket-authentication-plugin/

# this is only for embedded server
(embedded)

# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
(mariadb)

# This group is only read by MariaDB-10.1 servers.
# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
(mariadb-10.1)

Here my first page of htop
htop result after some minutes
Could not export/copy htop result.

I would be happy if you could help me out!!

Thanks a lot
M

Windows 10 crashed. Reinstalled and now need to install fresh BlueStacks. Can I get the old instances somehow from the Windows.old folder?

I had BlueStacks running on Windows 10 and then I got the Blue screen of death. I need to reinstall windows. My existing BlueStacks will be save in Windows.old. Is there a way to "move" the old instances back once I reinstall Windows and install a fresh BlueStacks again?

❕NEWS – Reasons For Bitcoin Crashed Last July 10 and Analysis | NewProxyLists

According to statistical data, an exchange was responsible for the drop of bitcoin last July 10, 2020, where bitcoin dropped down 150$ in a just a few seconds, more data said that the cause for the drop was bitcoin miners who sold their bitcoins at once during the time, the effect of this case was felt market-wide,

But after the dropped, bitcoin immediately rebounded back up, some analyst suspect that after the sell-off investors were jumping to buy bitcoin, increasing the demand at the same time

Crashed site/site is down

guys!
I am running a site on GCP AND USING THE THEME COLORMAG. I was updating the theme and then the site crashed. I can log in to the backend but everything is wiped away.
The error I am getting is that the theme directory is not there.
What do I do?

bitcoind – Recover corrupted wallet due to system crashed

My server was crashed suddenly and didn’t shut down bitcoin core probably, so now my wallet was corrupted due to it didn’t be released. I try to moved the corrupted wallet to a new server but it can’t be load:

Wallet file verification failed: wallet.dat corrupt, salvage failed

I have also tried to use pywallet to rescue, but getting this error:

ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.

I suspect that my wallet.dat was totally corrupt so pywallet couldn’t found main . Any help on this please ? Possible to get back my privatekey from wallet.dat please ? Thanks alot.

Information:

bitcoin version: v0.18
os: centos7

Mysql Crashed WordPress database tables (Ubuntu)

We installed Mysql on the Ubuntu server, and having the multiple problems, at times, MySQL was automatically closed, I have to restart it again and again. When I check the MySQL logs, I found that there are tables that are blocked and not repaired. so I should know that by this MySQL problem my server is stopped?

Here is the error log

2020-04-24T14:53:43.859753Z 3 [ERROR] /usr/sbin/mysqld: Table './abc/wpdw_woocommerce_sessions' is marked as crashed and should be repaired

2020-04-24T14:53:41.320799Z 2 [ERROR] /usr/sbin/mysqld: Table './abc/wpdw_options' is marked as crashed and should be repaired

I also repaired the table, but after one day this problem reappears and the problem of server failure is launched. Is there a permanent solution?

If anyone knows, help me solve this problem

Thanks in advance

125 passenger planes crashed

Today, 25,000 people have died from coronavirus worldwide. It is as if 125 passenger planes have crashed.

If a large passenger plane crashes, 200 people are killed. How bad the situation is.

The lighthouse returned an error: INTERNAL: APP :: 1: abnormal rendering stop, state = crashed exit_code = 1

When analyzing my page https://besttransfers-mallorca.com/
PageSpeed ​​Insights gives me this error
How could I fix it? Please, please !!
Thank you
sandra

crash – Catalina Crashed my mac!

When Catalina came out, I waited for other updates because of my Adobe. Once installed, it will detach. Can not connect, can not do anything, now it always comes back to the utility. At this point, I just want to erase and install and register my Mac!

Can I flash Android on a device with mmcblk0 crashed

Can Android device with fully crashed /dev/mmcblk0 (without /dev/mmcblk0p* partitions) be still flashed using fastboot? Is it true that the crash /dev/mmcblk0 do not delete /dev/mmcblk0boot* partitions?