Estou com problemas no meu dedicado, vi me obrigado a dar reboot e manter o servidor desligado para trocar as senhas da base de dados devido a expulsão de um membro da equipa.
O que acontece é que esse mesmo membro é que tratava de iniciar o servidor.
Eu já tentei um pouco de tudo e não tive sucesso a iniciar o servidor.
Tentei reiniciar o mysql, tentei dar stop depois start e tentei dar logo start.
Erro ao dar Restart/Stop no mysql:
Spoiler
service mysql-server start
/etc/rc.conf: apache22_enable: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: apache22_enable: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
Starting mysql.
Erro ao iniciar o Servidor:
Spoiler
****************** Starting LibGame ******************
**** Made by iMer (www.imer.cc).
**** Special Thanks to Nova & tim66613
**** Game Revision is 34083
hacking out LD_PRELOAD from environ[0]
Hook @0x80ccf80
Hook @0x81956b0
**** Hooking Phase completed!
**** Done initializing!
PUBLIC_IP: x.xx.xx.xxx interface em0 < Onde está os x.xx.xx.xxx é o ip da maquina so substitui ao colar o código de erro aqui >
HOSTNAME: channel1_core1
mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
cannot open direct sql connection to host: localhost user: mt2 db: common
cannot start server while no common sql connected
failed, retrying in 5 secondsmysql_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)
failed, retrying in 5 secondsmysql_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)
failed, retrying in 5 secondsmysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
O que aparece ao dar o comando ps:
Spoiler
# ps
PID TT STAT TIME COMMAND
790 v0- S 0:00.00 sh /etc/rc autoboot
791 v0- S 0:00.00 logger -p daemon.notice -t fsck
792 v0- S 0:00.00 sleep 60
797 v0 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv0
798 v1 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv1
799 v2 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv2
800 v3 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv3
801 v4 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv4
802 v5 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv5
803 v6 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv6
804 v7 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv7
808 0 Ss 0:00.02 -csh (csh)
811 0 R+ 0:00.00 ps
Log error BD:
Spoiler
170125 01:23:37 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:23:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:23:38 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:23:38 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1433 ...
2017-01-25 01:23:38 1433 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:23:38 1433 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:23:38 1433 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:23:38 1433 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:23:38 1433 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:23:38 1433 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:23:38 1433 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:23:38 1433 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:23:38 1433 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:23:38 1433 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:23:38 1433 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:23:38 1433 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:23:38 1433 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:23:38 1433 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:23:38 1433 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:23:38 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:23:38 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:28:54 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:28:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:28:55 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:28:55 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 694 ...
2017-01-25 01:28:55 694 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:28:55 694 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:28:55 694 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:28:55 694 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:28:55 694 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:28:55 694 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:28:55 694 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:28:55 694 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:28:55 694 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:28:55 694 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:28:55 694 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:28:55 694 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:28:55 694 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:28:55 694 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:28:55 694 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:28:55 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:28:55 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:31:43 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:31:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:31:43 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:31:43 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 961 ...
2017-01-25 01:31:43 961 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:31:43 961 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:31:43 961 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:31:43 961 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:31:43 961 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:31:43 961 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:31:43 961 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:31:43 961 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:31:43 961 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:31:44 961 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:31:44 961 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:31:44 961 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:31:44 961 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:31:44 961 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:31:44 961 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:31:44 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:31:44 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:34:09 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:34:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:34:10 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:34:10 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1131 ...
2017-01-25 01:34:10 1131 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:34:10 1131 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:34:10 1131 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:34:10 1131 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:34:10 1131 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:34:10 1131 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:34:10 1131 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:34:10 1131 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:34:10 1131 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:34:10 1131 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:34:10 1131 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:34:10 1131 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:34:10 1131 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:34:10 1131 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:34:10 1131 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:34:10 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:34:10 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:48:29 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:48:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:48:29 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:48:29 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1483 ...
2017-01-25 01:48:29 1483 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:48:29 1483 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:48:29 1483 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:48:29 1483 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:48:29 1483 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:48:29 1483 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:48:29 1483 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:48:29 1483 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:48:29 1483 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:48:29 1483 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:48:29 1483 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:48:29 1483 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:48:29 1483 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:48:29 1483 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:48:29 1483 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:48:29 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:48:30 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:48:42 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:48:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:48:43 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:48:43 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1622 ...
2017-01-25 01:48:43 1622 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:48:43 1622 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:48:43 1622 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:48:43 1622 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:48:43 1622 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:48:43 1622 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:48:43 1622 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:48:43 1622 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:48:43 1622 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:48:43 1622 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:48:43 1622 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:48:43 1622 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:48:43 1622 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:48:43 1622 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:48:43 1622 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:48:43 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:48:43 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:52:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:52:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:52:48 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:52:48 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 690 ...
2017-01-25 01:52:48 690 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:52:48 690 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:52:48 690 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:52:48 690 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:52:48 690 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:52:48 690 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:52:48 690 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:52:48 690 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:52:49 690 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:52:49 690 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:52:49 690 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:52:49 690 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:52:49 690 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:52:49 690 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:52:49 690 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:52:49 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:52:49 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
Será que estou a iniciar o Mysql mal?
Será que tenho de dar outros comandos antes de iniciar o servidor?
Não queria mesmo dar reseet, não quero que os jogadores percam os seus itens devido a estupidez do ex membro da equipa...
Se for preciso até pago a quem me ajudar a resolver isto...
Olá,
Estou com problemas no meu dedicado, vi me obrigado a dar reboot e manter o servidor desligado para trocar as senhas da base de dados devido a expulsão de um membro da equipa.
O que acontece é que esse mesmo membro é que tratava de iniciar o servidor.
Eu já tentei um pouco de tudo e não tive sucesso a iniciar o servidor.
Tentei reiniciar o mysql, tentei dar stop depois start e tentei dar logo start.
Erro ao dar Restart/Stop no mysql:
service mysql-server start
/etc/rc.conf: apache22_enable: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: apache22_enable: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=”YES”‘: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
/etc/rc.conf: ‘apache22_enable=yes: not found
Starting mysql.
Erro ao iniciar o Servidor:
****************** Starting LibGame ******************
**** Made by iMer (www.imer.cc).
**** Special Thanks to Nova & tim66613
**** Game Revision is 34083
hacking out LD_PRELOAD from environ[0]
Hook @0x80ccf80
Hook @0x81956b0
**** Hooking Phase completed!
**** Done initializing!
PUBLIC_IP: x.xx.xx.xxx interface em0 < Onde está os x.xx.xx.xxx é o ip da maquina so substitui ao colar o código de erro aqui >
HOSTNAME: channel1_core1
mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
cannot open direct sql connection to host: localhost user: mt2 db: common
cannot start server while no common sql connected
failed, retrying in 5 secondsmysql_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)
failed, retrying in 5 secondsmysql_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)
failed, retrying in 5 secondsmysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
O que aparece ao dar o comando ps:
# ps
PID TT STAT TIME COMMAND
790 v0- S 0:00.00 sh /etc/rc autoboot
791 v0- S 0:00.00 logger -p daemon.notice -t fsck
792 v0- S 0:00.00 sleep 60
797 v0 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv0
798 v1 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv1
799 v2 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv2
800 v3 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv3
801 v4 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv4
802 v5 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv5
803 v6 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv6
804 v7 Ss+ 0:00.00 /usr/libexec/getty Pc ttyv7
808 0 Ss 0:00.02 -csh (csh)
811 0 R+ 0:00.00 ps
Log error BD:
170125 01:23:37 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:23:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:23:38 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:23:38 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1433 ...
2017-01-25 01:23:38 1433 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:23:38 1433 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:23:38 1433 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:23:38 1433 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:23:38 1433 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:23:38 1433 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:23:38 1433 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:23:38 1433 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:23:38 1433 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:23:38 1433 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:23:38 1433 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:23:38 1433 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:23:38 1433 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:23:38 1433 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:23:38 1433 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:23:38 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:23:38 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:28:54 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:28:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:28:55 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:28:55 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 694 ...
2017-01-25 01:28:55 694 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:28:55 694 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:28:55 694 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:28:55 694 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:28:55 694 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:28:55 694 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:28:55 694 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:28:55 694 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:28:55 694 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:28:55 694 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:28:55 694 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:28:55 694 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:28:55 694 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:28:55 694 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:28:55 694 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:28:55 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:28:55 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:31:43 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:31:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:31:43 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:31:43 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 961 ...
2017-01-25 01:31:43 961 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:31:43 961 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:31:43 961 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:31:43 961 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:31:43 961 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:31:43 961 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:31:43 961 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:31:43 961 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:31:43 961 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:31:44 961 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:31:44 961 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:31:44 961 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:31:44 961 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:31:44 961 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:31:44 961 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:31:44 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:31:44 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:34:09 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:34:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:34:10 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:34:10 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1131 ...
2017-01-25 01:34:10 1131 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:34:10 1131 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:34:10 1131 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:34:10 1131 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:34:10 1131 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:34:10 1131 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:34:10 1131 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:34:10 1131 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:34:10 1131 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:34:10 1131 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:34:10 1131 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:34:10 1131 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:34:10 1131 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:34:10 1131 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:34:10 1131 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:34:10 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:34:10 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:48:29 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:48:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:48:29 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:48:29 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1483 ...
2017-01-25 01:48:29 1483 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:48:29 1483 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:48:29 1483 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:48:29 1483 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:48:29 1483 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:48:29 1483 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:48:29 1483 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:48:29 1483 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:48:29 1483 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:48:29 1483 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:48:29 1483 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:48:29 1483 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:48:29 1483 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:48:29 1483 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:48:29 1483 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:48:29 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:48:30 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:48:42 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:48:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:48:43 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:48:43 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 1622 ...
2017-01-25 01:48:43 1622 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:48:43 1622 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:48:43 1622 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:48:43 1622 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:48:43 1622 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:48:43 1622 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:48:43 1622 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:48:43 1622 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:48:43 1622 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:48:43 1622 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:48:43 1622 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:48:43 1622 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:48:43 1622 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:48:43 1622 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:48:43 1622 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:48:43 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:48:43 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
170125 01:52:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-25 01:52:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-25 01:52:48 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-25 01:52:48 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 690 ...
2017-01-25 01:52:48 690 [Note] Plugin 'FEDERATED' is disabled.
2017-01-25 01:52:48 690 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-25 01:52:48 690 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 01:52:48 690 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 01:52:48 690 [Note] InnoDB: Memory barrier is not used
2017-01-25 01:52:48 690 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-25 01:52:48 690 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-25 01:52:48 690 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-25 01:52:49 690 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 01:52:49 690 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-25 01:52:49 690 [Note] InnoDB: The log sequence numbers 2038378 and 2038378 in ibdata files do not match the log sequence number 2038388 in the ib_logfiles!
2017-01-25 01:52:49 690 [Note] InnoDB: Database was not shutdown normally!
2017-01-25 01:52:49 690 [Note] InnoDB: Starting crash recovery.
2017-01-25 01:52:49 690 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-25 01:52:49 690 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd. Cannot open tablespace itemshop/categorii_shop which uses space ID: 1 at filepath: ./itemshop/categorii_shop.ibd
2017-01-25 01:52:49 802c06400 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 ./itemshop/categorii_shop.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.
170125 01:52:49 mysqld_safe mysqld from pid file /var/db/mysql/metin2privado.pid ended
Será que estou a iniciar o Mysql mal?
Será que tenho de dar outros comandos antes de iniciar o servidor?
Não queria mesmo dar reseet, não quero que os jogadores percam os seus itens devido a estupidez do ex membro da equipa...
Se for preciso até pago a quem me ajudar a resolver isto...
Cumpz.
Share this post
Link to post
Share on other sites