aaPanel_Kern

Just restarted the MYsql service from the aapanel got this updated error log... maybe this could help before i detele all my data.

2025-01-21T08:13:36.512426Z 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.
2025-01-21T08:13:36.512481Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2025-01-21T08:13:36.512506Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2025-01-21T08:13:36.512525Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 801509 ...
2025-01-21T08:13:36.623005Z 0 [Note] InnoDB: PUNCH HOLE support available
2025-01-21T08:13:36.623039Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2025-01-21T08:13:36.623043Z 0 [Note] InnoDB: Uses event mutexes
2025-01-21T08:13:36.623047Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2025-01-21T08:13:36.623050Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2025-01-21T08:13:36.623435Z 0 [Note] InnoDB: Number of pools: 1
2025-01-21T08:13:36.623527Z 0 [Note] InnoDB: Using CPU crc32 instructions
2025-01-21T08:13:36.624670Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2025-01-21T08:13:36.862591Z 0 [Note] InnoDB: Completed initialization of buffer pool
2025-01-21T08:13:36.918189Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2025-01-21T08:13:36.930052Z 0 [Note] InnoDB: Setting log file /www/server/data/ib_logfile101 size to 1024 MB
2025-01-21T08:13:36.930606Z 0 [Note] InnoDB: Progress in MB:
100 200 300 400 500 600 700 800 900 1000
2025-01-21T08:13:38.091388Z 0 [Note] InnoDB: Setting log file /www/server/data/ib_logfile1 size to 1024 MB
2025-01-21T08:13:38.092441Z 0 [Note] InnoDB: Progress in MB:
100 200 300 400 500 600 700 800 900 1000
2025-01-21T08:13:43.073732Z 0 [Note] InnoDB: Renaming log file /www/server/data/ib_logfile101 to /www/server/data/ib_logfile0
2025-01-21T08:13:43.073873Z 0 [Warning] InnoDB: New log files created, LSN=1602662
2025-01-21T08:13:43.082787Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2025-01-21T08:13:43.138891Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1603084
2025-01-21T08:13:43.138940Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1603093
2025-01-21T08:13:43.138952Z 0 [Note] InnoDB: Database was not shutdown normally!
2025-01-21T08:13:43.138962Z 0 [Note] InnoDB: Starting crash recovery.
2025-01-21T08:13:43.156483Z 0 [Note] InnoDB: pre-5.7.2 rseg: 1 holds data to be purged. History length: 1. Recommend slow shutdown with innodb_fast_shutdown=0 and restart
2025-01-21T08:13:43.156548Z 0 [Note] InnoDB: pre-5.7.2 rseg: 2 holds data to be purged. History length: 1. Recommend slow shutdown with innodb_fast_shutdown=0 and restart
2025-01-21T08:13:43.345897Z 0 [Note] InnoDB: Successfully reset 30 pre-5.7.2 rseg slots.
2025-01-21T08:13:43.347134Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2025-01-21T08:13:43.347149Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-01-21T08:13:43.347216Z 0 [Note] InnoDB: Setting file '/www/server/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-01-21T08:13:43.361801Z 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB.
2025-01-21T08:13:43.362476Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2025-01-21T08:13:43.362494Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2025-01-21T08:13:43.362754Z 0 [Note] InnoDB: Waiting for purge to start
08:13:43 UTC - mysqld got signal 11 ;
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=1073741824
read_buffer_size=16777216
max_used_connections=0
max_threads=500
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 = 17439275 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x145db0000b60
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...

      aaP_houseofservers23

      My config file for your reference
      [client]
      #password = your_password
      port = 3306
      socket = /tmp/mysql.sock

      [mysqld]
      port = 3306
      socket = /tmp/mysql.sock
      datadir = /www/server/data/mysql
      skip-external-locking
      performance_schema_max_table_instances=400
      table_definition_cache=400
      table_open_cache = 4096
      key_buffer_size = 1024M
      max_allowed_packet = 1M
      table_open_cache = 4096
      sort_buffer_size = 16M
      net_buffer_length = 8K
      read_buffer_size = 16M
      read_rnd_buffer_size = 512K
      myisam_sort_buffer_size = 256M
      thread_cache_size = 512
      query_cache_size = 512M
      tmp_table_size = 512M
      sql-mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

      explicit_defaults_for_timestamp = true
      #skip-networking
      max_connections = 500
      max_connect_errors = 100
      open_files_limit = 65535

      log-bin=mysql-bin
      binlog_format=mixed
      server-id = 1
      expire_logs_days = 10
      #early-plugin-load = ""

      #loose-innodb-trx=0
      #loose-innodb-locks=0
      #loose-innodb-lock-waits=0
      #loose-innodb-cmp=0
      #loose-innodb-cmp-per-index=0
      #loose-innodb-cmp-per-index-reset=0
      #loose-innodb-cmp-reset=0
      #loose-innodb-cmpmem=0
      #loose-innodb-cmpmem-reset=0
      #loose-innodb-buffer-page=0
      #loose-innodb-buffer-page-lru=0
      #loose-innodb-buffer-pool-stats=0
      #loose-innodb-metrics=0
      #loose-innodb-ft-default-stopword=0
      #loose-innodb-ft-inserted=0
      #loose-innodb-ft-deleted=0
      #loose-innodb-ft-being-deleted=0
      #loose-innodb-ft-config=0
      #loose-innodb-ft-index-cache=0
      #loose-innodb-ft-index-table=0
      #loose-innodb-sys-tables=0
      #loose-innodb-sys-tablestats=0
      #loose-innodb-sys-indexes=0
      #loose-innodb-sys-columns=0
      #loose-innodb-sys-fields=0
      #loose-innodb-sys-foreign=0
      #loose-innodb-sys-foreign-cols=0

      default_storage_engine = InnoDB
      innodb_data_home_dir = /www/server/data/mysql
      innodb_data_file_path = ibdata1:10M:autoextend
      innodb_log_group_home_dir = /www/server/data/mysql
      innodb_buffer_pool_size = 4096M
      innodb_log_file_size = 1024M
      innodb_log_buffer_size = 8M
      innodb_flush_log_at_trx_commit = 1
      innodb_lock_wait_timeout = 50

      [mysqldump]
      quick
      max_allowed_packet = 16M

      [mysql]
      no-auto-rehash

      [myisamchk]
      key_buffer_size = 1024M
      sort_buffer_size = 16M
      read_buffer = 2M
      write_buffer = 2M

      [mysqlhotcopy]
      interactive-timeout

          Hello, which files did you delete specifically? It is recommended that you find a professional company to help you deal with database problems.

          aaP_houseofservers23