Percebi que meu servidor mysql estava inativo nesta manhã e desde então tenho tentado reiniciá-lo e solucionar o problema.
Quando eu uso este código
service mysql restart
Eu recebi os seguintes erros
Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
Mesmo com innodb_force_recovery = 1
E quando eu executo o systemctl status mysql.service , recebo isso
mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Sat 2018-03-10 11:55:53 EST; 39s ago
Process: 522 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
Mar 10 12:05:31 vps159679 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Mar 10 12:06:02 vps159679 /etc/init.d/mysql[5737]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Mar 10 12:06:02 vps159679 /etc/init.d/mysql[5737]: [61B blob data]
Mar 10 12:06:02 vps159679 /etc/init.d/mysql[5737]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Mar 10 12:06:02 vps159679 /etc/init.d/mysql[5737]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Mar 10 12:06:02 vps159679 /etc/init.d/mysql[5737]:
Mar 10 12:06:02 vps159679 mysql[4911]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Mar 10 12:06:02 vps159679: mysql.service: control process exited, code=exited status=1
Mar 10 12:06:02 vps159679: Failed to start LSB: Start and stop the mysql database server daemon.
Mar 10 12:06:02 vps159679: Unit mysql.service entered failed state.
E ao executar o journalctl -xn
-- Logs begin at Sat 2018-03-10 11:55:20 EST, end at Sat 2018-03-10 12:04:15 EST.
Mar 10 12:03:58 vps159679 spamd[1226]: spamd: clean message (1.9/5.0)
Mar 10 12:03:58 vps159679 spamd[1226]: spamd: result: . 1 - URIBL_BLOC
Mar 10 12:03:58 vps159679 spamd[648]: prefork: child states: II
Mar 10 12:04:04 vps159679 sshd[4691]: error: Could not load host key:
Mar 10 12:04:12 vps159679 sshd[4691]: Invalid user openerp from 175.20
Mar 10 12:04:12 vps159679 sshd[4691]: input_userauth_request: invalid
Mar 10 12:04:12 vps159679 sshd[4691]: pam_unix(sshd:auth): check pass;
Mar 10 12:04:12 vps159679 sshd[4691]: pam_unix(sshd:auth): authenticat
Mar 10 12:04:14 vps159679 sshd[4691]: Failed password for invalid user
Mar 10 12:04:15 vps159679 sshd[4691]: Connection closed by 175.207.12.
E a parte final do meu log do mysql é mostrada abaixo
InnoDB: End of page dump
180310 12:05:32 InnoDB: Page checksum 3188502394, prior-to-4.0.14-form checksum 1352818685
InnoDB: stored checksum 3188502394, prior-to-4.0.14-form stored checksum 1352818685
InnoDB: Page lsn 6 130089285, low 4 bytes of lsn at page end 130089285
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
17:05:32 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 674050 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x55efd2700653]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55efd25ec9a4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fc0763b5890]
/usr/sbin/mysqld(+0x6316cb)[0x55efd28496cb]
/usr/sbin/mysqld(+0x5a59e9)[0x55efd27bd9e9]
/usr/sbin/mysqld(+0x5638e6)[0x55efd277b8e6]
/usr/sbin/mysqld(+0x65256e)[0x55efd286a56e]
/usr/sbin/mysqld(+0x65286b)[0x55efd286a86b]
/usr/sbin/mysqld(+0x64e327)[0x55efd2866327]
/usr/sbin/mysqld(+0x6434eb)[0x55efd285b4eb]
/usr/sbin/mysqld(+0x5883aa)[0x55efd27a03aa]
/usr/sbin/mysqld(+0x588a83)[0x55efd27a0a83]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fc0763ae064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc074e5e62d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.