Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#11439 closed Bug/Something is broken (fixed)

Site off-line Urgente

Reported by: https://id.mayfirst.org/cimac Owned by:
Priority: Urgent Component: Tech
Keywords: mysql mx25 Cc: erq@…, https://id.mayfirst.org/adolfo
Sensitive: no

Description

Hola!

Nuestro portal cimacnoticias.com.mx esta fuera de línea. Nos envía el siguiente mensaje:

Site off-line The site is currently not available due to technical problems. Please try again later. Thank you for your understanding.

If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider's database server is running. For more help, see the handbook, or contact your hosting provider.

Pueden apooyarnos.

Muchas gracias

Change History (5)

comment:1 Changed 3 years ago by https://id.mayfirst.org/erq

hola compañer@s Encontré el servidor mysql detenido y estas líneas en la bitácora /var/log/syslog, quizás puedan servir para diagnosticar la causa del problema:

mx25:~# grep mysql /var/log/syslog
Feb 17 13:11:13 mx25 mysqld_safe: Number of processes running now: 1
Feb 17 13:11:13 mx25 mysqld_safe: mysqld process hanging, pid 1566 - killed
Feb 17 13:11:14 mx25 mysqld_safe: mysqld restarted
Feb 17 13:11:14 mx25 mysqld: 160217 13:11:14 [Note] Plugin 'FEDERATED' is disabled.
Feb 17 13:11:14 mx25 mysqld: 160217 13:11:14  InnoDB: Initializing buffer pool, size = 8.0M
Feb 17 13:11:14 mx25 mysqld: 160217 13:11:14  InnoDB: Completed initialization of buffer pool
Feb 17 13:11:14 mx25 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 128 3142844030
Feb 17 13:11:14 mx25 mysqld: 160217 13:11:14  InnoDB: Database was not shut down normally!
Feb 17 13:11:14 mx25 mysqld: InnoDB: Starting crash recovery.
Feb 17 13:11:14 mx25 mysqld: InnoDB: Reading tablespace information from the .ibd files...
Feb 17 13:11:16 mx25 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Feb 17 13:11:16 mx25 mysqld: InnoDB: buffer...
Feb 17 13:11:16 mx25 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 128 3142896047
Feb 17 13:11:16 mx25 mysqld: 160217 13:11:16  InnoDB: Starting an apply batch of log records to the database...
Feb 17 13:11:17 mx25 mysqld: InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
Feb 17 13:11:17 mx25 mysqld: InnoDB: Apply batch completed
Feb 17 13:11:17 mx25 mysqld: 160217 13:11:17  InnoDB: Started; log sequence number 128 3142896047
Feb 17 13:11:17 mx25 mysqld: 160217 13:11:17 [Note] Event Scheduler: Loaded 0 events
Feb 17 13:11:17 mx25 mysqld: 160217 13:11:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 17 13:11:17 mx25 mysqld: Version: '5.1.73-1+deb6u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
Feb 17 13:11:50 mx25 mysqld: 160217 13:11:50 [Note] /usr/sbin/mysqld: Normal shutdown
Feb 17 13:11:50 mx25 mysqld: 
Feb 17 13:11:50 mx25 mysqld: 160217 13:11:50 [Note] Event Scheduler: Purging the queue. 0 events
Feb 17 13:11:52 mx25 mysqld: 160217 13:11:52  InnoDB: Starting shutdown...
Feb 17 13:11:57 mx25 mysqld: 160217 13:11:57  InnoDB: Shutdown completed; log sequence number 128 3143098420
Feb 17 13:11:57 mx25 mysqld: 160217 13:11:57 [Note] /usr/sbin/mysqld: Shutdown complete
Feb 17 13:11:57 mx25 mysqld: 
Feb 17 13:11:58 mx25 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

Reiniciaré el servidor de base de datos mysql

comment:2 Changed 3 years ago by https://id.mayfirst.org/erq

  • Cc https://id.mayfirst.org/adolfo added
  • Keywords mysql mx25 added
  • Resolution set to fixed
  • Status changed from new to closed

Compañer@s de CIMAC: el sitio ahora está de nuevo funcional, no encontré ningún mensaje de advertencia o error al arranque, así que reportaré a Adolfo para su conocimiento y cerraré el ticket -siéntanse en libertad de abrirlo de nuevo en caso necesario- Saludos

comment:3 Changed 3 years ago by https://id.mayfirst.org/cimac

Hola!

Muchas gracias por su apoyo. Estaremos al pendiente.

Saludos

comment:4 Changed 3 years ago by https://id.mayfirst.org/cimac

Ahora nuestro problema es con las listas de aprobación de cimacdiario, nuestro servicio no ha caido en http://listas.cimac.laneta.apc.org/admindb/cimacdiario

Asimismo en el administrador de correo (thunderbird) no entran, ni salen correos.

Espero respuesta, muchas gracias.

comment:5 Changed 3 years ago by https://id.mayfirst.org/jaimev

Creo en el proceso de actualizar el servidor mx25 para mitigar los riesgos de un nuevo bug de seguridad en libc https://www.debian.org/security/2016/dsa-3481 los procesos de mysql y mailman fueron detenidos. Enrique resolvió lo de mysql y acabo ver reiniciar mailman. Pronto sus correos a la lista debe empezar a fluir.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.