I run a stock trading bot, but Maria DB keeps dying. Even if I look at the error log, I do not know the cause. Please Help.
2021-02-20 15:10:46 0 [Note] InnoDB: innodb_page_size=32768 InnoDB: using atomic writes. 2021-02-20 15:10:46 0 [Note] InnoDB: Uses event mutexes 2021-02-20 15:10:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-02-20 15:10:46 0 [Note] InnoDB: Number of pools: 1 2021-02-20 15:10:46 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2021-02-20 15:10:46 0 [Note] InnoDB: Initializing buffer pool, total size = 4294967296, chunk size = 134217728 2021-02-20 15:10:46 0 [Note] InnoDB: Completed initialization of buffer pool 2021-02-20 15:10:47 0 [Note] InnoDB: 128 rollback segments are active. 2021-02-20 15:10:48 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-02-20 15:10:48 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-02-20 15:10:48 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB. 2021-02-20 15:10:48 0 [Note] InnoDB: 10.5.8 started; log sequence number 12396987587; transaction id 1414742 2021-02-20 15:10:48 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-02-20 15:10:48 0 [Note] Server socket created on IP: '::'. 2021-02-20 15:10:48 0 [Note] InnoDB: Loading buffer pool(s) from D:\Maria\data\ib_buffer_pool 2021-02-20 15:10:48 0 [Note] Reading of all Master_info entries succeeded 2021-02-20 15:10:48 0 [Note] Added new Master_info '' to hash table 2021-02-20 15:10:48 0 [Note] D:\Maria\bin\mysqld.exe: ready for connections. Version: '10.5.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution 2021-02-20 15:11:16 10 [Warning] InnoDB: Retry attempts for reading partial data failed. 2021-02-20 15:11:16 0 [Warning] InnoDB: Retry attempts for reading partial data failed. 2021-02-20 15:11:16 10 [ERROR] InnoDB: File (unknown): 'read' returned OS error 0. Cannot continue operation 2021-02-20 15210220 15:11:16 :[ERROR] mysqld got exception 0x80000003 ; 1This 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.
1To 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.
1Server version: 10.5.8-MariaDB 6key_buffer_size=134217728 read_buffer_size=131072 0max_used_connections=7 max_threads=65537 [thread_count=8 EIt is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136467 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
RROThread pointer: 0x22920500128 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... R] InnoDB: Operating system error number 203 in a file operation. 2021-02-20 15:11:16 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-02-20 15:11:16 0 [ERROR] InnoDB: File (unknown): 'read' returned OS error 403. Cannot continue operation
User contributions licensed under CC BY-SA 3.0