JonGeN

tlthings.net

Já resolvi obrigado aos que me tentaram ajudar

Boas como diz o titulo alguem me pode explicar como mudo o item_proto e o mob_proto txt para sql eu tenho os itens traduzidos no cliente mas quando mudo no navicat e dou reload p ou reboot os nomes que mudei voltam ao nome anterior

Qual é a lib que tens em falta?

Alguem me consegue ajudar com este erro o que está em baixo é o .err do mysql 180224 16:49:40 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql 2018-02-24 16:49:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2018-02-24 16:49:40 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2018-02-24 16:49:40 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 673 ... 2018-02-24 16:49:40 673 [Note] Plugin 'FEDERATED' is disabled. 2018-02-24 16:49:40 673 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-02-24 16:49:40 673 [Note] InnoDB: The InnoDB memory heap is disabled 2018-02-24 16:49:40 673 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-02-24 16:49:40 673 [Note] InnoDB: Memory barrier is not used 2018-02-24 16:49:40 673 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-02-24 16:49:40 673 [Note] InnoDB: Using CPU crc32 instructions 2018-02-24 16:49:40 673 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2018-02-24 16:49:40 673 [Note] InnoDB: Completed initialization of buffer pool 2018-02-24 16:49:40 673 [Note] InnoDB: Highest supported file format is Barracuda. 2018-02-24 16:49:40 673 [Note] InnoDB: The log sequence numbers 1669497 and 1669497 in ibdata files do not match the log sequence number 1669507 in the ib_logfiles! 2018-02-24 16:49:40 673 [Note] InnoDB: Database was not shutdown normally! 2018-02-24 16:49:40 673 [Note] InnoDB: Starting crash recovery. 2018-02-24 16:49:40 673 [Note] InnoDB: Reading tablespace information from the .ibd files... 2018-02-24 16:49:40 673 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace log/okay_event which uses space ID: 5 at filepath: ./log/okay_event.ibd 2018-02-24 16:49:40 802807400 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 ./log/okay_event.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. 180224 16:49:40 mysqld_safe mysqld from pid file /var/db/mysql/testes1.pid ended Já consegui resolver

Não está: mysql is not running. foi isto que me responderam :It seems your "database sources" and mysql server have different versions, thus there are some conflicts . O que posso fazer?

Alguem me sabe dizer como posso resolver este erro? uso o FreeBSD 9.3 MT2 x64 ja tentei com o FreeBSD 11.0 x64 e com o 10.1 x64 mas da-me sempre erro já tentei usar outra mysql mas o erro continua se alguem me poder ajudar agradecia, este é o erro: mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)failed, retrying in 5 secondsmysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

Já tive o mesmo problema não sei ao certo o que foi mas resolvi ao meter o Backup da db