financial-freedom
financial-freedom copied to clipboard
Published
20 hours ago •
serversideup
serversideup
Mariadb error
Issue description
During migration, an error occurred.
Environment
- What's My Browser Support link: https://www.whatsmybrowser.org/b/6MZN7
Steps to reproduce the issue
- run
php artisan migrate
What is expected?
Finished migrating
Link to where issue can be reproduced
Additional details / screenshots
2022-08-09 12:56:48 6 [ERROR] InnoDB: preallocating 114688 bytes for file ./financial_freedom/sessions.ibd failed with error 2
2022-08-09 12:56:48 0x7fd26c0cd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.16/storage/innobase/fil/fil0fil.cc line 620
InnoDB: Failing assertion: fsize != os_offset_t(-1)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
220809 12:56:48 [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 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.5.16-MariaDB-1:10.5.16+maria~focal
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=2
max_threads=153
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467873 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fd24c00de08
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 = 0x7fd26c0ccd58 thread_stack 0x49000
Printing to addr2line failed
mysqld(my_print_stacktrace+0x32)[0x5628bb87e182]
mysqld(handle_fatal_signal+0x485)[0x5628bb2c2f35]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7fd2830ed420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fd282bf100b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fd282bd0859]
mysqld(+0x643bd5)[0x5628baf79bd5]
mysqld(+0x656220)[0x5628baf8c220]
mysqld(+0x6564cd)[0x5628baf8c4cd]
mysqld(+0x65953b)[0x5628baf8f53b]
mysqld(+0x659889)[0x5628baf8f889]
mysqld(+0xe7fdc0)[0x5628bb7b5dc0]
mysqld(+0xdd94d4)[0x5628bb70f4d4]
mysqld(+0xe2fc4d)[0x5628bb765c4d]
mysqld(+0xe30392)[0x5628bb766392]
mysqld(+0xd33e28)[0x5628bb669e28]
mysqld(+0xcb2a61)[0x5628bb5e8a61]
mysqld(+0xcbb5a5)[0x5628bb5f15a5]
mysqld(+0xcc0f90)[0x5628bb5f6f90]
mysqld(+0x81785c)[0x5628bb14d85c]
mysqld(_Z17mysql_alter_tableP3THDPK25st_mysql_const_lex_stringS3_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderbb+0x3a87)[0x5628bb15a877]
mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x371)[0x5628bb1bbf31]
mysqld(_Z21mysql_execute_commandP3THD+0x10e6)[0x5628bb0b09f6]
mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x465)[0x5628bb0c52c5]
mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0xa1)[0x5628bb0c54b1]
mysqld(+0x7903a5)[0x5628bb0c63a5]
mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x30)[0x5628bb0c65e0]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x22c7)[0x5628bb0ad107]
mysqld(_Z10do_commandP3THD+0x123)[0x5628bb0aebc3]
mysqld(_Z24do_handle_one_connectionP7CONNECTb+0x421)[0x5628bb1b7281]
mysqld(handle_one_connection+0x5d)[0x5628bb1b76fd]
mysqld(+0xbea77f)[0x5628bb52077f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7fd2830e1609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7fd282ccd133]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fd24c024088): alter table `sessions` add index `sessions_user_id_index`(`user_id`)
Connection ID (thread ID): 6
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
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 unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 83968000 83968000 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 15708 15708 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
Fatal signal 11 while backtracing
