천마건빵1096;.104;Nj12;,144;였lj16;데, 서버 1116;시1089; 후 mariadb 시1089;1060; 안.104;네요.
구글,160;색해봐도 알수가 없네요.
/var/log/mariadb/mariadb.log 파1068; 내용1077;니다.
ᕬ1;시 왜그런1648; 알수 1080;1012; 가요?
221126 20:50:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
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 toInnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
221126 20:50:08 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/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: 5.5.68-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=502
thread_count=0
It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1232387 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 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x55a879874cad]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x55a879488975]
sigaction.c:0(__restore_rt)[0x7f5dfeb30630]
:0(__GI_raise)[0x7f5dfd257387]
:0(__GI_abort)[0x7f5dfd258a78]
/usr/libexec/mysqld(+0x63845f)[0x55a87961d45f]
/usr/libexec/mysqld(+0x638f69)[0x55a87961df69]
/usr/libexec/mysqld(+0x73b504)[0x55a879720504]
/usr/libexec/mysqld(+0x730487)[0x55a879715487]
/usr/libexec/mysqld(+0x63b17d)[0x55a87962017d]
/usr/libexec/mysqld(+0x62f0f6)[0x55a8796140f6]
pthread_create.c:0(start_thread)[0x7f5dfeb28ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f5dfd31f96d]
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.
221126 20:50:09 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
감사합니다.
이래도 해결 안 되면 백업된 상태니 패키지의 아무것도 없는 DB랑 설정 파일로 서비스만 올려보세요
원인을 알수가 없어 그냥 삭제 하고 재설치를 하였습니다.
ㅇ DB 프로그램 삭제
yum remove mariadb mariadb-libs mariadb-server
ㅇ DB 파일 삭제 /var/lib/mysql
ㅇ db 재설치
yum install mariadb mariadb-libs mariadb-server
ㅇ db 백업 복구
정상가동하였습니다.
감사합니다.
최근 깔거나 지운게 있다면 그쪽 의심해보시고, 짚히는 구석이 없다면 디스크라던가 심각한 원인이 있을 수 도 있습니다 (안 건드리는데 난대없이 라이브러리나 바이너리가 망가지면 시스템 신뢰성이 0입니다)
하드웨어 문제 같으니.....
메모리 접점 확인 하시고.
하드드라이브 베드섹터 검사 해 보세요.