Project

General

Profile

Tâche #34546

Distribution EOLE - Scénario #35233: Traitement express fermés 31/03/2023

probleme serveur scribe 2.8.1 - Collège Grisolles - Département 82

Added by Julien Lacombe almost 2 years ago. Updated over 1 year ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
08/31/2022
Due date:
% Done:

0%

Remaining (hours):
0.0

Description

Bonjour,
Je me permets de vous contacter car nous rencontrons un problème sur un de nos serveur scribe au niveau de la BD Mysql.

Notre prestataire a essayé de résoudre le problème sans succès.
Pourriez vous nous assister?

Je dispose des logs que je vais vous transmettre en parallèle par mail.

Le problème se situe au niveau de la BD MYSQL.

L’erreur démontre un problème de mise à niveau suite à une mise à jour.

Elle se trouve dans un état « entre deux » et ne permet plus d’accéder à la BD.

Il semble que la donnée soit altérer.

Cdlt

Contact SPIE Laurent Gonzalez

Ci-dessous les logs qui démontre de problème :

2022-08-31T07:39:00.124591Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.

2022-08-31T07:39:00.124621Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.20.04.2) starting as process 646192

2022-08-31T07:39:00.135677Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

2022-08-31T07:39:00.928767Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.29, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html

2022-08-31T07:39:00.928809Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.

2022-08-31T07:39:01.258014Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine

2022-08-31T07:39:01.258260Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.

2022-08-31T07:39:01.258297Z 0 [ERROR] [MY-010119] [Server] Aborting

2022-08-31T07:39:01.258980Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.20.04.2) (Ubuntu).

2022-08-31T07:39:01.590141Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 35000)

2022-08-31T07:39:01.980832Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.

History

#1 Updated by Daniel Dehennin almost 2 years ago

  • Assigned To set to Daniel Dehennin

Bonjour.

De tout ce que je comprends, en lisant la documentation et cherchant sur internet, c’est un soucis lors de l’arrête de la base de donnée avant mise à jour.

Est-ce que la mise à jour est arrivée à son terme où s’est-elle arrêtée sur mysql ?

Disposez-vous d’une sauvegarde ?

#2 Updated by Gilles Grandgérard almost 2 years ago

L'incident s'est passé le 29 aout à 9h14.
this error can also be caused by malfunctioning hardware.

Il semble qu'il faille regénérer la BD.
Il vous faut la sauvegarde du 28.

2022-08-29T09:14:00.141726Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-08-29T09:14:00.144207Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2022-08-29T09:14:00.144240Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29-0ubuntu0.20.04.3) starting as process 2927
2022-08-29T09:14:00.154997Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-29T09:14:00.641772Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-08-29T09:14:01.248546Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2022-08-29T09:14:01.266299Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2022-08-29T09:14:01.293394Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fut0lst.ic:81:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 139699112900352
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:14:01 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f0e30000b60
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 = 7f0e3bffebf0 thread_stack 0x30000
2022-08-29T09:14:01.299019Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-08-29T09:14:01.299072Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55678ed1bad1]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2fb) [0x55678dbbc7db]
/usr/sbin/mysqld(my_server_abort()+0x76) [0x55678dbbc926]
/usr/sbin/mysqld(my_abort()+0xe) [0x55678ed15ace]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x349) [0x55678ef917b9]
/usr/sbin/mysqld(+0x24c59f8) [0x55678ef509f8]
/usr/sbin/mysqld(+0x24c6d74) [0x55678ef51d74]
/usr/sbin/mysqld(trx_purge(unsigned long, unsigned long, bool)+0x14a) [0x55678ef523da]
/usr/sbin/mysqld(srv_purge_coordinator_thread()+0x6ef) [0x55678ef2025f]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)()> > >::_M_run()+0xbc) [0x55678ee2508c]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6de4) [0x7f0ea3d5ede4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f0ea47fb609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f0ea3a4b133]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2022-08-29T09:24:21.724035Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-08-29T09:24:21.726607Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2022-08-29T09:24:21.726645Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.20.04.2) starting as process 44336
2022-08-29T09:24:21.748925Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-29T09:24:21.952527Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.29, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
2022-08-29T09:24:21.952571Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2022-08-29T09:24:22.283911Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2022-08-29T09:24:22.284198Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2022-08-29T09:24:22.284236Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-08-29T09:24:22.285615Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.20.04.2)  (Ubuntu).
2022-08-29T09:24:23.681170Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 35000)

#3 Updated by Joël Cuissinat almost 2 years ago

  • Tracker changed from Demande to Tâche
  • Status changed from Nouveau to En cours
  • Parent task set to #34550

#4 Updated by Joël Cuissinat over 1 year ago

  • Parent task changed from #34550 to #34668

#5 Updated by Joël Cuissinat over 1 year ago

  • Status changed from En cours to Fermé
  • Parent task changed from #34668 to #35233
  • Remaining (hours) set to 0.0

Also available in: Atom PDF