[Mod_log_sql] Setting up mod_log_sql

[Chris Boler]

Hello Edward,
Thanks for your response. I'm not sure what libdbi THINKS it is linking to,
but I only have one mysql installation - which is version 4.1 - should I
downgrade?

As for apache, it is MPM Prefork

Thanks a lot,
--Chris

Edward Rudd <urkle at outoforder.cc> wrote:

> On Sun, 2005-06-26 at 02:27, Chris Boler wrote:
> > Okay so far what I have done is remove the debian packages and compile
> > everything from source. The same error still comes into effect:
> > 
> > [Sun Jun 26 18:42:09 2005] [notice] child pid 24681 exit signal
Segmentation
> > fault (11)
> > [Sun Jun 26 18:42:09 2005] [debug] mod_log_sql_mysql.c(54): HOST:
> '10.0.0.10'
> > PORT: '3306' DB: 'apachelogs' USER: 'apache' SOCKET:
> > '/var/lib/mysql/mysql.sock'
> > [Sun Jun 26 18:42:09 2005] [debug] mod_log_sql.c(443): mod_log_sql:
> > open_logdb_link successful
> > 
> > The only mods loaded are mod_dbi_pool, mod_log_sql, mod_vhost_dbi.
> 
> AHHH
> 
> you need to check what version of mysql libdbi is linked to. As that's
> probably where the root cause of the issue is. And what MPM module are
> you using with apache (ie. prefork or worker)
> 
> > One works when the other is disabled - e.g. when mod_vhost_dbi is not
> enabled,
> > it will log fine. When mod_log_sql is not enabled, the vhosts work fine. I
> > have a feeling it doesnt like that it has to get the vhost from the
database
> > because of mod_vhost_dbi... Any suggestions anyone?
> > 
> > Thanks,
> > --Chris
> > 
> > Craig Webster <craig at xeriom.net> wrote:
> > 
> > > Hi Chris,
> > > On 19 Jun 2005, at 09:18 you wrote:
> > > 
> > > > here is further output from error logs in debug level:
> > > [snip]
> > > > [Sun Jun 19 19:32:13 2005] [notice] Embperl/2.0rc3 Apache/2.0.54  
> > > > (Debian
> > > > GNU/Linux) mod_auth_kerb/5.0-rc6 DAV/2 SVN/1.1.4 mod_jk2/2.0.4
> > > > mod_ldap_userdir/1.1.7 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-15
> > > > proxy_html/2.4 mod_dbi_pool/0.1.0 mod_vhost_dbi/0.1.0 mod_perl/ 
> > > > 1.999.21
> > > [/snip]
> > > 
> > > Have you upgraded Apache recently? I had this problem when one of my  
> > > modules was compiled against a previous version of Apache.
> > > 
> > > You can easily find out which one by turning off each of the above  
> > > modules in turn and restarting Apache, watching for the segfaults.  
> > > Quite a lot of people have the problem with PHP - if this is the  
> > > problem module then make sure you delete the php module dir and the  
> > > old version of libphp before recompiling.
> > > 
> > > Simply recompiling the offending module stopped it for me.
> > > 
> > > Thanks,
> > > Craig
> > > --
> > > Craig Webster   | e: craig at xeriom.net  | t: +44 (0)2078 710 745
> > > Xeriom Networks | w: http://xeriom.net | Web hosting for the UK
> > > 
> > > _______________________________________________
> > > Download the latest version at
> > > http://www.outoforder.cc/projects/apache/mod_log_sql/
> > > 
> > > To unsubscribe send an e-mail to 
> > > mod_log_sql-unsubscribe at lists.outoforder.cc
> > > 
> > 
> > 
> > 
> > _______________________________________________
> > Download the latest version at
> http://www.outoforder.cc/projects/apache/mod_log_sql/
> > 
> > To unsubscribe send an e-mail to 
> mod_log_sql-unsubscribe at lists.outoforder.cc