| View previous topic :: View next topic |
| Author |
Message |
Sage
n00b
Joined: 01 Jul 2020
Posts: 1
|
 Posted: Wed Jul 01, 2020 10:51 am Post subject: MariaDB crashing. zm and mythtv crashing. [solvedish] |
 |
|
[Moderator note: split from the solved thread MariaDB crashing. zm and mythtv crashing. [solvedish]. -Hu]
Hi guys,
I am getting this issue in mariadb container that looks like the issue mentioned above.... the container restarted bz of this issue:
| Code: |
2020-06-26T11:07:36.385673273Z stdout F 2020-06-26 11:07:36 2246754 [ERROR] [FATAL] InnoDB: fsync() returned 5
2020-06-26T11:07:36.386131082Z stdout F 200626 11:07:36 [ERROR] mysqld got signal 6 ;
2020-06-26T11:07:36.388155119Z stdout F This could be because you hit a bug. It is also possible that this binary
2020-06-26T11:07:36.38818302Z stdout F or one of the libraries it was linked against is corrupt, improperly built,
2020-06-26T11:07:36.38819732Z stdout F or misconfigured. This error can also be caused by malfunctioning hardware.
2020-06-26T11:07:36.38820992Z stdout F
2020-06-26T11:07:36.388243621Z stdout F To report this bug, see https://mariadb.com/kb/en/reporting-bugs
2020-06-26T11:07:36.388255321Z stdout F
2020-06-26T11:07:36.388278322Z stdout F We will try our best to scrape up some info that will hopefully help
2020-06-26T11:07:36.388293022Z stdout F diagnose the problem, but since we have already crashed,
2020-06-26T11:07:36.388304722Z stdout F something is definitely wrong and this may fail.
2020-06-26T11:07:36.388315522Z stdout F
2020-06-26T11:07:36.388326922Z stdout F Server version: 10.4.12-MariaDB
2020-06-26T11:07:36.388339323Z stdout F key_buffer_size=134217728
2020-06-26T11:07:36.388361423Z stdout F read_buffer_size=131072
2020-06-26T11:07:36.388373323Z stdout F max_used_connections=25
2020-06-26T11:07:36.388384723Z stdout F max_threads=153
2020-06-26T11:07:36.388397924Z stdout F thread_count=34
2020-06-26T11:07:36.388409224Z stdout F It is possible that mysqld could use up to
2020-06-26T11:07:36.388420624Z stdout F key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467756 K bytes of memory
2020-06-26T11:07:36.388439524Z stdout F Hope that's ok; if not, decrease some variables in the equation.
2020-06-26T11:07:36.388458325Z stdout F
2020-06-26T11:07:36.388474025Z stdout F Thread pointer: 0x7fd59ed4d388
2020-06-26T11:07:36.388485825Z stdout F Attempting backtrace. You can use the following information to find out
2020-06-26T11:07:36.388497326Z stdout F where mysqld died. If you see no messages after this, something went
2020-06-26T11:07:36.388508426Z stdout F terribly wrong...
2020-06-26T11:07:36.441002295Z stdout F stack_bottom = 0x7fd5c21fc678 thread_stack 0x49000
2020-06-26T11:07:36.563812362Z stdout F /opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x55b805333479]
2020-06-26T11:07:36.565731298Z stdout F /opt/bitnami/mariadb/sbin/mysqld(handle_fatal_signal+0x53d)[0x55b804ea14dd]
2020-06-26T11:07:36.588551819Z stdout F /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fd5d6e3a730]
2020-06-26T11:07:36.611661946Z stdout F /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7fd5d639e7bb]
2020-06-26T11:07:36.612037953Z stdout F /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fd5d6389535]
2020-06-26T11:07:36.634609469Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0x5978c3)[0x55b804bc28c3]
2020-06-26T11:07:36.635986495Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0x57e3e4)[0x55b804ba93e4]
2020-06-26T11:07:36.637947531Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xb8ad78)[0x55b8051b5d78]
2020-06-26T11:07:36.639627962Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xb8d57d)[0x55b8051b857d]
2020-06-26T11:07:36.641320993Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xa4595a)[0x55b80507095a]
2020-06-26T11:07:36.641320993Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xa4595a)[0x55b80507095a]
2020-06-26T11:07:36.643334531Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xa464a5)[0x55b8050714a5]
2020-06-26T11:07:36.645204665Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0xaf84b4)[0x55b8051234b4]
2020-06-26T11:07:36.647153301Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0x9f3367)[0x55b80501e367]
2020-06-26T11:07:36.648910534Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0x877095)[0x55b804ea2095]
2020-06-26T11:07:36.650844469Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z15ha_commit_transP3THDb+0x4dd)[0x55b804eae23d]
2020-06-26T11:07:36.652283996Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x3c)[0x55b804d9f12c]
2020-06-26T11:07:36.653905126Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xe5d)[0x55b804cb267d]
2020-06-26T11:07:36.655475755Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x3fe)[0x55b804ccce2e]
2020-06-26T11:07:36.657046184Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x7f)[0x55b804cccfff]
2020-06-26T11:07:36.658666114Z stdout F /opt/bitnami/mariadb/sbin/mysqld(+0x6a2bd5)[0x55b804ccdbd5]
2020-06-26T11:07:36.660035139Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x21)[0x55b804ccdc71]
2020-06-26T11:07:36.661358163Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1937)[0x55b804cbd037]
2020-06-26T11:07:36.662892992Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z10do_commandP3THD+0x14f)[0x55b804cbe13f]
2020-06-26T11:07:36.664116914Z stdout F /opt/bitnami/mariadb/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x204)[0x55b804d91bf4]
2020-06-26T11:07:36.665561941Z stdout F /opt/bitnami/mariadb/sbin/mysqld(handle_one_connection+0x34)[0x55b804d91ce4]
2020-06-26T11:07:36.68823396Z stdout F /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7fd5d6e2ffa3]
2020-06-26T11:07:36.708335831Z stdout F /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fd5d64604cf]
2020-06-26T11:07:36.708368531Z stdout F
2020-06-26T11:07:36.708379331Z stdout F Trying to get some variables.
2020-06-26T11:07:36.708421632Z stdout F Some pointers may be invalid and cause the dump to abort.
2020-06-26T11:07:36.720992564Z stdout F
2020-06-26T11:07:36.721003965Z stdout F The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
2020-06-26T11:07:36.721013965Z stdout F information that should help you find out what is causing the crash.
2020-06-26T11:07:36.721022965Z stdout F Writing a core file...
2020-06-26T11:07:36.721031265Z stdout F Working directory at /bitnami/mariadb/data
2020-06-26T11:07:36.721039965Z stdout F Resource Limits:
2020-06-26T11:07:36.721047565Z stdout F Limit Soft Limit Hard Limit Units
2020-06-26T11:07:36.721055065Z stdout F Max cpu time unlimited unlimited seconds
2020-06-26T11:07:36.721062966Z stdout F Max file size unlimited unlimited bytes
2020-06-26T11:07:36.721070566Z stdout F Max data size unlimited unlimited bytes
2020-06-26T11:07:36.721077866Z stdout F Max stack size 8388608 unlimited bytes
2020-06-26T11:07:36.721084966Z stdout F Max core file size unlimited unlimited bytes
2020-06-26T11:07:36.721091766Z stdout F Max resident set unlimited unlimited bytes
2020-06-26T11:07:36.721100566Z stdout F Max processes unlimited unlimited processes
2020-06-26T11:07:36.721108266Z stdout F Max open files 1048576 1048576 files
2020-06-26T11:07:36.721115367Z stdout F Max locked memory 16777216 16777216 bytes
2020-06-26T11:07:36.721122367Z stdout F Max address space unlimited unlimited bytes
2020-06-26T11:07:36.721129767Z stdout F Max file locks unlimited unlimited locks
2020-06-26T11:07:36.721138067Z stdout F Max pending signals 30457 30457 signals
2020-06-26T11:07:36.721145067Z stdout F Max msgqueue size 819200 819200 bytes
2020-06-26T11:07:36.721170368Z stdout F Max nice priority 0 0
2020-06-26T11:07:36.721177968Z stdout F Max realtime priority 0 0
2020-06-26T11:07:36.721185168Z stdout F Max realtime timeout unlimited unlimited us
2020-06-26T11:07:36.721192368Z stdout F Core pattern: |/usr/share/apport/apport %p %s %c %d %P %E
2020-06-26T11:07:36.721199568Z stdout F
2020-06-26T11:07:36.721207068Z stdout F Fatal signal 11 while backtracing
|
Initially i thought its a issue with NFS but its not bz other container didn't get the issue.
I could really user some help on this.
Thanks |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21724
|
| Posted: Thu Jul 02, 2020 2:45 am Post subject: Re: MariaDB crashing. zm and mythtv crashing. [solvedish] |
|
|
Welcome to the Gentoo forums.
| Sage wrote: | | I am getting this issue in mariadb container that looks like the issue mentioned above.... the container restarted bz of this issue: |
Gentoo does not install MariaDB in a container. What container software are you using, and how did you package the files from dev-db/mariadb into the container? | Sage wrote: | | Code: | | 2020-06-26T11:07:36.563812362Z stdout F /opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x55b805333479] |
|
This is a very strange path for mariadb. What is the output of emerge --info --verbose dev-db/mariadb? | Sage wrote: | | Initially i thought its a issue with NFS but its not bz other container didn't get the issue. |
Not which Bugzilla bug? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
