[ÇØ°á] mariadb ½ÃÀÛ ¿À·ù³µ¾î¿ä

   Á¶È¸ 3366   Ãßõ 0    

잘되던거였는데, 서버 재시작 후 mariadb 시작이 안되네요.
구글검색해봐도 알수가 없네요.

/var/log/mariadb/mariadb.log 파일 내용입니다.
혹시 왜그런지 알수 있을 가요?


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


감사합니다.


반갑습니다.
ªÀº±Û Àϼö·Ï ½ÅÁßÇϰÔ.
dateno1 2022-11
ÀÏ´Ü ¼³Á¤À̶û DB ÆÄÀÏ ¹é¾÷ÈÄ ÆÐŰÁö Áö¿ü´Ù°¡ ´Ù½Ã ±ò¾Æº¸¼¼¿ä (°¡´ÉÇÏ´Ù¸é 1Â÷ ÀÇÁ¸¼º±îÁö´Â È®ÀÎÈÄ µ¤¾î¼­ ´Ù½Ã ±ò¾Æº¸½Ã´Â°É ÃßõÇÕ´Ï´Ù)

ÀÌ·¡µµ ÇØ°á ¾È µÇ¸é ¹é¾÷µÈ »óÅÂ´Ï ÆÐŰÁöÀÇ ¾Æ¹«°Íµµ ¾ø´Â DB¶û ¼³Á¤ ÆÄÀÏ·Î ¼­ºñ½º¸¸ ¿Ã·Áº¸¼¼¿ä
     
°¨»çÇÕ´Ï´Ù.
¿øÀÎÀ» ¾Ë¼ö°¡ ¾ø¾î ±×³É »èÁ¦ Çϰí À缳ġ¸¦ ÇÏ¿´½À´Ï´Ù.

¤· DB ÇÁ·Î±×·¥ »èÁ¦
yum remove mariadb mariadb-libs mariadb-server
¤· DB ÆÄÀÏ »èÁ¦  /var/lib/mysql
¤· db À缳ġ
yum install mariadb mariadb-libs mariadb-server
¤· db ¹é¾÷ º¹±¸

Á¤»ó°¡µ¿ÇÏ¿´½À´Ï´Ù.
°¨»çÇÕ´Ï´Ù.
          
dateno1 2022-11
¶óÀ̺귯¸®³ª ¹ÙÀ̳ʸ® ¼Õ»óµÇ¾ú³ªº¸³×¿ä

ÃÖ±Ù ±ò°Å³ª Áö¿î°Ô ÀÖ´Ù¸é ±×ÂÊ ÀǽÉÇØº¸½Ã°í, ¤È÷´Â ±¸¼®ÀÌ ¾ø´Ù¸é µð½ºÅ©¶ó´ø°¡ ½É°¢ÇÑ ¿øÀÎÀÌ ÀÖÀ» ¼ö µµ ÀÖ½À´Ï´Ù (¾È °Çµå¸®´Âµ¥ ³­´ë¾øÀÌ ¶óÀ̺귯¸®³ª ¹ÙÀ̳ʸ®°¡ ¸Á°¡Áö¸é ½Ã½ºÅÛ ½Å·Ú¼ºÀÌ 0ÀÔ´Ï´Ù)
¹Ú¹®Çü 2022-11
¼ö°íÇϼ̽À´Ï´Ù..
This error can also be caused by malfunctioning hardware...

Çϵå¿þ¾î ¹®Á¦ °°À¸´Ï.....
¸Þ¸ð¸® Á¢Á¡ È®ÀÎ ÇϽðí.
Çϵåµå¶óÀÌºê º£µå¼½ÅÍ °Ë»ç ÇØ  º¸¼¼¿ä.


QnA
Á¦¸ñPage 963/5735
2015-12   1802282   ¹é¸Þ°¡
2014-05   5277525   Á¤ÀºÁØ1
2020-05   3335   ±èÁöö
2015-07   3335   Ä®µµ
2021-12   3335   VSPress
2020-11   3335   Sikieiki
2023-03   3335   ¿ö´Ï´Ô
2023-05   3335   ±æ°¡´ø´ººñ
2021-10   3335   ¹ÌÄ£°¨ÀÚ
2019-09   3336   ÇູÇϼ¼
2023-04   3336   ½Ãµµ´Ï
2018-11   3336   ¾ÈÇü°ï
2020-07   3336   ĸƾ¾Æ¸Þ¸®Ä«³ë
2018-08   3336   ¹Ì´ÏTM
2019-06   3336   online9
2020-09   3336   µ¶µµ78
2017-05   3336   ÀÎÃʸ®
2017-08   3336   Àü»ê½Ç«Âî
2020-09   3336   VSPress
2014-03   3336   ¹Ì¼ö¸Ç
2021-05   3336   inquisitive
2020-11   3336   ¶¥ºÎÀÚ