On Wed, Aug 09, 2006 at 07:57:28PM +0200, Martin Sebald wrote:
> because I was experiencing problems with libapache2-mod-auth-mysql 4.3.9-2
> (see other bug I submitted today) I upgraded to 4.3.9-2.1+b1. But this
> version seems to be a complete showstopper for me. I do not get anything
> from the webserver back. A deeper look into the global error.log showed
> this: 
> 
> > [Wed Aug 09 19:49:45 2006] [notice] child pid 9650 exit signal Segmentation 
> > fault (11)

Almost universally, problems with Apache processes segfaulting when
m-a-mysql is loaded are due to incompatibilities with your libmysqlclient
versions -- it's only *really* recently that the MySQL people have started
versioning their libraries.

Common "offenders" are PHP's MySQL extension, and the MySQL vhosting module.
They're often used, and there's no guarantee that the libmysqlclient version
linked against them is the same as that used by m-a-mysql.

Check (using ldd or apt-cache show) that anything that might link against
both Apache and MySQL (directly *or* indirectly) is using the same
libmysqlclient version.  Fixing it is extra special, but in this case I'd
suggest just going back to 4.3.9-2.  -2.1 was a transition upload, and it
looks like it's been rebuilt since (the +b1), but none of that should have
any effect on you if you were running 4.3.9-2 properly.

- Matt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to