e107help.org Q&A

CRITICAL ERROR

0 like 0 dislike

Hello people, I have a very strange problem. The problem is that my site constantly crashes with the following error:

CRITICAL ERROR:

Line : generic, class2.php

[6]: Unable to form a valid connection to mySQL. Please check that your e107_config.php contains the correct information.

Interestingly, it may stop today or in a week and this is happening several times I do not know where I'm wrong in e107_config.php everything is fine or at least I think so. I saw that there was such a topic but I probably did not understand what to do or my problem is not exactly that. Also when I stop everything, I run the site again and everything works but it's not known how long.

Thank you in advance for help, and apologize if I repeat the same topic because of my stupid.
 

e107 version e107_2.1.9_full
in Core by (11 points) ● 1 ● 2 ● 2

1 Answer

0 like 0 dislike

Hi!

It appears that at some point the e107 installation is no longer able to connect with the MySQL database (server). Seeing that this is an intermittent issue (rather than just 'all the time') I would suggest you ask your hosting provider to see if they can check the error logs at the times that the error occurs. This may give us some clues if there perhaps is an incompatibility with e107's code, or whether there is a server (configuration) side issue. 

If the error occurs, you can also try this to find more information:

- In your e107_config.php file, try adding this: define('e_DEBUG', true); 
- This will provide additional information in the error message which may help to find some clues 

Be sure to remove the line in the e107_config.php file (or change  'true' to 'false') if the error has disappeared again. This way no debug information is shown unintentionally. 

 

by (2.7k points) ● 7 ● 10 ● 10

Hi Moc , I'm the host and forgot to mention that I host 2 sites from one machine. I guess you need mysql_error and apache_error files? If it's not you just tell me who and will give it to you.

Apache error
libpng warning: bKGD: invalid
[Tue Feb 05 09:59:13.119255 2019] [ssl:warn] [pid 7728:tid 260] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Feb 05 09:59:13.197255 2019] [core:warn] [pid 7728:tid 260] AH00098: pid file G:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Tue Feb 05 09:59:13.197255 2019] [ssl:warn] [pid 7728:tid 260] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Feb 05 09:59:13.228455 2019] [mpm_winnt:notice] [pid 7728:tid 260] AH00455: Apache/2.4.33 (Win32) OpenSSL/1.1.0h PHP/7.2.7 configured -- resuming normal operations
[Tue Feb 05 09:59:13.228455 2019] [mpm_winnt:notice] [pid 7728:tid 260] AH00456: Apache Lounge VC15 Server built: Mar 28 2018 12:12:41
[Tue Feb 05 09:59:13.228455 2019] [core:notice] [pid 7728:tid 260] AH00094: Command line: 'g:\\xampp\\apache\\bin\\httpd123.exe -d G:/xampp/apache'
[Tue Feb 05 09:59:13.244055 2019] [mpm_winnt:notice] [pid 7728:tid 260] AH00418: Parent: Created child process 5728
[Tue Feb 05 09:59:14.150857 2019] [ssl:warn] [pid 5728:tid 272] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Feb 05 09:59:14.213257 2019] [ssl:warn] [pid 5728:tid 272] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Feb 05 09:59:14.244457 2019] [mpm_winnt:notice] [pid 5728:tid 272] AH00354: Child: Starting 150 worker threads.

by (11 points) ● 1 ● 2 ● 2
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.
by (11 points) ● 1 ● 2 ● 2
Sorry the late reply.

The above error log shows that several database tables (including mysql.user which is quite impressive, but also three e107 tables) have crashed. Apparently they get corrupted. Somehow the database got or intermittenly gets corrupted. Perhaps during an incorrect (e.g. unexpected, forced) shutdown?

You can ty repairing the database tables. This is not something that can be fixed by e107 itself. It's a server side issue that needs solving.
by (2.7k points) ● 7 ● 10 ● 10

Hi Moc you told me to write this setting define('e_DEBUG', true); and the error I received were:

Apache

[Sun Feb 24 10:40:26.489117 2019] [mpm_winnt:notice] [pid 8720:tid 260] AH00455: Apache/2.4.33 (Win32) OpenSSL/1.1.0h PHP/7.2.7 configured -- resuming normal operations
[Sun Feb 24 10:40:26.489117 2019] [mpm_winnt:notice] [pid 8720:tid 260] AH00456: Apache Lounge VC15 Server built: Mar 28 2018 12:12:41
[Sun Feb 24 10:40:26.489117 2019] [core:notice] [pid 8720:tid 260] AH00094: Command line: 'g:\\xampp\\apache\\bin\\httpd123.exe -d G:/xampp/apache'
[Sun Feb 24 10:40:26.490117 2019] [mpm_winnt:notice] [pid 8720:tid 260] AH00418: Parent: Created child process 5500
[Sun Feb 24 10:40:27.500175 2019] [ssl:warn] [pid 5500:tid 272] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sun Feb 24 10:40:27.557178 2019] [ssl:warn] [pid 5500:tid 272] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sun Feb 24 10:40:27.592180 2019] [mpm_winnt:notice] [pid 5500:tid 272] AH00354: Child: Starting 150 worker threads.

by (11 points) ● 1 ● 2 ● 2

MySQL


2019-02-23 16:01:52 16164 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-23 16:01:52 16164 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-23 16:01:57 16164 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-23 16:01:57 16164 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
Version: '10.1.34-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2019-02-23 17:18:06 6708 [ERROR] mysqld.exe: Table '.\e107abcdev\e107_user' is marked as crashed and should be repaired
2019-02-23 17:18:06 6708 [Warning] Checking table:   '.\e107abcdev\e107_user'
2019-02-23 17:18:06 6708 [ERROR] mysqld.exe: Table '.\e107abcdev\e107_news' is marked as crashed and should be repaired
2019-02-23 17:18:06 6708 [Warning] Checking table:   '.\e107abcdev\e107_news'
2019-02-23 17:18:06 6708 [ERROR] mysqld.exe: Table '.\e107abcdev\e107_core' is marked as crashed and should be repaired
2019-02-23 17:18:06 6708 [Warning] Checking table:   '.\e107abcdev\e107_core'
2019-02-23 17:18:19 6708 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_user' is marked as crashed and should be repaired
2019-02-23 17:18:19 6708 [Warning] Checking table:   '.\e107syrinx\e107_user'
2019-02-23 17:18:19 6708 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_core' is marked as crashed and should be repaired
2019-02-23 17:18:19 6708 [Warning] Checking table:   '.\e107syrinx\e107_core'
2019-02-23 17:18:19 6708 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_page' is marked as crashed and should be repaired
2019-02-23 17:18:19 6708 [Warning] Checking table:   '.\e107syrinx\e107_page'
2019-02-23 17:31:56 14260 [Warning] IP address '111.73.46.33' could not be resolved: No such host is known.
2019-02-23 17:44:10 6200 [Warning] IP address '85.93.20.38' could not be resolved: The requested name is valid, but no data of the requested type was found.
2019-02-23 18:40:53 14296 [Warning] IP address '191.96.214.13' could not be resolved: No such host is known.
2019-02-23 20:33:09 6816 [Warning] IP address '71.6.232.5' could not be resolved: No such host is known.
2019-02-23 21:58:10 11180 [Warning] Host name 'zg-0116c-30.stretchoid.com' could not be resolved: No such host is known.
2019-02-24  1:03:21 10352 [Warning] IP address '195.143.228.107' could not be resolved: No such host is known.
2019-02-24  1:03:29 10352 [ERROR] mysqld.exe: Table '.\e107abcdev\e107_admin_log' is marked as crashed and should be repaired
2019-02-24  1:03:29 10352 [Warning] Checking table:   '.\e107abcdev\e107_admin_log'
2019-02-24  1:03:31 10352 [ERROR] mysqld.exe: Table '.\e107syrinx\e107_admin_log' is marked as crashed and should be repaired
2019-02-24  1:03:31 10352 [Warning] Checking table:   '.\e107syrinx\e107_admin_log'
2019-02-24  3:13:53 7256 [Warning] IP address '138.68.18.223' could not be resolved: No such host is known.
2019-02-24  3:13:54 7256 [ERROR] mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired
2019-02-24  3:13:54 7256 [Warning] Checking table:   '.\mysql\user'
2019-02-24  3:13:54 7256 [ERROR] mysqld.exe: Table '.\mysql\db' is marked as crashed and should be repaired
2019-02-24  3:13:54 7256 [Warning] Checking table:   '.\mysql\db'
2019-02-24  3:59:47 5424 [Warning] IP address '212.114.52.250' 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-24  5:05:28 13644 [Warning] Host name 'hn.kd.ny.adsl' could not be resolved: No such host is known.
2019-02-24  5:14:18 13212 [Warning] IP address '212.114.52.250' 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-24  8:08:58 3628 [Warning] Host name 'zg-0116c-59.stretchoid.com' could not be resolved: No such host is known.
2019-02-24 10:40:34 3288 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-24 10:40:34 12936 [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.

Version: '10.1.34-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2019-02-24 14:12:19 12660 [Warning] IP address '58.218.66.92' could not be resolved: No such host is known.
2019-02-24 14:12:22 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:22 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:27 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:27 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:37 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:37 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:42 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-24 14:12:42 12660 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-24 17:04:37 1536 [Warning] IP address '138.68.29.165' could not be resolved: No such host is known.
2019-02-24 17:34:43 14780 [Warning] IP address '111.73.46.33' could not be resolved: No such host is known.
2019-02-24 17:34:47 14780 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'min_value' at position 3 to have type varbinary(255), found type varchar(255).
2019-02-24 17:34:47 14780 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'max_value' at position 4 to have type varbinary(255), found type varchar(255).
2019-02-24 18:05:00 6504 [Warning] IP address '191.96.110.41' could not be resolved: No such host is known.

 

by (11 points) ● 1 ● 2 ● 2

Please see my previous reply and please google these errors. They are not e107 specific.

Your MySQL database appears to have serious issues with crashed database tables. Also, there are several errors such as "IP address 'X' could not be resolved: No such host is known." This may explain why the MySQL server is unreachable. The error you get from e107 is a standard MySQL error, nothing e107 specific. I cannot help you further with this. Please contact your webhosting provider 

by (2.7k points) ● 7 ● 10 ● 10
Welcome to e107 Q&A, where you can ask questions and receive answers from other members of the e107 community.
920 questions
1,320 answers
2,305 comments
2,290 users