0.8.2 wsgi deployment - httpd.conf invalid command 'allow' error

MediaDrop Community » General Discussion & Feedback

0.8.2 wsgi deployment - httpd.conf invalid command 'allow' error

4 posts Started 13 years ago by aicm Latest reply from RobGoretsky

aicm
Member
Posted 13 years ago

Hello there,

I am using webfaction and have managed to pull and install the latest git release of 0.8.2. Everything is working fine, except deployment as wsgi. I have user level access, no root level, however I have a feeling that this isn't my problem.

I followed Apache & mod_wsgi Deployment guide and have added the necessary lines to httpd.conf however when trying to start apache, I get the following error:

Syntax error on line 49 of /home/aicm/webapps/mediacore_wsgi/apache2/conf/httpd.conf:
Invalid command 'Allow', perhaps misspelled or defined by a module not included in the server configuration

I don't know much about how apache works, but which one is the module needed to have apache understand Order, Allow and so on? I would think it's part of its core...

Here's what my httpd.conf looks like:

ServerRoot "/home/aicm/webapps/mediacore_wsgi/apache2"

LoadModule dir_module        modules/mod_dir.so
LoadModule env_module        modules/mod_env.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module       modules/mod_mime.so
LoadModule rewrite_module    modules/mod_rewrite.so
LoadModule setenvif_module   modules/mod_setenvif.so
LoadModule wsgi_module       modules/mod_wsgi.so

LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
CustomLog /home/aicm/logs/user/access_mediacore_wsgi.log combined
DirectoryIndex index.py
DocumentRoot /home/aicm/webapps/mediacore_wsgi/htdocs
ErrorLog /home/aicm/logs/user/error_mediacore_wsgi.log
KeepAlive Off
Listen 16225
MaxSpareThreads 3
MinSpareThreads 1
ServerLimit 1
SetEnvIf X-Forwarded-SSL on HTTPS=1
ThreadsPerChild 5
WSGIDaemonProcess mediacore_wsgi processes=5 python-path=/home/aicm/webapps/mediacore_wsgi/lib/python2.6 threads=1

<Directory /home/aicm/webapps/mediacore_wsgi/htdocs>
    AddHandler wsgi-script .py
</Directory>

# You can tweak the WSGIDaemonProcess directive for performance, but this
# will work for now.
# Relevant doc pages:
#     http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
#     http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIDaemonProcess
# Hint: pay attention to issues surrounding worker-mpm and prefork-mpm.

WSGIDaemonProcess mcore \
    threads=10 \
    display-name=%{GROUP} \
    python-path=/home/aicm/webapps/mediacore_wsgi/htdocs/9beta/lib/python2.5/site-packages \
    python-eggs=/home/aicm/webapps/mediacore_wsgi/htdocs/mediacore9beta/data/python-egg-cache

WSGIProcessGroup mcore

# Intercept all requests to /my_media/* and pass them to mediacore.wsgi
WSGIScriptAlias / /home/aicm/webapps/mediacore_wsgi/htdocs/mediacore9beta/deployment-scripts/mod_wsgi/mediacore.wsgi

# Make the url accessible (just in case it's not already)
<Location "/">
    Allow from all
</Location>

# Make the wsgi script accessible
<Directory /home/aicm/webapps/mediacore_wsgi/htdocs/mediacore9beta/deployment-scripts/mod_wsgi>
    Order allow,deny
    Allow from all
</Directory>

# Create exceptions for all static content
AliasMatch /(admin/)?(images|scripts|styles)(/?.*) /home/aicm/webapps/mediacore_wsgi/htdocs/mediacore9beta/mediacore/public/$1$2$3

# Make all the static content accessible
<Directory /home/aicm/webapps/mediacore_wsgi/htdocs/mediacore9beta/mediacore/public/*>
    Order allow,deny
    Allow from all
</Directory>

Obviously, there's two different WSGIDaemonProcess, one from webfaction and one from you. I have tried removing the first and leaving yours alone, but no go. I also tried commenting out mediacore WSGI statements but that didn't work either. So far, I have had 0 bright ideas.

My available modules inside /modules are:

mod_actions.so
 mod_alias.so
 mod_asis.so
 mod_auth_basic.so
 mod_auth_digest.so
 mod_authn_anon.so
 mod_authn_dbd.so
 mod_authn_dbm.so
 mod_authn_default.so
 mod_authn_file.so
 mod_authz_dbm.so
 mod_authz_default.so
 mod_authz_groupfile.so
 mod_authz_host.so
 mod_authz_owner.so
 mod_authz_user.so
 mod_autoindex.so
 mod_cern_meta.so
 mod_cgi.so
 mod_dav_fs.so
 mod_dav.so
 mod_dbd.so
 mod_deflate.so
 mod_dir.so
 mod_dumpio.so
 mod_env.so
 mod_expires.so
 mod_ext_filter.so
 mod_filter.so
 mod_headers.so
 mod_ident.so
 mod_imagemap.so
 mod_include.so
 mod_info.so
 mod_log_config.so
 mod_log_forensic.so
 mod_logio.so
 mod_mime_magic.so
 mod_mime.so
 mod_negotiation.so
 mod_reqtimeout.so
 mod_rewrite.so
 mod_setenvif.so
 mod_speling.so
 mod_status.so
 mod_substitute.so
 mod_unique_id.so
 mod_userdir.so
 mod_usertrack.so
 mod_version.so
 mod_vhost_alias.so
 mod_wsgi.so

Thank you for being willing to take a look at this.

Nathan Wright
Maintainer
Posted 13 years ago

It seems odd that the Allow command isn't working, but that might just be because you have limited permissions for configuring Apache. So the problem is not with the WSGI setup itself, it's telling Apache that it's allowed to read those files. It should start properly if you comment out the <Location> and both <Directory> blocks, but then you may get a 403 Forbidden error. Can you confirm this?
aicm
Member
Posted 13 years ago
Hello Nathan,

Thank you for taking the time to read my long post.

I have commented out <location> and <directory>.
```
Syntax error on line 59 of /home/aicm/webapps/mediacore_wsgi/apache2/conf/httpd.conf:
Invalid command 'AliasMatch', perhaps misspelled or defined by a module
not included in the server configuration
```
So I looked around for what provides Allow and Deny functionality. It's mod_access.so (which I tried to compile myself from apache2 source). And here's the interesting part: In apache 2.2 they renamed modules (why Apache, why?!) and mod_access.so is now mod_authz_host.so. Makes sense right? :) NOT.

Leaving that aside, apache starts properly but I get error 500 with the additions for mediacore. I'm sure it's something I did when it came to renaming /my_media to serve from / of that domain name. I think I saw that somewhere around here...

Thank you again for your help.

For search purposes:
mod_access.so provides Allow Order Deny functionality for Apache. If you are running Apache 2.2, make sure mod_authz_host.so is loaded, because that's the renamed mod_access.so.
RobGoretsky
Member
Posted 12 years ago

Just wanted to thank 'aicm' and Nathan for their posts - I found this when Googling for the same issue - . I found that I was hitting the same error, also when trying to configure MediaCore on WebFaction using mod_WSGI:
Syntax error on line 49 of /home/aicm/webapps/mediacore_wsgi/apache2/conf/httpd.conf: Invalid command 'Allow', perhaps misspelled or defined by a module not included in the server conf

The solution for me was to just add these lines directly under the other "LoadModule" lines in httpd.conf:
LoadModule authz_host_module modules/mod_authz_host.so LoadModule alias_module modules/mod_alias.so

I also commented out the WSGIDaemonProcess line that was created by WebFaction.. Then, I restarted Apache and everything worked!

RSS feed for this topic

Reply

You must log in to post.

Community Forums

0.8.2 wsgi deployment - httpd.conf invalid command 'allow' error

Reply