Hi.
Our ticketing system osTicket (version: 1.10) has been running for quite some time now and we haven't encountered any issues at all until today. For some reason, all the users can no longer access all the attachments. Whenever they click on any of the attachments, the database crashes.
I tried executing several commands on table ost_file_chunk, the database crashes. I even tried deleting and renaming it all together, same result.
Below is the error message I got after executing alter table from the shell:
`2019-09-18 15:40:39 eec InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-09-18 15:40:39 3820 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-09-18 15:40:39 3820 [Note] InnoDB: The InnoDB memory heap is disabled
2019-09-18 15:40:39 3820 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-09-18 15:40:39 3820 [Note] InnoDB: Memory barrier is not used
2019-09-18 15:40:39 3820 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-09-18 15:40:39 3820 [Note] InnoDB: Using generic crc32 instructions
2019-09-18 15:40:39 3820 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-09-18 15:40:39 3820 [Note] InnoDB: Completed initialization of buffer pool
2019-09-18 15:40:39 3820 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-18 15:40:39 3820 [Note] InnoDB: The log sequence numbers 17316322882 and 17316322882 in ibdata files do not match the log sequence number 17316634487 in the ib_logfiles!
2019-09-18 15:40:39 3820 [Note] InnoDB: Database was not shutdown normally!
2019-09-18 15:40:39 3820 [Note] InnoDB: Starting crash recovery.
2019-09-18 15:40:39 3820 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-09-18 15:40:39 3820 [Note] InnoDB: Restoring possible half-written data pages
2019-09-18 15:40:39 3820 [Note] InnoDB: from the doublewrite buffer...
2019-09-18 15:40:40 3820 [Note] InnoDB: 128 rollback segment(s) are active.
2019-09-18 15:40:40 3820 [Note] InnoDB: Waiting for purge to start
2019-09-18 15:40:40 3820 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 17316634487
2019-09-18 15:40:40 4528 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-09-18 15:40:40 3820 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-18 15:40:40 3820 [Note] Server socket created on IP: '::'.
2019-09-18 15:40:40 3820 [Note] F:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
InnoDB: Error: trying to access page number 11584 in space 54,
InnoDB: space name fbosticket/ost_file_chunk,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2019-09-18 15:40:51 11e8 InnoDB: Assertion failure in thread 4584 in file fil0fil.cc line 5866
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190918 15:40:51 [ERROR] mysqld got exception 0x80000003 ;
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.1.13-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=1001
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x4df0028
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_mb_ctype_mb()
mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ()
mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ()
mysqld.exe!?functype@Item_func_dyncol_create@@ube?AW4Functype@Item_func@@XZ()
mysqld.exe!?functype@Item_func_dyncol_create@@ube?AW4Functype@Item_func@@XZ()
mysqld.exe!?functype@Item_func_dyncol_create@@ube?AW4Functype@Item_func@@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!?my_ulonglong2double@@YAN_K@Z()
mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHI@Z()
mysqld.exe!?open_table_from_share@@YA?AW4open_frm_error@@PAVTHD@@PAUTABLE_SHARE@@PBDIIIPAUTABLE@@N@Z()
mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_context@@@Z()
mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ()
mysqld.exe!?open_tables@@YA_NPAVTHD@@ABUDDL_options_st@@PAPAUTABLE_LIST@@PAIIPAVPrelocking_strategy@@@Z()
mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUHA_CREATE_INFO@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@N@Z()
mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
mysqld.exe!?threadpool_process_request@@YAHPAVTHD@@@Z()
mysqld.exe!?tp_end@@YAXXZ()
KERNEL32.DLL!GetAtomNameW()
ntdll.dll!TpCancelAsyncIoOperation()
ntdll.dll!TpCancelAsyncIoOperation()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x4df77d0): alter table ost_file_chunk rename to ost_file_chunk_old
Connection ID (thread ID): 2
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=off,table_elimination=on,extended_keys=on,exists_to_in=on
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.
`
Hope anybody have any solutions on this. Thanks in advance.