• Support

  • MySQLd service failed to start (after restarting server)

Hi, please describe your problem in detail.
If you delete the prompted directory by mistake, please find a professional company to help you restore important data
If there is no database, you can reinstall mysql

aaP_olaniyi

    Please check whether the mysql configuration file has changed the database storage directory?

    aaP_olaniyi

      Hello, please check if there are any files in this directory?
      ls -l /www/server/data

      aaP_olaniyi

        5 days later

        i have reintsall aapanel

        pls how can i stop this its genereting itself and its eating up my storage

          aaP_olaniyi
          mysql8 close binary log
          Added in the configuration：
          skip-log-bin=1
          #log-bin=mysql-bin
          #binlog_format=mixed
          expire_logs_days=3
          binlog_expire_logs_seconds = 600000

              Hello, what is your mysql version? Do you want to configure automatic deletion of configuration? Do you want to restart mysql after configuration?

              aaP_olaniyi

              • jaac replied to this.
                  13 days later

                  aaPanel_Kern got error again 🙁

                  2023-09-26T04:02:51.321754Z 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
                  2023-09-26T04:02:51.321912Z 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.
                  2023-09-26T04:02:51.321915Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
                  2023-09-26T04:02:51.321939Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
                  2023-09-26T04:02:51.321963Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.43-log) starting as process 9222 ...
                  2023-09-26T04:02:51.332264Z 0 [Note] InnoDB: PUNCH HOLE support available
                  2023-09-26T04:02:51.332304Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
                  2023-09-26T04:02:51.332307Z 0 [Note] InnoDB: Uses event mutexes
                  2023-09-26T04:02:51.332310Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
                  2023-09-26T04:02:51.332313Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
                  2023-09-26T04:02:51.332446Z 0 [Note] InnoDB: Number of pools: 1

                  2023-09-26T04:02:51.332517Z 0 [Note] InnoDB: Using CPU crc32 instructions

                  2023-09-26T04:02:51.412394Z 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB.
                  2023-09-26T04:02:51.413321Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
                  2023-09-26T04:02:51.413333Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
                  2023-09-26T04:02:51.413746Z 0 [Note] InnoDB: Waiting for purge to start
                  2023-09-26T04:02:51.463949Z 0 [Note] InnoDB: 5.7.43 started; log sequence number 1876267808
                  2023-09-26T04:02:51.463973Z 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
                  2023-09-26T04:02:51.464187Z 0 [Note] InnoDB: Loading buffer pool(s) from /www/server/data/ib_buffer_pool
                  2023-09-26T04:02:51.464376Z 0 [Note] Plugin 'FEDERATED' is disabled.
                  2023-09-26T04:02:51.464452Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230926 4:02:51
                  mysqld: File './mysql-bin.000188' not found (Errcode: 2 - No such file or directory)
                  2023-09-26T04:02:51.465220Z 0 [ERROR] Failed to open log (file './mysql-bin.000188', errno 2)
                  2023-09-26T04:02:51.465227Z 0 [ERROR] Could not open log file
                  2023-09-26T04:02:51.465237Z 0 [ERROR] Can't init tc log
                  2023-09-26T04:02:51.465242Z 0 [ERROR] Aborting

                  2023-09-26T04:02:51.465270Z 0 [Note] Binlog end
                  2023-09-26T04:02:51.465323Z 0 [Note] Shutting down plugin 'ngram'
                  2023-09-26T04:02:51.465329Z 0 [Note] Shutting down plugin 'partition'
                  2023-09-26T04:02:51.465334Z 0 [Note] Shutting down plugin 'BLACKHOLE'
                  2023-09-26T04:02:51.465338Z 0 [Note] Shutting down plugin 'ARCHIVE'
                  2023-09-26T04:02:51.465343Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
                  2023-09-26T04:02:51.465446Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
                  2023-09-26T04:02:51.465452Z 0 [Note] Shutting down plugin 'MyISAM'
                  2023-09-26T04:02:51.465467Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'

                      jaac
                      Try to delete ./mysql-bin.000188 from the content of this /www/server/data/mysql-bin.index file, and then restart mysql. Can it be solved?
                      It can be operated in the "File" interface of the panel
                      cp /www/server/data/mysql-bin.index /www/server/data/mysql-bin.index_
                      /etc/init.d/mysqld restart

                      Execute the command Check out what mysql-bin files are in your directory
                      ls /www/server/data/mysql-bin*

                      • jaac replied to this.