Forum Moderators: phranque

Message Too Old, No Replies

Started getting this weird error

500 EOF when chunk header expected

         

runner

7:22 am on Aug 28, 2005 (gmt 0)

10+ Year Member



My main web page on my web site stopped working tody. What happens is the server serves up part of the page and then just stops. I'm using SSI includes for several areas. Apache seems to be choking on three different includes, one is a CGI and the other two are text files. If I comment out the three includes everything works. If I uncomment one of the three includes, apache stops serving up the page exactly at the spot where the include is located. Absolutely no errors in the apache error log. There are other includes on this page that are working.

What's weird about this is there are absolutey no errors in the apache log file. This is a hosted account so I don't see the main apache log file, just my domain logs.

However, just for kicks, I went to the w3c validator and typed in my link and it gave me this error:

*** Start of error message
500 EOF when chunk header expected

If you made recent changes to your domain name (DNS) configuration, you may also want to check that your domain records are correct, or ask your hosting company to do so.
*** End of error message

I don't see how DNS could be an issue here. This is weird. I didn't change anything on my web site today. I think the hosting company must have changed something that affected the way apache's ssi works.

My hosting company is well known for low prices and terrible support so I'm looking for help troubleshooting this so I can tell them how to fix it.

I'd also appreciate any other troubleshooting tips.

Because I don't see any errors in my apache error_log, I'm wondering if it's an apache problem that is system-wide and not specific to my domain and that's why I'm not seeing the errors.

runner

7:27 am on Aug 28, 2005 (gmt 0)

10+ Year Member



Oh... one more thing I forgot to mention, I don't believe my includes are faulty for two reasons:

1) I didn't modify anything today
2) If there was a problem with the include like bad syntax or a missing file, apache would have gone ahead and served up the page with that standard error message where the "bad" include was. I think apache's standard error message is something like "An error occured while processing this directive"

I'm not getting those errors. Apache just stops sending the page.