[ZBX-17950] errors in the database, table history_uint Created: 2020 Jun 22  Updated: 2020 Jun 24  Resolved: 2020 Jun 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.0.1
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: ilia bakhterev Assignee: Zabbix Support Team
Resolution: Won't fix Votes: 0
Labels: database
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Hyper-V 2019
DELL R730 14CPU 2xIntel Xeon


Attachments: PNG File image-2020-06-22-12-47-57-079.png     PNG File image-2020-06-22-12-48-04-420.png     Text File memory_dump_mysql.txt    

 Description   

Steps to reproduce:

  1. After updating zabbix server to 5.0.1 version
  2. the database crashes after a while

Result:

 



 Comments   
Comment by ilia bakhterev [ 2020 Jun 22 ]

Impossible to dump the table history_uint

mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `history_uint` at row: 183743095 ]

6.09GiB 0:11:53 [8.75MiB/s] [ <=> ]

Comment by ilia bakhterev [ 2020 Jun 22 ]

the table suffered before upgrade to 5.0

Mariadb log says it's a bug

// заполнитель кода2020-06-22 15:50:52 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-06-22 15:50:52 0 [Note] Recovering after a crash using /var/lib/mysql/mariadb-bin
2020-06-22 15:50:52 0 [Note] Starting crash recovery...
2020-06-22 15:50:52 0 [Note] Crash recovery finished.
2020-06-22 15:50:52 0 [Note] Server socket created on IP: '::'.
2020-06-22 15:50:52 0 [Note] Reading of all Master_info entries succeeded
2020-06-22 15:50:52 0 [Note] Added new Master_info '' to hash table
2020-06-22 15:50:52 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.4.13-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2020-06-22 15:54:34 0 [Note] InnoDB: Buffer pool(s) load completed at 200622 15:54:34
2020-06-22 16:32:51 0x7f618c0af700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.13/storage/innobase/btr/btr0pcur.cc line 495
InnoDB: Failing assertion: btr_page_get_prev(next_page) == btr_pcur_get_block(cursor)->page.id.page_no()
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.
200622 16:32:51 [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-bugsWe 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.4.13-MariaDB-log
key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=7
max_threads=302
thread_count=14
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2387206 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x7f5c780009a8
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 = 0x7f618c0aecc0 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55cc6541f6ce]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55cc64eb5f7f]
/lib64/libpthread.so.0(+0xf630)[0x7f61c7f6d630]
/lib64/libc.so.6(gsignal+0x37)[0x7f61c623e387]
/lib64/libc.so.6(abort+0x148)[0x7f61c623fa78]
/usr/sbin/mysqld(+0x5b346a)[0x55cc64bb946a]
/usr/sbin/mysqld(+0xbca5ea)[0x55cc651d05ea]
/usr/sbin/mysqld(+0xb3dbfc)[0x55cc65143bfc]
/usr/sbin/mysqld(+0xa5e1d7)[0x55cc650641d7]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x81)[0x55cc64eba411]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1c)[0x55cc64fe8a6c]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x24f)[0x55cc64ce9ddf]
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xc73)[0x55cc64d0c223]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x55cc64d0c453]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x186)[0x55cc64d0a6a6]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1d7)[0x55cc64d0b217]
/usr/sbin/mysqld(+0x59fea3)[0x55cc64ba5ea3]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3832)[0x55cc64cb2552]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1fb)[0x55cc64cb78ab]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1957)[0x55cc64cb9a37]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x)[0x55cc64cbb049]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1fa)[0x55cc64d98bfa]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55cc64d98cdd]
/usr/sbin/mysqld(+0xdcb78d)[0x55cc653d178d]
/lib64/libpthread.so.0(+0x7ea5)[0x7f61c7f65ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f61c63068dd]Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f5c7800ff50): SELECT /*!40001 SQL_NO_CACHE */ `itemid`, `clock`, `value`, `ns` FROM `history_uint`
Connection ID (thread ID): 951
Status: NOT_KILLEDOptimizer 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=onThe 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.
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             95064                95064                processes 
Max open files            16364                16364                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       95064                95064                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
2020-06-22 16:33:02 0 [Note] InnoDB: Using Linux native AIO
2020-06-22 16:33:02 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-06-22 16:33:02 0 [Note] InnoDB: Uses event mutexes
2020-06-22 16:33:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-06-22 16:33:02 0 [Note] InnoDB: Number of pools: 1
2020-06-22 16:33:02 0 [Note] InnoDB: Using generic crc32 instructions
2020-06-22 16:33:02 0 [Note] InnoDB: Initializing buffer pool, total size = 18G, instances = 12, chunk size = 128M
2020-06-22 16:33:03 0 [Note] InnoDB: Completed initialization of buffer pool
2020-06-22 16:33:03 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-06-22 16:33:03 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2035467989327
2020-06-22 16:33:04 0 [Note] InnoDB: Last binlog file '/var/lib/mysql/mariadb-bin.000399', position 54658
2020-06-22 16:33:04 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-06-22 16:33:04 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-06-22 16:33:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-06-22 16:33:04 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-06-22 16:33:04 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-06-22 16:33:04 0 [Note] InnoDB: Waiting for purge to start
2020-06-22 16:33:04 0 [Note] InnoDB: 10.4.13 started; log sequence number 2035467989336; transaction id 769198619
2020-06-22 16:33:04 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-06-22 16:33:04 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-06-22 16:33:04 0 [Note] Recovering after a crash using /var/lib/mysql/mariadb-bin
2020-06-22 16:33:04 0 [Note] Starting crash recovery...
2020-06-22 16:33:04 0 [Note] Crash recovery finished.
2020-06-22 16:33:04 0 [Note] Server socket created on IP: '::'.
2020-06-22 16:33:04 0 [Note] Reading of all Master_info entries succeeded
2020-06-22 16:33:04 0 [Note] Added new Master_info '' to hash table
2020-06-22 16:33:04 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.4.13-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

 

Comment by Edgar Akhmetshin [ 2020 Jun 24 ]

Hello Ilia,

Usually such error means internal database structure problem with data and table space files. Please contact MariaDB support for further help or try to recover from backup first. Also please check MariaDB configuration, pay attention to the 'innodb_doublewrite', 'innodb_flush_log_at_trx_commit' and 'binlog*' related options. Also file system should not use writeback/nobarriers modes.

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Regards,
Edgar

Generated at Thu May 15 06:33:41 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.