|
From: David F. <Da...@me...> - 2005-05-12 09:24:20
|
Hi TIA, I could be on the wrong track, but I think I was getting this error until I created the directory /chroot/apache/usr/local/apache/logs/ssl_scache where the chroot is to /chroot/apache If I remember correctly, Apache wants to write there after the chroot has taken place, by which time it cannot open new files in the log directory in the main file system. Ensure Apache has write permissions even if the directory already exists. It's a while since I had the problem so I could have this wrong, but it might help. David >Subject: [mod-security-users] mod_ssl: Child could not open SSLMutex lockfile >Reply-To: mod...@li... > >------=_Part_2042_9626190.1115640236279 >Content-Type: text/plain; charset=ISO-8859-1 >Content-Transfer-Encoding: quoted-printable >Content-Disposition: inline > >Hi guys, > >When I chroot my Apache 1.3.x with mod_security, it kept reporting that=20 >error. I have searched through this list and found that this error had been= >=20 >reported one but still there is no solution rite?=20 -- --------------------------------------- Email da...@me... --------------------------------------- |
|
From: Thai D. <th...@gm...> - 2005-05-12 18:22:41
|
Hi David, 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. -T 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 until= =20 > 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 has= =20 > taken > place, by which time it cannot open new files in the log directory in the= =20 > main > file system. Ensure Apache has write permissions even if the directory > 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 > >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 > >=3D20 > >reported one but still there is no solution rite?=3D20 >=20 > -- > --------------------------------------- > Email da...@me... > --------------------------------------- >=20 > ------------------------------------------------------- > This SF.Net <http://SF.Net> email is sponsored by Oracle Space Sweepstake= s > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=3D7393&alloc_id=3D16281&op=3Dclick > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > |
|
From: Thai D. <th...@gm...> - 2005-05-13 23:38:59
|
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 > |
|
From: Thai D. <th...@gm...> - 2005-05-13 21:53:18
|
Sorry, I forgot to mention that problems only occur when I use=20 mod_security's internal chroot mechanism. Without chroot, everything's ok. On 5/14/05, Thai Duong <th...@gm...> wrote: >=20 > 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= =20 > the mod_ssl module (also compiled statically). mod_ssl complained that it= =20 > could not open its SSLMutext, and when I set SSLMutext to none, it contin= ued=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 the= se=20 > directories to apache but still no luck. It seems that mod_security is no= t=20 > made to use as a static module/in a static server (I meant a server that = all=20 > modules are compiled statically), rite? >=20 > -T >=20 > 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=20 > > work. Anyway, I found a solution, just set SSLMutex directive to none, = it=20 > > works 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 director= y=20 > > >=20 > > > already exists. > > >=20 > > > It's a while since I had the problem so I could have this wrong, but= =20 > > > it 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=20 > > > >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= =20 > > > had 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=20 > > > 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 > >=20 > |
