Mysql_error
2019-02-04 18:35:50 8556 [Warning] IP address '111.175.60.97' could not be resolved: No such host is known.
2019-02-04 18:35:50 9364 [Warning] IP address '111.175.60.97' could not be resolved: No such host is known.
2019-02-04 18:53:16 8956 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-04 19:30:18 11116 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-04 20:07:04 5900 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-04 20:57:04 4808 [Warning] IP address '191.101.128.1' has been resolved to the host name '191.101.128.1.netsystemsresearch.com', which resembles IPv4-address itself.
2019-02-05 0:42:54 5596 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 1:18:46 10912 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 2:12:18 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:19 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:19 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:20 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:21 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:21 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:22 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:22 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:23 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:24 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:24 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:25 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:26 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:26 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:27 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:28 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:28 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:29 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:30 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:30 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:31 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:32 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 2:12:32 4072 [Warning] IP address '138.36.199.30' has been resolved to the host name '138.36.199.30.speedtelcomunicacoes.com.br', which resembles IPv4-address itself.
2019-02-05 4:02:01 10180 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 4:37:56 8124 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 5:14:03 7144 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 5:49:18 5972 [Warning] IP address '113.96.223.207' could not be resolved: No such host is known.
2019-02-05 5:49:18 1940 [Warning] IP address '113.96.223.207' could not be resolved: No such host is known.
2019-02-05 7:49:40 5000 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 8:24:11 10304 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 9:00:05 11204 [Warning] IP address '85.93.20.38' could not be resolved: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2019-02-05 09:59:13 1360 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-02-05 9:59:13 4960 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-02-05 9:59:13 4960 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-05 9:59:13 4960 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-05 9:59:13 4960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-02-05 9:59:13 4960 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-02-05 9:59:13 4960 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-02-05 9:59:13 4960 [Note] InnoDB: Using generic crc32 instructions
2019-02-05 9:59:13 4960 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-02-05 9:59:13 4960 [Note] InnoDB: Completed initialization of buffer pool
2019-02-05 9:59:13 4960 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-05 9:59:13 4960 [Note] InnoDB: The log sequence number 1835717 in ibdata file do not match the log sequence number 61296488 in the ib_logfiles!
2019-02-05 9:59:13 4960 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-02-05 9:59:14 4960 [Note] InnoDB: 128 rollback segment(s) are active.
2019-02-05 9:59:14 4960 [Note] InnoDB: Waiting for purge to start
2019-02-05 9:59:15 4960 [Note] InnoDB: Percona XtraDB (
http://www.percona.com) 5.6.39-83.1 started; log sequence number 61296488
2019-02-05 9:59:15 6576 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-02-05 9:59:15 4960 [Note] Plugin 'FEEDBACK' is disabled.
2019-02-05 9:59:15 4960 [Note] Server socket created on IP: '::'.
2019-02-05 9:59:15 4960 [Note] g:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.34-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2019-02-05 9:59:35 5424 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_core' is marked as crashed and should be repaired
2019-02-05 9:59:35 5424 [Warning] Checking table: '.\e107syrinx\e107_core'
2019-02-05 9:59:36 5424 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_user' is marked as crashed and should be repaired
2019-02-05 9:59:36 5424 [Warning] Checking table: '.\e107syrinx\e107_user'
2019-02-05 9:59:36 5424 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_page' is marked as crashed and should be repaired
2019-02-05 9:59:36 5424 [Warning] Checking table: '.\e107syrinx\e107_page'
2019-02-05 15:20:52 9092 [ERROR] mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired
2019-02-05 15:20:52 9092 [Warning] Checking table: '.\mysql\user'
Thanks Moc for the fast answer.