cgi scripts fail to run from userdir with "End of script output before headers" errors
Lonni J Friedman
netllama at gmail.com
Wed Oct 8 12:11:11 PDT 2014
That's correct, the script works just fine when in /var/www/cgi-bin.
mod_cgi is explicitly loaded.
I've attached my config files. userdir.conf & 01-cgi.conf are
included from httpd.conf.
On Wed, Oct 8, 2014 at 12:06 PM, David A. Bandel <david.bandel at gmail.com> wrote:
> Lonnie,
>
> OK, there must be a global configuration that's preventing this script from
> running. Can you post your entire config file? If you don't want to do
> that, I can provide an alternate means to pass it to me. Also, you said
> these run if you put them in your global cgi-bin directory, just not as a
> user, correct? So mod_cgi is loaded (please confirm).
>
> David-
>
> On Wed, Oct 8, 2014 at 12:34 PM, Lonni J Friedman <netllama at gmail.com>
> wrote:
>>
>> I saved the script in /home/netllama/public_html/cgi-bin/m.py, made it
>> executable for everyone, and ran it manually:
>>
>> [netllama at netllama cgi-bin]$ ./m.py
>> Content-Type: text/plain;charset=utf-8
>>
>> Hello World!
>>
>>
>> I then attempted to call it from firefox, and I saw another 500
>> Internal Server Error:
>> [Wed Oct 08 10:32:06.977104 2014] [cgi:error] [pid 26629] [client
>> 127.0.0.1:59320] End of script output before headers: m.py
>>
>>
>> I've already got the SetHandler in the config:
>> <Directory /home/*/public_html/cgi-bin>
>> AllowOverride Indexes AuthConfig
>> Options ExecCGI FollowSymLinks
>> SetHandler cgi-script
>> AddHandler cgi-script .py
>> </Directory>
>>
>> I'm using apache-2.4.10.
>>
>>
>> On Tue, Oct 7, 2014 at 7:26 PM, David A. Bandel <david.bandel at gmail.com>
>> wrote:
>> > Lonnie,
>> >
>> > Phew -- yep, this is why I hate this error.
>> >
>> > Try this:
>> > /----start of script----/
>> > #!/usr/bin/env python
>> > # -*- coding: UTF-8 -*-
>> >
>> > # enable debugging
>> > import cgitb
>> > cgitb.enable()
>> >
>> > print "Content-Type: text/plain;charset=utf-8"
>> > print
>> >
>> > print "Hello World!"
>> >
>> > ----/end of script/----
>> >
>> > Your script and this one (call it test.py) should both be executable,
>> > owned
>> > by the same user, and in the user's cgi-bin directory.
>> >
>> > Ensure you can run both from the command line, then try to run them in
>> > apache by connecting with a browser.
>> >
>> > If test.py works, but your foo.py script doesn't, the problem is in your
>> > foo.py script. Make sure your script is outputting a content-type line
>> > (see
>> > above).
>> >
>> > If the test.py does not work, we have a configuration issue.
>> >
>> > Could also add a "SetHandler: cgi-script" to your cgi-directory stanza.
>> >
>> > BTW: which version of apache? 2.2 or 2.4 (some declarations changed
>> > between
>> > these two version numbers)
>> >
>> >
>> > David-
>> >
>> >
>> > On Tue, Oct 7, 2014 at 6:17 PM, Lonni J Friedman <netllama at gmail.com>
>> > wrote:
>> >>
>> >> I definitely have suexec enabled:
>> >> [Mon Oct 06 16:09:31.518777 2014] [suexec:notice] [pid 20128] AH01232:
>> >> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>> >>
>> >> Renaming the suexec binary, and retrying didn't really help:
>> >> [Tue Oct 07 16:17:15.854011 2014] [cgi:error] [pid 26631] [client
>> >> 127.0.0.1:55657] AH01215: (2)No such file or directory: exec of
>> >> '/usr/sbin/suexec' failed
>> >> [Tue Oct 07 16:17:15.854671 2014] [cgi:error] [pid 26631] [client
>> >> 127.0.0.1:55657] End of script output before headers: foo.py
>> >>
>> >> I added a handler to the "<Directory /home/*/public_html/cgi-bin>"
>> >> section of my apache config, but that didn't have any impact on the
>> >> problem.
>> >>
>> >> Any other suggestions?
>> >>
>> >>
>> >> On Tue, Oct 7, 2014 at 6:28 AM, David A. Bandel
>> >> <david.bandel at gmail.com>
>> >> wrote:
>> >> > Lonnie,
>> >> >
>> >> > With or without suexec, you will need a handler line:
>> >> > AddHandler cgi-script .cgi .py
>> >> > (make sure the above line has the pertinent extension, like .py and
>> >> > your
>> >> > python script ends in .py)
>> >> >
>> >> > If using suexec, you should see a line in your error_log:
>> >> > suEXEC mechanism enabled
>> >> >
>> >> > Your script must be runable by suEXEC user. You might find it
>> >> > easier
>> >> > to
>> >> > disable suexec (unless you need it). Just rename the suexec script
>> >> > and
>> >> > restart apache and test. If you the script works but you need suexec
>> >> > (because you're going to have lots of users that need to run CGI
>> >> > scripts),
>> >> > then you'll need to troubleshoot the suexec mess.
>> >> >
>> >> > David-
>> >> >
>> >> > On Mon, Oct 6, 2014 at 8:55 PM, Lonni J Friedman <netllama at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi David,
>> >> >> I was actually leaning towards some kind of apache configuration
>> >> >> issue, but clearly i'm not the expert here, or I would have figured
>> >> >> it
>> >> >> out myself :)
>> >> >>
>> >> >> To answer your questions:
>> >> >> Its a python script that I'm trying to run.
>> >> >> $HOME is on the same partition as / (which is the same partition as
>> >> >> the apache $DOCROOT). Its all on a development system, not anything
>> >> >> resembling production.
>> >> >> The user's UID is greater than 1000.
>> >> >> I am using suexec.
>> >> >>
>> >> >> I'd be happy to answer any other questions.
>> >> >>
>> >> >> thanks
>> >> >>
>> >> >>
>> >> >> On Mon, Oct 6, 2014 at 6:45 PM, David A. Bandel
>> >> >> <david.bandel at gmail.com>
>> >> >> wrote:
>> >> >> > Lonnie,
>> >> >> >
>> >> >> > This is one of the most annoying, frustrating errors. All it says
>> >> >> > is
>> >> >> > that
>> >> >> > the script didn't work. This may be permissions. It may be your
>> >> >> > $HOME
>> >> >> > mount is non-executable. Difficult to say. You didn't say what
>> >> >> > kind
>> >> >> > of
>> >> >> > script it was (Perl, PHP, shell). Is the UID of the user greater
>> >> >> > than
>> >> >> > 1000?
>> >> >> > Are you using suexec?
>> >> >> >
>> >> >> > I hate this error. Will be either one of the permissions issues
>> >> >> > above
>> >> >> > or
>> >> >> > some Apache configuration issue (I'm betting on permissions).
>> >> >> >
>> >> >> > David-
>> >> >> >
>> >> >> > On Mon, Oct 6, 2014 at 5:57 PM, Lonni J Friedman
>> >> >> > <netllama at gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Howdy folks,
>> >> >> >> Any cgi/apach experts still around? I'm trying to get cgi
>> >> >> >> scripts
>> >> >> >> working from $USERDIR on a new Fedora system, and they all fail
>> >> >> >> with
>> >> >> >> internal server errors. In the apache error log, I see:
>> >> >> >> [cgi:error] End of script output before headers
>> >> >> >>
>> >> >> >> If I copy the script over to the server $DOCROOT/cgi-bin then it
>> >> >> >> runs
>> >> >> >> just fine. So this proves the script itself isn't the problem.
>> >> >> >> Additionally, non-cgi scripts are served just fine from $USERDIR.
>> >> >> >> Both the cgi-bin directory and the script itself are executable
>> >> >> >> for
>> >> >> >> all users (755). This is what I've got set in the apache config
>> >> >> >> for
>> >> >> >> the USERDIR directory structure:
>> >> >> >>
>> >> >> >> <Directory "/home/*/public_html">
>> >> >> >> AllowOverride FileInfo AuthConfig Limit Indexes
>> >> >> >> Options MultiViews Indexes SymLinksIfOwnerMatch ExecCGI
>> >> >> >> Require method GET POST OPTIONS
>> >> >> >> </Directory>
>> >> >> >>
>> >> >> >> <Directory /home/*/public_html/cgi-bin>
>> >> >> >> AllowOverride Indexes AuthConfig
>> >> >> >> Options ExecCGI
>> >> >> >> SetHandler cgi-script
>> >> >> >> </Directory>
>> >> >> >>
>> >> >> >>
>> >> >> >> Anyone know what I'm missing?
>> >> >> >>
>> >> >> >> thanks
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >> >> L. Friedman netllama at gmail.com
>> >> >> LlamaLand http://netllama.linux-sxs.org
>> >> >> _______________________________________________
>> >> >> Linux-users mailing list
>> >> >> Linux-users at linux-sxs.org
>> >> >> http://mailman.celestial.com/mailman/listinfo/linux-users
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Two things are infinite: the universe and human stupidity; and I'm
>> >> > not
>> >> > sure
>> >> > about the the universe. -- Albert Einstein
>> >> > Visit my web page at: http://david.bandel.us/
>> >> >
>> >> > _______________________________________________
>> >> > Linux-users mailing list
>> >> > Linux-users at linux-sxs.org
>> >> > http://mailman.celestial.com/mailman/listinfo/linux-users
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >> L. Friedman netllama at gmail.com
>> >> LlamaLand http://netllama.linux-sxs.org
>> >> _______________________________________________
>> >> Linux-users mailing list
>> >> Linux-users at linux-sxs.org
>> >> http://mailman.celestial.com/mailman/listinfo/linux-users
>> >
>> >
>> >
>> >
>> > --
>> > Two things are infinite: the universe and human stupidity; and I'm not
>> > sure
>> > about the the universe. -- Albert Einstein
>> > Visit my web page at: http://david.bandel.us/
>> >
>> > _______________________________________________
>> > Linux-users mailing list
>> > Linux-users at linux-sxs.org
>> > http://mailman.celestial.com/mailman/listinfo/linux-users
>> >
>>
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> L. Friedman netllama at gmail.com
>> LlamaLand http://netllama.linux-sxs.org
>> _______________________________________________
>> Linux-users mailing list
>> Linux-users at linux-sxs.org
>> http://mailman.celestial.com/mailman/listinfo/linux-users
>
>
>
>
> --
> Two things are infinite: the universe and human stupidity; and I'm not sure
> about the the universe. -- Albert Einstein
> Visit my web page at: http://david.bandel.us/
>
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> http://mailman.celestial.com/mailman/listinfo/linux-users
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama at gmail.com
LlamaLand http://netllama.linux-sxs.org
-------------- next part --------------
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache
# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#
#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin at your-domain.com
#
ServerAdmin root at localhost
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80
#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"
#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride None
# Allow open access:
Require all granted
</Directory>
# Further relax access to the default document root:
<Directory "/var/www/html">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>
#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog "logs/access_log" common
#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
</IfModule>
#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/mime.types
#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
AddHandler cgi-script .cgi .py
# AddHandler cgi-script .py
# For type maps (negotiated resources):
#AddHandler type-map var
#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
</IfModule>
#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8
<IfModule mime_magic_module>
#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
MIMEMagicFile conf/magic
</IfModule>
#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#
#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on
# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
-------------- next part --------------
#
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
#
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid. This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
#
<IfModule mod_userdir.c>
#
# UserDir is disabled by default since it can confirm the presence
# of a username on the system (depending on home directory
# permissions).
#
#UserDir disabled
#
# To enable requests to /~user/ to serve the user's public_html
# directory, remove the "UserDir disabled" line above, and uncomment
# the following line instead:
#
UserDir public_html
</IfModule>
#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
<Directory "/home/*/public_html">
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch ExecCGI
Require method GET POST OPTIONS
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# AllowOverride AuthConfig Limit FileInfo
</Directory>
<Directory /home/*/public_html/cgi-bin>
AllowOverride Indexes AuthConfig
Options ExecCGI FollowSymLinks
SetHandler cgi-script
AddHandler cgi-script .py
# Allow from all
</Directory>
-------------- next part --------------
# This configuration file loads a CGI module appropriate to the MPM
# which has been configured in 00-mpm.conf. mod_cgid should be used
# with a threaded MPM; mod_cgi with the prefork MPM.
<IfModule mpm_worker_module>
LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
LoadModule cgi_module modules/mod_cgi.so
</IfModule>
More information about the Linux-users
mailing list