same problem here, i got this error sir
2024-05-28T03:46:56.189839Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-05-28T03:46:56.189941Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2024-05-28T03:46:56.190006Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T03:46:56.190061Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.40-log) starting as process 3305 ...
2024-05-28T03:46:56.257057Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T03:46:56.257127Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T03:46:56.257142Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T03:46:56.257156Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T03:46:56.257169Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2024-05-28T03:46:56.257839Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T03:46:56.258110Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T03:46:56.260728Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2024-05-28T03:46:56.320398Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T03:46:56.334988Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T03:46:56.347057Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2024-05-28T03:46:56.355249Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3531694092
2024-05-28T03:46:56.355288Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3531694101
2024-05-28T03:46:56.355306Z 0 [Note] InnoDB: Database was not shutdown normally!
2024-05-28T03:46:56.355320Z 0 [Note] InnoDB: Starting crash recovery.
2024-05-28T03:46:56.390062Z 0 [Note] InnoDB: Last MySQL binlog file position 0 42020977, file name mysql-bin.000005
2024-05-28T03:47:55.521683Z 0 [ERROR] InnoDB: Cannot allocate 18446744073709551608 bytes of memory after 60 retries over 60 seconds. OS error: Cannot allocate memory (12). Check if you should increase the swap file or ulimits of your operating system. Note that on most 32-bit computers the process memory space is limited to 2 GB or 4 GB.
2024-05-28 03:47:55 0x14b65dfb8740 InnoDB: Assertion failure in thread 22773493368640 in file ut0ut.cc line 936
InnoDB: Failing assertion: !m_fatal
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:47:55 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=268435456
read_buffer_size=786432
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 572022 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x40)[0x55ab85e84be0]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x4f9)[0x55ab856af9f9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x14b65e511420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x14b65e00000b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x14b65dfdf859]
/www/server/mysql/bin/mysqld(+0x654688)[0x55ab85673688]
/www/server/mysql/bin/mysqld(+0x6549be)[0x55ab856739be]
/www/server/mysql/bin/mysqld(ZN12ut_allocatorIhE8allocateEmPKhPKcbb+0x201)[0x55ab85ec1661]
/www/server/mysql/bin/mysqld(Z23eval_node_alloc_val_bufPvm+0xc6)[0x55ab86117df6]
/www/server/mysql/bin/mysqld(+0xfb48cc)[0x55ab85fd38cc]
/www/server/mysql/bin/mysqld(+0xfb83c9)[0x55ab85fd73c9]
/www/server/mysql/bin/mysqld(Z12row_sel_stepP9que_thr_t+0x3f)[0x55ab85fd9f5f]
/www/server/mysql/bin/mysqld(Z15que_run_threadsP9que_thr_t+0x7a8)[0x55ab85f7dc08]
/www/server/mysql/bin/mysqld(Z12que_eval_sqlP11pars_info_tPKcmP5trx_t+0x82)[0x55ab85f7e672]
/www/server/mysql/bin/mysqld(Z27row_merge_drop_temp_indexesv+0x89)[0x55ab85fa86e9]
/www/server/mysql/bin/mysqld(Z29recv_recovery_rollback_activev+0x29)[0x55ab85f35ef9]
/www/server/mysql/bin/mysqld(Z34innobase_start_or_create_for_mysqlv+0x3f3f)[0x55ab8601800f]
/www/server/mysql/bin/mysqld(+0xeb5c3d)[0x55ab85ed4c3d]
/www/server/mysql/bin/mysqld(Z24ha_initialize_handlertonP13st_plugin_int+0x59)[0x55ab85700549]
/www/server/mysql/bin/mysqld(+0xc3df85)[0x55ab85c5cf85]
/www/server/mysql/bin/mysqld(Z40plugin_register_builtin_and_init_core_sePiPPc+0x1f4)[0x55ab85c5f404]
/www/server/mysql/bin/mysqld(Z11mysqld_mainiPPc+0xbae)[0x55ab856ab31e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x14b65dfe1083]
/www/server/mysql/bin/mysqld(start+0x2e)[0x55ab856a01de]
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.
2024-05-28T03:50:52.969309Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-05-28T03:50:52.969365Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2024-05-28T03:50:52.969399Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T03:50:52.969422Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.40-log) starting as process 4690 ...
2024-05-28T03:50:53.003160Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T03:50:53.003211Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T03:50:53.003218Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T03:50:53.003226Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T03:50:53.003233Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2024-05-28T03:50:53.003561Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T03:50:53.003689Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T03:50:53.005022Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2024-05-28T03:50:53.031974Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T03:50:53.039023Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T03:50:53.050252Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2024-05-28T03:50:53.054524Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3531694092
2024-05-28T03:50:53.054545Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3531694101
2024-05-28T03:50:53.054554Z 0 [Note] InnoDB: Database was not shutdown normally!
2024-05-28T03:50:53.054560Z 0 [Note] InnoDB: Starting crash recovery.
2024-05-28T03:50:53.279768Z 0 [Note] InnoDB: Last MySQL binlog file position 0 42020977, file name mysql-bin.000005
2024-05-28T03:51:52.398864Z 0 [ERROR] InnoDB: Cannot allocate 18446744073709551608 bytes of memory after 60 retries over 60 seconds. OS error: Cannot allocate memory (12). Check if you should increase the swap file or ulimits of your operating system. Note that on most 32-bit computers the process memory space is limited to 2 GB or 4 GB.
2024-05-28 03:51:52 0x1552e104c740 InnoDB: Assertion failure in thread 23445706688320 in file ut0ut.cc line 936
InnoDB: Failing assertion: !m_fatal
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:51:52 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=268435456
read_buffer_size=786432
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 572022 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x40)[0x55ef403aabe0]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x4f9)[0x55ef3fbd59f9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x1552e15a5420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x1552e109400b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x1552e1073859]
/www/server/mysql/bin/mysqld(+0x654688)[0x55ef3fb99688]
/www/server/mysql/bin/mysqld(+0x6549be)[0x55ef3fb999be]
/www/server/mysql/bin/mysqld(ZN12ut_allocatorIhE8allocateEmPKhPKcbb+0x201)[0x55ef403e7661]
/www/server/mysql/bin/mysqld(Z23eval_node_alloc_val_bufPvm+0xc6)[0x55ef4063ddf6]
/www/server/mysql/bin/mysqld(+0xfb48cc)[0x55ef404f98cc]
/www/server/mysql/bin/mysqld(+0xfb83c9)[0x55ef404fd3c9]
/www/server/mysql/bin/mysqld(Z12row_sel_stepP9que_thr_t+0x3f)[0x55ef404fff5f]
/www/server/mysql/bin/mysqld(Z15que_run_threadsP9que_thr_t+0x7a8)[0x55ef404a3c08]
/www/server/mysql/bin/mysqld(Z12que_eval_sqlP11pars_info_tPKcmP5trx_t+0x82)[0x55ef404a4672]
/www/server/mysql/bin/mysqld(Z27row_merge_drop_temp_indexesv+0x89)[0x55ef404ce6e9]
/www/server/mysql/bin/mysqld(Z29recv_recovery_rollback_activev+0x29)[0x55ef4045bef9]
/www/server/mysql/bin/mysqld(Z34innobase_start_or_create_for_mysqlv+0x3f3f)[0x55ef4053e00f]
/www/server/mysql/bin/mysqld(+0xeb5c3d)[0x55ef403fac3d]
/www/server/mysql/bin/mysqld(Z24ha_initialize_handlertonP13st_plugin_int+0x59)[0x55ef3fc26549]
/www/server/mysql/bin/mysqld(+0xc3df85)[0x55ef40182f85]
/www/server/mysql/bin/mysqld(Z40plugin_register_builtin_and_init_core_sePiPPc+0x1f4)[0x55ef40185404]
/www/server/mysql/bin/mysqld(Z11mysqld_mainiPPc+0xbae)[0x55ef3fbd131e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x1552e1075083]
/www/server/mysql/bin/mysqld(start+0x2e)[0x55ef3fbc61de]
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.
2024-05-28T03:54:13.093332Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-05-28T03:54:13.093421Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2024-05-28T03:54:13.093477Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-05-28T03:54:13.093526Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.40-log) starting as process 5751 ...
2024-05-28T03:54:13.151281Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-05-28T03:54:13.151343Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-05-28T03:54:13.151377Z 0 [Note] InnoDB: Uses event mutexes
2024-05-28T03:54:13.151390Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-05-28T03:54:13.151401Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2024-05-28T03:54:13.151937Z 0 [Note] InnoDB: Number of pools: 1
2024-05-28T03:54:13.152169Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-05-28T03:54:13.154437Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2024-05-28T03:54:13.203203Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-28T03:54:13.215118Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-05-28T03:54:13.226858Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2024-05-28T03:54:13.233861Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3531694092
2024-05-28T03:54:13.233893Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3531694101
2024-05-28T03:54:13.233909Z 0 [Note] InnoDB: Database was not shutdown normally!
2024-05-28T03:54:13.233921Z 0 [Note] InnoDB: Starting crash recovery.
2024-05-28T03:54:13.269912Z 0 [Note] InnoDB: Last MySQL binlog file position 0 42020977, file name mysql-bin.000005
2024-05-28T03:55:12.400717Z 0 [ERROR] InnoDB: Cannot allocate 18446744073709551608 bytes of memory after 60 retries over 60 seconds. OS error: Cannot allocate memory (12). Check if you should increase the swap file or ulimits of your operating system. Note that on most 32-bit computers the process memory space is limited to 2 GB or 4 GB.
2024-05-28 03:55:12 0x14c3841d7740 InnoDB: Assertion failure in thread 22829967701824 in file ut0ut.cc line 936
InnoDB: Failing assertion: !m_fatal
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:55:12 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=268435456
read_buffer_size=786432
max_used_connections=0
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 572022 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x40)[0x557a20833be0]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x4f9)[0x557a2005e9f9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x14c384730420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x14c38421f00b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x14c3841fe859]
/www/server/mysql/bin/mysqld(+0x654688)[0x557a20022688]
/www/server/mysql/bin/mysqld(+0x6549be)[0x557a200229be]
/www/server/mysql/bin/mysqld(ZN12ut_allocatorIhE8allocateEmPKhPKcbb+0x201)[0x557a20870661]
/www/server/mysql/bin/mysqld(Z23eval_node_alloc_val_bufPvm+0xc6)[0x557a20ac6df6]
/www/server/mysql/bin/mysqld(+0xfb48cc)[0x557a209828cc]
/www/server/mysql/bin/mysqld(+0xfb83c9)[0x557a209863c9]
/www/server/mysql/bin/mysqld(Z12row_sel_stepP9que_thr_t+0x3f)[0x557a20988f5f]
/www/server/mysql/bin/mysqld(Z15que_run_threadsP9que_thr_t+0x7a8)[0x557a2092cc08]
/www/server/mysql/bin/mysqld(Z12que_eval_sqlP11pars_info_tPKcmP5trx_t+0x82)[0x557a2092d672]
/www/server/mysql/bin/mysqld(Z27row_merge_drop_temp_indexesv+0x89)[0x557a209576e9]
/www/server/mysql/bin/mysqld(Z29recv_recovery_rollback_activev+0x29)[0x557a208e4ef9]
/www/server/mysql/bin/mysqld(Z34innobase_start_or_create_for_mysqlv+0x3f3f)[0x557a209c700f]
/www/server/mysql/bin/mysqld(+0xeb5c3d)[0x557a20883c3d]
/www/server/mysql/bin/mysqld(Z24ha_initialize_handlertonP13st_plugin_int+0x59)[0x557a200af549]
/www/server/mysql/bin/mysqld(+0xc3df85)[0x557a2060bf85]
/www/server/mysql/bin/mysqld(Z40plugin_register_builtin_and_init_core_sePiPPc+0x1f4)[0x557a2060e404]
/www/server/mysql/bin/mysqld(Z11mysqld_mainiPPc+0xbae)[0x557a2005a31e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x14c384200083]
/www/server/mysql/bin/mysqld(start+0x2e)[0x557a2004f1de]
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.