Date: Tue, 05 Apr 2005 08:35:22 +0200 From: Uzi Klein <uzi@bmby.com> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-stable@freebsd.org Subject: Re: apache+mod_ssl signal 4 Message-ID: <425231AA.7040705@bmby.com> In-Reply-To: <20050404103341.H20646@carver.gumbysoft.com> References: <424D1FBD.3070207@bmby.com> <20050401185643.I94922@carver.gumbysoft.com> <20050402065702.GA69101@pit.databus.com> <20050402145930.G1503@carver.gumbysoft.com> <42501965.3030103@bmby.com> <425049F8.3060704@mac.com> <4250DB47.5020008@bmby.com> <20050404103341.H20646@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote: [....] >>php was compiled with OpenSSL support. >>When I removed that, it works like charm. >>( Still, i might want that future one day ) >> [....] > I've seen this if you have multiple OpenSSL versions installed and somehow > both libraries get linked in at once. This commonly happens if you have > program X linked against openssl 0.9.6 and load shared library Y linked > against 0.9.7. > > Use ldd to inspect your httpd and php modules and try to find the > offending openssl library. Perhaps you installed OpenSSL as a port at one > point? Thanks for giving me the idea. Perhaps there was some kind of test using OpenSSL from ports, even tho there's no track of it. Doesn't OpenSLL rebuild the libs when one rebuild world? Anyway, feels better now when the problem is "fixed" and i have a general idea of what the problem is. -- Uzi Klein BMBY Software Systems Ltd http://www.bmby.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425231AA.7040705>