[squid-users] problem with squid and squid2mysql

hi all,
Got a small problem here with squid running in conjunction with squid2mysql
on a linux box.

Config is

RH 9 system running as squid cache with a back end mysql database runnning
on another machine.
Perl 5.08 installed with dbi module, mysql drivers and perl::ldap

Created a special file on the webcache called /logs/mysqlacess.log and have
started

"cat /logs/mysqlaccess.log|tee -a
/logs/access.log|/usr/local/bin/squid2mysql 2>/logs/squid2mysql.err"

The above means I can still have the standard "access.log" file and dump
log entries into a back end database.

A back end RADIUS authentication database is also present to authenticate
various classes of users.

For various reasons i can't set up our dial in service to authenticate to
our web caches, so i've added some code to the squid2mysql perl prog that
performs an ldap query of our RADIUS server whenever a log file entry
appears with a client ip address that comes from our dialin service.
Basically it asks the radius server for the userid currently logged onto
the ip address obtained from the access log entry.

When i go through a web cache configured as described, everything works.
When i try routing all of our dial in service calls through it the squid
process crashes. I *think* its to do with the ldap lookups performed for
every log record associated with our dial in service - all i see in the
logs is "FATAL: Received Segment Violation...dying."

Just before I crank up the logging to see whats happening, anyone out there
using squid2mysql on a linux platform? - just to double check that it does
work in a production environment

alex

Sent using Mulberry 3.01a
Received on Thu Dec 18 2003 - 09:33:44 MST