I have a bunch of virtual hosts that are all using the same virtual
host definitions (a populated template created for each account),
included using Apache 2.0's ability to do that.

Most accounts/virtual hosts run CGIs (Perl) fine, with Suexec enabled.

One, however, won't; all attempts to run CGIs fail with "Premature end
of script header" recorded to error_log and no additional information.
Even running httpd -X with strace didn't shed any light.  If I
comment out the SuexecUserGroup line, everything works fine.  This
account was set up just as every other account was, with the same
directory structure, ownerships and permissions, etc.  (Cookie-cutter;
everything's scripted.)

Any idea where I can determine what went wrong?  Thanks!

[ Post a follow-up to this message ]

On 5 Oct 2004 10:04:53 -0700, Wendell <ojailoop@yahoo.com> wrote:
> I have a bunch of virtual hosts that are all using the same virtual
> host definitions (a populated template created for each account),
> included using Apache 2.0's ability to do that.
>
> Most accounts/virtual hosts run CGIs (Perl) fine, with Suexec enabled.
>
> One, however, won't; all attempts to run CGIs fail with "Premature end
> of script header" recorded to error_log and no additional information.
>  Even running httpd -X with strace didn't shed any light.  If I
> comment out the SuexecUserGroup line, everything works fine.  This
> account was set up just as every other account was, with the same
> directory structure, ownerships and permissions, etc.  (Cookie-cutter;
> everything's scripted.)

What does suexec.log say?

Do any directories in path have more than 755 permission?

Sometimes a simple typo can trip you up (like "," in place of ".").

[ Post a follow-up to this message ]

efflandt@xnet.com (David Efflandt) wrote in message news:
> What does suexec.log say?
>
> Do any directories in path have more than 755 permission?
>
> Sometimes a simple typo can trip you up (like "," in place of ".").

D'oh.  Teach me to RTFM.  I've never used suexec before, and since all
of our virtualhosts have separate log definitions, I was looking
locally for clues.  The *system* (/usr/local/apache/logs) log
directory had suexec_log...

directory is writable by others

was the culprit.

Thanks!

What permissions / ownerships do people use for php in SAFE_MODE, and
SuExec for Perl?   Following up in a separate thread...

[ Post a follow-up to this message ]