Bonjour à tous,
Je suis actuellement sous debian version 10.7 sur un Raspbery pi3.
Dessus est installé jeedom une superbe plateforme domotique mais depuis quelques jours je n'ai plus l’accès en local ou à distance à mon interface et un message d'erreur s'affiche
SQLSTATE[HY000] [2002] No such file or directory
Après quelques recherches je m'oriente vers un problème de mysql et mariadl.
Je suis donc allé dans le log de mysql et voilà ce qu'il en ressort.
2022-11-01 0:00:07 0 [Warning] The parameter innodb_large_prefix is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
2022-11-01 0:00:07 0 [Note] InnoDB: Using Linux native AIO
2022-11-01 0:00:07 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-11-01 0:00:07 0 [Note] InnoDB: Uses event mutexes
2022-11-01 0:00:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-11-01 0:00:07 0 [Note] InnoDB: Number of pools: 1
2022-11-01 0:00:07 0 [Note] InnoDB: Using generic crc32 instructions
221101 0:00:07 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.3.27-MariaDB-0+deb10u1
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 351526 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 = 0x0 thread_stack 0x49000
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 6878 6878 processes
Max open files 16384 16384 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 6878 6878 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core
Une âme charitable pour venir à mon aide svp.
Serait-ce un problème de place sur un fichier?
J'ai 45,5Go de libre sur 58,4Go du raspbery.
Pouvez vous m'aiguiller sur mes recherches.
Debian
Debian-France
Debian-Facile
Debian-fr.org
Forum-Debian.fr
Debian ?
Communautés
ou trouver un dépôt qui va bien pour arm 
.