Hallo Com,
vlt kann mir einer von euch helfen, habe immer mal wieder das Problem das der SQL Server crascht.... wäre erstmal nicht schlimm, nur finde ich den Grund dafür leider nicht.
Der Server läuft und läuft und läuft und iwann kann man nicht mehr auf die DB zugreifen und auch nicht mehr mit dem Client einloggen.
Wenn man nun versucht den SQL neu zu starten, bekommt man die Meldung das dieser nicht mehr läuft. (Restart)
Habe noch den Log des SQL Server angehängt. Ich hoffe das mir einer von euch helfen kann.
Vielen dank schonmal.
SQL Log:
Fehler beim Starten der Files:
vlt kann mir einer von euch helfen, habe immer mal wieder das Problem das der SQL Server crascht.... wäre erstmal nicht schlimm, nur finde ich den Grund dafür leider nicht.
Der Server läuft und läuft und läuft und iwann kann man nicht mehr auf die DB zugreifen und auch nicht mehr mit dem Client einloggen.
Wenn man nun versucht den SQL neu zu starten, bekommt man die Meldung das dieser nicht mehr läuft. (Restart)
Habe noch den Log des SQL Server angehängt. Ich hoffe das mir einer von euch helfen kann.
Vielen dank schonmal.
SQL Log:
Code:
2018-09-28 23:32:31 722 [Warning] IP address '185.234.219.169' could not be resolved: hostname nor servname provided, or not known 2018-09-29 02:50:00 722 [Warning] IP address '211.218.126.142' could not be resolved: hostname nor servname provided, or not known 180929 03:03:32 mysqld_safe mysqld restarted 2018-09-29 03:03:36 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2018-09-29 03:03:36 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.41) starting as process 2313 ... 2018-09-29 03:03:36 2313 [Note] Plugin 'FEDERATED' is disabled. 2018-09-29 03:03:36 2313 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-09-29 03:03:36 2313 [Note] InnoDB: The InnoDB memory heap is disabled 2018-09-29 03:03:36 2313 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-09-29 03:03:36 2313 [Note] InnoDB: Memory barrier is not used 2018-09-29 03:03:36 2313 [Note] InnoDB: Compressed tables use zlib 1.2.11 2018-09-29 03:03:36 2313 [Note] InnoDB: Not using CPU crc32 instructions 2018-09-29 03:03:36 2313 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2018-09-29 03:03:36 2313 [Note] InnoDB: Completed initialization of buffer pool 2018-09-29 03:03:36 2313 [Note] InnoDB: Highest supported file format is Barracuda. 2018-09-29 03:03:36 2313 [Note] InnoDB: The log sequence numbers 1626047 and 1626047 in ibdata files do not match the log sequence number 1626057 in the ib_logfiles! 2018-09-29 03:03:36 2313 [Note] InnoDB: Database was not shutdown normally! 2018-09-29 03:03:36 2313 [Note] InnoDB: Starting crash recovery. 2018-09-29 03:03:36 2313 [Note] InnoDB: Reading tablespace information from the .ibd files... 2018-09-29 03:03:36 2313 [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 account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd 2018-09-29 03:03:36 803806400 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 ./account/server_settings.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. 180929 03:03:37 mysqld_safe mysqld from pid file /var/db/mysql/cloud604777.fastpipe.io.pid ended<img src="https://www.*******************/cms/attachment/1989-pasted-from-clipboard-png/?thumbnail=1" class="woltlabAttachment" data-attachment-id="1989" id="wcfImgAttachment0">
Fehler beim Starten der Files:
Code:
Startet die Datenbank .. Real Server Log Offmysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) failed, retrying in 5 secondsReiche_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected Kern1_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) failed, retrying in 5 secondsKern2_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected Kern3_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) failed, retrying in 5 secondsNeutraler_Server is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: game99 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: core db: common cannot start server while no common sql connected Reiche_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected auth is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: auth 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: core db: common cannot start server while no common sql connected Kern1_Ch1 is not running PUBLIC_IP: x.x.0.0 interface vtnet0 HOSTNAME: channel1 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: core db: common cannot start server while no common sql connected Der Loginserver wurde gestartet.