I'm running Fedora and set the ErrorLog directive in my VirtualHost
file to /var/log/httpd/web2py-error_log - but there is no error.  Just
the 303 code in the access_log.

My web2py directory is in /var/www/ and I have chown'd all files
apache:apache and chmod 777.  I still get the error.

I _can_  create the application manually, so, I agree, it sounds like
apache isn't able to write but how can that be the case if all the
files are owned by apache and have rwx permissions?  /var/www/web2py
is where web2py is installed and that's what's in my VirtualHost file.

Could it have something to do with HTTPS?  Here is my VirtualHost
file:

<VirtualHost *:8080>

        ServerName web2py.order-system.com
        WSGIDaemonProcess web2py user=apache group=apache
        WSGIProcessGroup web2py
        WSGIScriptAlias / /var/www/web2py/wsgihandler.py

        <Directory /var/www/web2py>
                AllowOverride None
                Order Allow,Deny
                Deny from all
                <Files wsgihandler.py>
                        Allow from all
                </Files>
        </Directory>

        AliasMatch ^/([^/]+)/static/(.*) /var/www/web2py/applications/$1/
static/$2

        <Directory /var/www/web2py/applications/*/static/>
                Order Allow,Deny
                Allow from all
        </Directory>

        <Location /admin>
                Deny from all
        </Location>

        <LocationMatch ^/([^/]+)/appadmin>
                Deny from all
        </LocationMatch>

        ErrorLog logs/web2py-error_log
        CustomLog logs/web2py-access_log common

</VirtualHost>

LoadModule ssl_module modules/mod_ssl.so
NameVirtualHost *:443
Listen 443

<VirtualHost *:443>

        ServerName web2py.order-system.com
        SSLEngine on
        SSLCertificateFile /etc/httpd/ssl/server.crt
        SSLCertificateKeyFile /etc/httpd/ssl/server.key

        WSGIProcessGroup web2py

        WSGIScriptAlias / /var/www/web2py/wsgihandler.py

        <Directory /var/www/web2py>
                AllowOverride None
                Order Allow,Deny
                Allow from all
                <Files wsgihandler.py>
                        Allow from all
                </Files>
        </Directory>

        AliasMatch ^/([^/]+)/static/(.*) /var/www/web2py/applications/$1/
static/$2

        <Directory /var/www/web2py/applications/*/static/>
                Order Allow,Deny
                Allow from all
        </Directory>

        ErrorLog logs/web2py-error_log
        CustomLog logs/web2py-access_log common

</VirtualHost>





On Mar 2, 11:25 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> These type of errors should be in /var/log/apach2/error.log
>
> It is either a permission issue or web2py is not running from the
> proper folder.
>
> On Mar 2, 12:13 pm, snfctech <tschm...@sacfoodcoop.com> wrote:
>
> > Fedora10 web2py1.76.1 apache2/mod_wsgi
>
> > I thought all errors generated tickets?  When I try to create an app
> > via the admin over HTTPS on a LAN all I get is an error flash "unable
> > to create application."  It's not an apache permission issue because
> > it does the same thing if all my files and dirs have 777 permissions.
> > I don't get any apache errors in the error log and the only funny
> > thing I get in the access log is a 303 code from the POST request to
> > admin/default/site.  Something must not be working out with
> > gluon.admin.app_create.
>
> > How should I troubleshoot this type of error, or does anybody have an
> > idea what's going on?
>
> > I'm going to start dissecting the app_create function - but my python
> > skills are still pretty weak and I was hoping there would just be a
> > good error log somewhere...
>
> > Thanks in advance for any tips.

-- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en.

Reply via email to