next »

[CrazyDave]

I have been testing CalendarScript (GREAT SCRIPT, Matt!). I had one calendar working great for the past few weeks. Yesterday, it would not let me log in to admin, so I checked the docs and searched the forum, and followed the instuctions I found. This didn't work, so I saved my custom calendar, deleted all files, and reinstalled CalendarScript. Since then I have been receiving Server Error 500's. I again searched the documentaion and followed the instuctions, checking the path to perl and my file permissions, all in order. I did upload using ASCII, and CHMOD'ed all the files as instructed. I have changed nothing in the script. I try to run debug.pl, but it gives me the 500 error. The server's error log shows that this is being caused by a "Premature end of script headers" error. I have installed the script several times on different servers, and have never had any problems, so I'm baffled! Here are the particulars of the webhost, Startlogic:

code:

FreeBSD 4.8-RELEASE
perl, v5.8.3
/usr/bin/perl

I hope you guys can help, cause I'm pulling mr hair out!

------------------
Peace,
Dave

[DanO]

** The server's error log shows that this is being caused by a "Premature end of script headers" error. **

That just means the script failed to produce any output and is not actually the cause of the error but the result.

If the error logs are not recording any more specific error messages, you may need to run the script from the shell (telnet, SSH, etc.) to see what error's Perl reports.

** I have changed nothing in the script. **

That doesn't mean that nothing on the server has changed. Any changes there could be responsible for the error.

Have you tried contacting your host's support to see if they have any ideas? If you don't have shell access, they may need to run the script for you to get the actual error causing the problem(s).

JMO

Dan O.

------------------

[CrazyDave]

Thanks for the quick reply, Dan!

You are right about the nature of the error--my bad! (I guess you can tell that I might know enough to be dangerous). I have not yet gotten hold of my host--it can be kind of trying getting through their automated trouble ticket system. I've have been wondering if they have changed something that has caused this.

I'll post more when I find out!

------------------
Peace,
Dave