[Mod_log_sql] mod_log_sql 1.97 with Apache 2 with MySQL on FreeBSD...

Paul Chvostek paul+modlogsql at it.ca
Sun Jul 11 03:26:47 EST 2004


I've been using mod_log_sql v1.18 with Apache 1.3 for quite some time
with great success.  I thought it might be fun to play around with
Apache 2, but I've hit a (perhaps small) roadblock.

I'm using FreeBSD 5.2.1, MySQL 4.0.20, Apache 2.0.50, PHP 5.0.0.r3
(compiled with MySQL support) and mod_log_sql 1.97 (ya, someone needs
to poke the FreeBSD port maintainer).  My configs include:

  LogSQLLoginInfo mysql://not:used@not/used
  LogSQLForcePreserve on
  LogSQLPreserveFile /tmp/sql-preserve

  <VirtualHost *:80>
    LogSQLTransferLogTable access_log

All log data goes to a single access_log table which contains a field
for virtualhost.  My goal is to log only to the Preserve file, which
I'll batch-process at regular intervals.  This is to reduce the number
of database connections, giving me more control over db server load.

The problem is, Apache is reporting segfaults to its error_log:

[Sun Jul 11 03:59:30 2004] [notice] child pid 3866 exit signal Segmentation fault (11)
[Sun Jul 11 03:59:35 2004] [notice] child pid 3867 exit signal Segmentation fault (11)

FAQ question 2.1 seemed plausable enough until I noticed that PHP5 seems
to use the real MySQL libraries rather than rolling its own.

Am I missing something obvious?  Before I go through regression testing,
backing out of each of the "new" pieces of software I'm playing with, is
there something obvious I've missed?  Is anyone else using mod_log_sql
with Apache2 and PHP5 with MySQL?


  Paul Chvostek                                             <paul at it.ca>
  Operations / Abuse / Whatever
  it.canada, hosting and development                   http://www.it.ca/

More information about the Mod_log_sql mailing list