mod_log_sql - Error

[Reinhold Uhrmacher]

Hi,

 

we are still trying to migrate our board from Version 3.4.8 to 4.4.x and I restarted the process from scatch.

I set up debian 8 on a virtual machine (because our provider runs debian 8 as well) and set up mysql, apache, php5, phpmyadmin.

I created a new database via phpmyadmin an restored the backup of our live-board via mysql -u myuser -p database < mydump.sql, which also succeeded.

After adapting the configfile to the new database credentials I accessed the url of the board and got a message, that said, that something with the database connection is wrong. Looking in the error.log of apache I found those messages:

[Tue Feb 04 04:14:22.085231 2020] [:error] [pid 2927] mod_log_sql: child spawned but unable to open database link
[Tue Feb 04 04:14:32.099367 2020] [:error] [pid 2935] mod_log_sql: insufficient configuration info to establish database link
[Tue Feb 04 04:14:32.099433 2020] [:error] [pid 2935] mod_log_sql: child spawned but unable to open database link
[Tue Feb 04 04:15:29.064443 2020] [core:notice] [pid 2923] AH00052: child pid 2927 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.064468 2020] [core:notice] [pid 2923] AH00052: child pid 2928 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.064473 2020] [core:notice] [pid 2923] AH00052: child pid 2929 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.064479 2020] [core:notice] [pid 2923] AH00052: child pid 2931 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.064482 2020] [core:notice] [pid 2923] AH00052: child pid 2935 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.130359 2020] [core:notice] [pid 2923] AH00052: child pid 2930 exit signal Segmentation fault (11)
[Tue Feb 04 04:15:29.130474 2020] [mpm_prefork:notice] [pid 2923] AH00169: caught SIGTERM, shutting down
[Tue Feb 04 04:15:30.173108 2020] [mpm_prefork:notice] [pid 2981] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Tue Feb 04 04:15:30.173130 2020] [core:notice] [pid 2981] AH00094: Command line: '/usr/sbin/apache2'
[Tue Feb 04 04:15:30.173315 2020] [:error] [pid 2989] mod_log_sql: insufficient configuration info to establish database link
[Tue Feb 04 04:15:30.173325 2020] [:error] [pid 2989] mod_log_sql: child spawned but unable to open database link

Since phpmyadmin works, my first thought was, that it must be an issue with IP Board.

Any ideas?

Thanx for your help in advance
 

[bfarber]

I'm guessing you need to edit sql_socket in your conf_global.php file so it can use the correct socket to establish the connection.

[Reinhold Uhrmacher]

Hi bfarber,

thanx for your answer. I am not sure which value to put in. In

it says: 'sql_socket'    => '/var/lib/mysql.sock',

On our system /var/lib/mysql.sock does not exist and I cannot find any file mysql.sock under /var.

Any advice, which value to set?

Thanx and kind regards

[Reinhold Uhrmacher]

I put in conf_global.php:

  'sql_debug' => '1',

Where does it log to?

[bfarber]

sql_debug is no longer valid (that was a 3.x thing)

If your conf_global.php has the socket specified as /var/lib/mysql.sock and that file doesn't exist, then that's quite likely the problem. I would try removing that and see if everything works properly, and if not contact your host to see what the correct path to the MySQL socket file should be. You may also be able to retrieve it from php.ini if your host has configured it there.

[Reinhold Uhrmacher]

Found the directory, where sql-errors were logged (any yes, we are still on 3.x) and finally found out, that I had a typo in the login-credentials for the database.

The SQL-Error log-files (if anybody has the same problem) can be found in the cache/ directory for version 3.x

Thanx for your help and the mod_log_sql error was imho not a part of the prob.