RE: [Devil-Linux-discuss] DL1.2.9/apache2 connection close, FIN,ACK error

[<gun...@lh...>]

Hi Dick,

I have had this same problem until yesterday.

After searching some Apache Mailing Lists I found out that what seems to =
be causing the problem is the "EnableSendfile" Directive in the Apache =
config. This sometimes is supposed to create problems on NFS Directories =
but also seems to create problems on the shm Filesystem und DL1.2.9.

After I set "EnableSendfile Off" in the Apache httpd.conf it seems to be =
working fine.

I hope this helps you and others too.

Best regards
Gunnar

>					=09
>Lufthansa Technik AG
>Completion Center
Gunnar Dibbern
>Dept. HAM WL/I, Innovation Engineering
>					=09


> -----Original Message-----
> From: dev...@li...=20
> [mailto:dev...@li...] On=20
> Behalf Of Dick Middleton
> Sent: Monday, March 06, 2006 11:07 AM
> To: dev...@li...
> Subject: Re: [Devil-Linux-discuss] DL1.2.9/apache2 connection=20
> close, FIN,ACK error
>=20
>=20
> Heiko,
>=20
> >>I've been having real trouble getting apache2 to work on DL 1.2.9.
>=20
> > I'm successfully using Apache on my Server at home, but=20
> then I'm not=20
> > using an index.html. Does it happen with any index.html, or=20
> only with=20
> > a specific one you created?
>=20
> It only happens with directly served files.  PHP works OK. =20
> Images and=20
> css files fail.
>=20
> What I did was copy the default index.html to /var/data/www which I'd=20
> created and changed the document root settings in httpd.conf=20
> appropriately.
>=20
> At that point it works.  I then added characters to the file until it=20
> failed.  255 chars works, 256 chars doesn't.
>=20
> I attach httpd.conf with all comment lines removed - just in case=20
> there's something stupid in it.  Also a 256 byte index.html.
>=20
> What's bizarre is that apache doesn't see a problem.  It thinks the=20
> pages are served correctly.
>=20
> Running "lynx localhost" is all you need to demonstrate the problem.=20
> However I've just discovered a "telnet localhost 80" access works OK.=20
> So maybe it's something in the headers? I attach what Firefox=20
> sends as well.
>=20
> It would be nice if someone could try to reproduce the=20
> problem to see if=20
> it's just me or more general.
>=20
> Dick
>=20
>=20