Bad or malformed header in Fast CGI environment [RESOLVED]

[mstreet]

Hi folks,

I have a conference that I am in the middle of setting up. I'm using OCS 2.0, and when I initially set it up in our Linux, Apache, Fast CGI environment, I had to disable the PATH_INFO variable in the config settings.

I have some users who have uploaded some submissions, but when they go to 'Edit Metadata', the server throws an Internal Server Error (500), with this in the logs:

Code: Select all

[Thu Mar 06 16:16:17 2008] [error] [client <removed>] malformed header from script. Bad header=\r\n : index.php, referer: http://<removed>/index.php?conference=carfms&schedConf=carfms08&page=presenter&op=submission&path[]=1

I suspect that this is related to the PATH problem, but that's only my guess. Can anyone help with this? If there's any more details I can provide, please let me know.

I have been able to get this to work on a 'normal' Apache set-up with mod_php. Unfortunately, we've put too much work into this conference site to switch environments now. I really need a way to get this working under Fast CGI.

Any help would be greatly appreciated,
Mike.

[smiri]

Hi Mike,

Are you sure that's the only error message you're getting in your error logs? I have feeling that there's another message or two before this one. This message usually just means that something else went wrong before this.

Also do you know what type of submission files the users uploaded? And if it's happening for everyone or just a particular user?

Regards,

[mstreet]

Hi,

Thanks for replying, I appreciate it. I've gone over all the possible logs, in my hosting environment:

access.log
error.log
suexec.log

The only one that shows anything is the error.log with the same message I posted earlier. Although web applications are run as the user, I do have root access to the box, if you think there's someplace else I should look.

I've also confirmed that it happens regardless of which user attempts to edit the metadata of their submission.

This error is unfortunately a show-stopper for the adoption of the software for us, so any help would be greatly appreciated. Thanks in advance.

[smiri]

Hi Mike,

Could you check and see what your php memory limit is set at? you could check this in your php.ini file. The memory limit needs to be at least 16MB for the latest OJS version to function correctly. (Make sure to restart your apache server when you make a php.ini change)

Regards,

[mstreet]

Our memory limit is set to 24, so that's not the problem. We also do not have Zend optimizer installed. Thankfully, I was able to determine that upgrading Apache to 2.2 and Fast CGI fixed the problem. We were initially running apache 2.0.55.