T18:02:01.345281Z 0 InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo T18:02:01.338117Z 0 InnoDB: Database was not shutdown normally! T18:02:01.335810Z 0 InnoDB: Highest supported file format is Barracuda. T18:02:01.323919Z 0 InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. T18:02:01.321980Z 0 InnoDB: Completed initialization of buffer pool T18:02:01.314672Z 0 InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M T18:02:01.312603Z 0 InnoDB: GCC builtin _atomic_thread_fence() is used for memory barrier T18:02:01.312593Z 0 InnoDB: Mutexes and rw_locks use GCC atomic builtins T18:02:01.312557Z 0 InnoDB: PUNCH HOLE support available Please use -explicit_defaults_for_timestamp server option (see documentation for more details). T18:02:01.309162Z 0 TIMESTAMP with implicit DEFAULT value is deprecated. Contact your system administrator if the service does not automagically recover.And here is some part of log mysqld.log: (XID q58dv7) The “mysql” service failed to start.įeb 24 14:36:15 systemd: Starting MySQL Server. …failed.Ĭpanel::Exception::Services::StartError Service Status This should resolve any errors that stem from an outdated MySQL configuration file. The system has attempted to auto-update your MySQL configuration file for your MySQL version. …Unrecognized configuration options may have caused the MySQL startup errors. Waiting for “mysql” to start ………Unrecognized configuration options may have caused the MySQL startup errors.
0 kommentar(er)
