[gentoo-user] Re: Eeek: Apache2 lost it's CGI ability
Kevin O'Gorman kogorman at gmail.com writes: But this much I know: The permissions on the failing (python) script are the same. So are the owner and group. The python script runs fine from the command-line, even as an other user. Hello Kevin, 2 things. Have your run 'python-updater' since your last update of python and such? Or you just may need to rebuild some of the modules you use with apache? (revdep-rebuild -p). A while back, much change with the Apache config files. Even now some of them, related to php, python and such get modified even with minor revision updates of Apache and related packages. I always save out old.dated config files to remind me of what I had set. A while back the organization of some of the apache related config files changes. Look over them to see that you have everything set the way it needs to be. (just a thought). Good luck, James
[gentoo-user] Re: Eeek: Apache2 lost it's CGI ability
Kevin O'Gorman kogor...@gmail.com writes:
I don't get much help from the logs. The access log shows that the
request got an error code,
64.166.164.49 - - [15/Feb/2009:15:46:32 -0800] GET /hex-bin/board
HTTP/1.1 500 542
and all that the error log says is:
[Sun Feb 15 15:46:32 2009] [error] [client 64.166.164.49] Premature
end of script headers: board
Any idea how to debug this, or any intuitions about what I neglected to do?
Well a few things come to mind. Test the script by hand first.
Check the permissions are 755 or the like.
Test a very simple cgi that is known to work.
Here is a simple one... make sure it has chmod 755
--- 8 snip --- 8 snip
#!/usr/bin/perl
print Content-type: text/html\n\n;
print REMOTE_ADDR = $ENV{REMOTE_ADDR}BR \n;
Re: [gentoo-user] Re: Eeek: Apache2 lost it's CGI ability
On Sun, Feb 15, 2009 at 4:44 PM, Harry Putnam rea...@newsguy.com wrote:
Kevin O'Gorman kogor...@gmail.com writes:
I don't get much help from the logs. The access log shows that the
request got an error code,
64.166.164.49 - - [15/Feb/2009:15:46:32 -0800] GET /hex-bin/board
HTTP/1.1 500 542
and all that the error log says is:
[Sun Feb 15 15:46:32 2009] [error] [client 64.166.164.49] Premature
end of script headers: board
Any idea how to debug this, or any intuitions about what I neglected to do?
Well a few things come to mind. Test the script by hand first.
Check the permissions are 755 or the like.
Test a very simple cgi that is known to work.
Here is a simple one... make sure it has chmod 755
--- 8 snip --- 8 snip
#!/usr/bin/perl
print Content-type: text/html\n\n;
print REMOTE_ADDR = $ENV{REMOTE_ADDR}BR \n;
This is wonderful. Thanks. Your cgi script worked just fine. I put
it in the same directory,
called it 'cgi.perl', and made the permissions 755. It ran just fine.
So I guess apache is fine.
Having something simple that works is a great help in figuring out
what is actually broken.
I've got a meeting to go to, so I'll have to get back to it.
But this much I know:
The permissions on the failing (python) script are the same. So are
the owner and group.
The python script runs fine from the command-line, even as an other user.
Next thing: I'll make a python version of your program and work up from there.
--
Kevin O'Gorman, PhD
Re: [gentoo-user] Re: Eeek: Apache2 lost it's CGI ability
On Sun, Feb 15, 2009 at 5:23 PM, Kevin O'Gorman kogor...@gmail.com wrote:
On Sun, Feb 15, 2009 at 4:44 PM, Harry Putnam rea...@newsguy.com wrote:
Kevin O'Gorman kogor...@gmail.com writes:
I don't get much help from the logs. The access log shows that the
request got an error code,
64.166.164.49 - - [15/Feb/2009:15:46:32 -0800] GET /hex-bin/board
HTTP/1.1 500 542
and all that the error log says is:
[Sun Feb 15 15:46:32 2009] [error] [client 64.166.164.49] Premature
end of script headers: board
Any idea how to debug this, or any intuitions about what I neglected to do?
Well a few things come to mind. Test the script by hand first.
Check the permissions are 755 or the like.
Test a very simple cgi that is known to work.
Here is a simple one... make sure it has chmod 755
--- 8 snip --- 8 snip
#!/usr/bin/perl
print Content-type: text/html\n\n;
print REMOTE_ADDR = $ENV{REMOTE_ADDR}BR \n;
This is wonderful. Thanks. Your cgi script worked just fine. I put
it in the same directory,
called it 'cgi.perl', and made the permissions 755. It ran just fine.
So I guess apache is fine.
Having something simple that works is a great help in figuring out
what is actually broken.
I've got a meeting to go to, so I'll have to get back to it.
But this much I know:
The permissions on the failing (python) script are the same. So are
the owner and group.
The python script runs fine from the command-line, even as an other user.
Next thing: I'll make a python version of your program and work up from there.
--
Kevin O'Gorman, PhD
Update: still broken, but the broken piece seems to be my use of the
gettext package,
not apache. My translated message strings are still there, but
something is erroring
out when run under apache that works okay when run from the command line.
I'll sleep on it.
--
Kevin O'Gorman, PhD
