[HF]White scrie: ↑18 Oct 2023, 14:53
vers mysql nu e buna
intr-adevar, aici am incercat pe bsd9.2 cu mysql 5.5
dar am incercat si acum pe bsd 13.1 cu mysql 5.6 si tot nu merge
aici am alte erori:
Cod: Selectaţi tot
231018 19:27:21 mysqld_safe Logging to '/var/db/mysql/localhost.err'.
231018 19:27:21 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-10-18 19:27:21 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-10-18 19:27:21 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 792 ...
2023-10-18 19:27:21 792 [Note] Plugin 'FEDERATED' is disabled.
2023-10-18 19:27:21 792 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-10-18 19:27:21 792 [Note] InnoDB: The InnoDB memory heap is disabled
2023-10-18 19:27:21 792 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-10-18 19:27:21 792 [Note] InnoDB: Memory barrier is not used
2023-10-18 19:27:21 792 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-18 19:27:21 792 [Note] InnoDB: Not using CPU crc32 instructions
2023-10-18 19:27:21 792 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-10-18 19:27:21 792 [Note] InnoDB: Completed initialization of buffer pool
2023-10-18 19:27:21 792 [Note] InnoDB: Highest supported file format is Barracuda.
2023-10-18 19:27:21 792 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1595675 in the ib_logfiles!
2023-10-18 19:27:21 792 [Note] InnoDB: Database was not shutdown normally!
2023-10-18 19:27:21 792 [Note] InnoDB: Starting crash recovery.
2023-10-18 19:27:21 792 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-10-18 19:27:21 792 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/bbldah uses space ID: 1 at filepath: ./mysql/bbldah.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
2023-10-18 19:27:21 20e77000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
231018 19:27:21 mysqld_safe mysqld from pid file /var/db/mysql/localhost.pid ended
2023-10-18 19:34:48 967 [Note] Plugin 'FEDERATED' is disabled.
2023-10-18 19:34:48 967 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-10-18 19:34:48 967 [Note] InnoDB: The InnoDB memory heap is disabled
2023-10-18 19:34:48 967 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-10-18 19:34:48 967 [Note] InnoDB: Memory barrier is not used
2023-10-18 19:34:48 967 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-18 19:34:48 967 [Note] InnoDB: Not using CPU crc32 instructions
2023-10-18 19:34:48 967 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-10-18 19:34:48 967 [Note] InnoDB: Completed initialization of buffer pool
2023-10-18 19:34:48 967 [Note] InnoDB: Highest supported file format is Barracuda.
2023-10-18 19:34:48 967 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1595675 in the ib_logfiles!
2023-10-18 19:34:48 967 [Note] InnoDB: Database was not shutdown normally!
2023-10-18 19:34:48 967 [Note] InnoDB: Starting crash recovery.
2023-10-18 19:34:48 967 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-10-18 19:34:48 967 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/bbldah uses space ID: 1 at filepath: ./mysql/bbldah.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
2023-10-18 19:34:48 20e77000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
de 
de