Date: Mon, 4 Apr 2005 10:35:55 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Uzi Klein <uzi@bmby.com> Cc: freebsd-stable@freebsd.org Subject: Re: apache+mod_ssl signal 4 Message-ID: <20050404103341.H20646@carver.gumbysoft.com> In-Reply-To: <4250DB47.5020008@bmby.com> References: <424D1FBD.3070207@bmby.com> <20050401185643.I94922@carver.gumbysoft.com> <20050402145930.G1503@carver.gumbysoft.com> <4250DB47.5020008@bmby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Apr 2005, Uzi Klein wrote: > Chuck Swiger wrote: > > [.....] > > Try using PHP from the ports and see whether that runs better. If it > > does, well, take a look at what the port changes, and you've probably > > located the source of your current problems. > > I mananged to fix it. > php was compiled with OpenSSL support. > When I removed that, it works like charm. > ( Still, i might want that future one day ) > > BTW, PHP has no specific FreeBSD patches AFAIK, and it was working on > 5.3-RELEASE before p-5. > > Looks more like a shared lib problem than a PHP bug to me, but then > again, I'm no expert. 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? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050404103341.H20646>