The "bad header" could be an error message being printed before the
Content-type line. After a move that changes their siteXXX number, most
likely candidate is a hard wired $foo_dir in the config section for a CGI
script, which has been hard wired to a numbered site path from the old
server.
So go searching in the CGI dir for "home/.sites", and anything you find,
change to the slightly more migration tolerant /home/sites/www.foo.com/
path.
Might not be the problem, but it's a place to start looking.
-- hugh
> -----Original Message-----
> From: Diana Saunders [mailto:toodi4 (at mark) hotmail.com]
> Sent: Monday, June 18, 2007 2:28 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:10146] cgi script problem when going from Cobalt to BQ
>
> I know this issue has been dealt with before, but I can't seem to find a
> reference to it.
>
> I switched a customer's account from a RAQ 550 server to a server with the
> Nuonce BQ/Centos package. There is a very simple CGI perl script that is
> getting an internal server error. (and yes, permissions and ownership are
> all correct and the cgi environment script I use runs just fine)
>
> In the apache error log, the error message is:
>
> malformed header from script. Bad header=/home/.sites/148/site16/.users:
> cgiwrap,
>
> The users directory is the users directory for the site, though it isn't
> referenced in the script itself.
>
> Can anyone help?
>
> _________________________________________________________________
> Who's that on the Red Carpet? Play & win glamorous prizes.
> http://club.live.com/red_carpet_reveal.aspx?icid=REDCARPET_hotmailtextlink
> 3
>