Re: [mod-security-users] Re: mod_ssl: Child could not open SSLMutex lockfile

[Thai D. <th...@gm...>]

FYI, I encountered a lot of problems when using mod_security as a static=20
module of both apache 1.3.x and httpd 2.x. Most of the problems are with th=
e=20
mod_ssl module (also compiled statically). mod_ssl complained that it could=
=20
not open its SSLMutext, and when I set SSLMutext to none, it continued=20
complained that it could not write to the scache directory, which I have=20
created both in the chroot jail and the original path. I also chowned these=
=20
directories to apache but still no luck. It seems that mod_security is not=
=20
made to use as a static module/in a static server (I meant a server that al=
l=20
modules are compiled statically), rite?

-T

On 5/13/05, Thai Duong <th...@gm...> wrote:
>=20
> Hi David,
>=20
> I have created that directory with a correct permission but it doest work=
.=20
> Anyway, I found a solution, just set SSLMutex directive to none, it works=
=20
> like a charm.
>=20
> -T
>=20
>=20
> On 5/12/05, David Fletcher <Da...@me...> wrote:
> >=20
> > Hi TIA,
> >=20
> > I could be on the wrong track, but I think I was getting this error=20
> > until I
> > created the directory
> >=20
> > /chroot/apache/usr/local/apache/logs/ssl_scache
> >=20
> > where the chroot is to /chroot/apache
> >=20
> > If I remember correctly, Apache wants to write there after the chroot=
=20
> > has taken
> > place, by which time it cannot open new files in the log directory in=
=20
> > the main
> > file system. Ensure Apache has write permissions even if the directory=
=20
> > already exists.
> >=20
> > It's a while since I had the problem so I could have this wrong, but it=
=20
> > might
> > help.
> >=20
> > David
> >=20
> > >Subject: [mod-security-users] mod_ssl: Child could not open SSLMutex=
=20
> > lockfile
> > >Reply-To: mod...@li...
> > >
> > >------=3D_Part_2042_9626190.1115640236279
> > >Content-Type: text/plain; charset=3DISO-8859-1
> > >Content-Transfer-Encoding: quoted-printable=20
> > >Content-Disposition: inline
> > >
> > >Hi guys,
> > >
> > >When I chroot my Apache 1.3.x with mod_security, it kept reporting=20
> > that=3D20
> > >error. I have searched through this list and found that this error had=
=20
> > been=3D=20
> > >=3D20
> > >reported one but still there is no solution rite?=3D20
> >=20
> > --
> > ---------------------------------------
> > Email da...@me...
> > ---------------------------------------=20
> >=20
> > -------------------------------------------------------
> > This SF.Net <http://SF.Net> email is sponsored by Oracle Space=20
> > Sweepstakes
> > Want to be the first software developer in space?
> > Enter now for the Oracle Space Sweepstakes!=20
> > http://ads.osdn.com/?ad_id=3D7393&alloc_id=3D16281&op=3Dclick
> > _______________________________________________
> > mod-security-users mailing list=20
> > mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/mod-security-users=20
> >=20
>=20
>