Job for mysqld.service failed because a timeout was exceeded

Stack Overflow en español Asked by Neg90 on August 29, 2020

Estoy teniendo problemas para iniciar el servicio mysql en un servidor centos7, estaba todo funcionando correctamente, pero al reiniciar el servidor el servicio de base de datos no inicio, al intentar iniciarlo vía ssh se demoraba unos 10 minutos y devuelve el siguiente error

Job for mysqld.service failed because a timeout was exceeded.

En el sistema no se realizo ninguna modificación de ningún tipo, solo re reinicio, la base de datos principal (la que necesito para que funcione nuevamente la web) pesa casi 1 GB, sospecho que el problema esta en el peso de la base de datos pero no estoy seguro, también puede ser que simplemente este dañada..

El sitio que intento recuperar es un moodle, dejo todos los datos que fui recolectando mientras intentaba solucionar el problema.

Desde ya muchas gracias.


2020-08-23 11:39:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is 
deprecated. Please use --explicit_defaults_for_timestamp serv$
2020-08-23 11:39:50 0 [Note] /usr/sbin/mysqld (mysqld 5.6.47) starting as 
process 17199 ...
2020-08-23 11:39:50 17199 [Warning] Buffered warning: Changed limits: 
max_open_files: 1024 (requested 5000)

2020-08-23 11:39:50 17199 [Warning] Buffered warning: Changed limits: 
table_open_cache: 431 (requested 2000)

2020-08-23 11:39:50 17199 [Note] Plugin 'FEDERATED' is disabled.
2020-08-23 11:39:50 17199 [Note] InnoDB: Using atomics to ref count buffer 
pool pages
2020-08-23 11:39:50 17199 [Note] InnoDB: The InnoDB memory heap is disabled
2020-08-23 11:39:50 17199 [Note] InnoDB: Mutexes and rw_locks use GCC 
2020-08-23 11:39:50 17199 [Note] InnoDB: Memory barrier is not used
2020-08-23 11:39:50 17199 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-08-23 11:39:50 17199 [Note] InnoDB: Using Linux native AIO
2020-08-23 11:39:50 17199 [Note] InnoDB: Using CPU crc32 instructions
2020-08-23 11:39:50 17199 [Note] InnoDB: Initializing buffer pool, size = 
2020-08-23 11:39:50 17199 [Note] InnoDB: Completed initialization of buffer 
2020-08-23 11:39:50 17199 [Note] InnoDB: Highest supported file format is 
InnoDB: Error: trying to access page number 4294962430 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2020-08-23 11:39:50 7fad5c9ab780  InnoDB: Assertion failure in thread 
140382559713152 in file line 5674
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
14:39:50 UTC - mysqld got signal 6 ;
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68109 
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
The manual page at contains
information that should help you find out what is causing the crash.
200823 11:39:50 mysqld_safe mysqld from pid file /var/run/mysqld/ 

Cualquier tipo de ayuda es bienvenida.

Este es mi archivo my.cnf

 # For advice on how to change settings please see

 # Remove leading # and set to the amount of RAM for the most important data
 # cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
 # innodb_buffer_pool_size = 128M
 # Remove leading # to turn on a very important data integrity option: logging
 # changes to the binary log between backups.
 # log_bin
 # Remove leading # to set options mainly useful for reporting servers.
 # The server defaults are faster for transactions and fast SELECTs.
 # Adjust sizes as needed, experiment to find the optimal values.
 # join_buffer_size = 128M
 # sort_buffer_size = 2M
 # read_rnd_buffer_size = 2M
 #key_buffer = 16M
 #thread_stack = 192K
 #thread_cache_size = 8


 # Disabling symbolic-links is recommended to prevent assorted security risks

 # Recommended in standard MySQL setup

 !includedir /etc/my.cnf.d/

mysql –version

mysql  Ver 14.14 Distrib 5.6.47, for Linux (x86_64) using  EditLine wrapper

Datos del sistema operativo.

cat /etc/*release

CentOS Linux release 7.7.1908 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID_LIKE="rhel fedora"
PRETTY_NAME="CentOS Linux 7 (Core)"


CentOS Linux release 7.7.1908 (Core)
CentOS Linux release 7.7.1908 (Core)

Al intentar iniciar mysql devuelve esto

systemctl status mysqld.service -l
● mysqld.service - MySQL Community Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: activating (start-post) since dom 2020-08-23 12:29:52 -03; 9min ago
  Process: 28064 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
  Process: 28049 ExecStartPre=/usr/bin/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 28064 (code=exited, status=0/SUCCESS);         : 28066 (mysql-systemd-s)
   CGroup: /system.slice/mysqld.service
             ├─28066 /bin/bash /usr/bin/mysql-systemd-start post
             └─30276 sleep 1

ago 23 12:29:52 systemd[1]: Stopped MySQL Community Server.
ago 23 12:29:52 systemd[1]: Starting MySQL Community Server...
ago 23 12:29:52 mysqld_safe[28064]: 200823 12:29:52 mysqld_safe Logging to '/var/log/mysqld.log'.
ago 23 12:29:52 mysqld_safe[28064]: 200823 12:29:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

Add your own answers!

Ask a Question

Get help from others!

© 2024 All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP