Zine

How to enable logging/tracing

How to enable logging/tracing

From:
Alex Rampp
Date:
2010-01-20 @ 19:30
Subject:
How to enable logging/tracing
Hello,

I am just installing zine on my webserver and get the HTTP error 500 when I
call zine via mod_wsgi. Is there a posiblity to get logging or debug
information so that I get a detailed output of what went wrong?

Greets
Alex

Re: How to enable logging/tracing

From:
Armin Ronacher
Date:
2010-01-20 @ 19:59
Subject:
Re: How to enable logging/tracing
Hi,

Am 20.01.2010 20:30, schrieb Alex Rampp:
> Hello,
> 
> I am just installing zine on my webserver and get the HTTP error 500
> when I call zine via mod_wsgi. Is there a posiblity to get logging or
> debug information so that I get a detailed output of what went wrong?
If it's an Apache black/white 500 look into the server error log. If
it's blueish, look into the zine.log in your instance folder :)

If the 500 happens to be blue and you don't have an instance folder yet
it probably means that a library is missing.  We have to improve the
debugging stuff there so it either catches such problems or logs that
into the apache log.


Regards,
Armin

Re: How to enable logging/tracing

From:
Alex Rampp
Date:
2010-01-21 @ 21:00
Subject:
Re: How to enable logging/tracing
Hi,

the problem is: I have a linux web server with no root access (only a normal
user via ssh and ftp). mod_wsgi is activated and seems  to be working. I set
up a virtualenv for python and installed the dependencies for zine in this
virtualenv. But mod_wsgi uses the system wide python installation.
I also tried to append the lib directory of the virtualenv to the pythonpath
(sys.path.apped in zine.wsgi) but this did not work. It seems that the
system wide python does not use the egg files installed via easy_install.
I only can configure Apache via .htaccess but there I can not set the needed
mod_wsgi directives (e. g. WSGIPythonHome). Is there any possibilty to
install zine in such an environment?

2010/1/20 Armin Ronacher <armin.ronacher@active-4.com>

> Hi,
>
> Am 20.01.2010 20:30, schrieb Alex Rampp:
> > Hello,
> >
> > I am just installing zine on my webserver and get the HTTP error 500
> > when I call zine via mod_wsgi. Is there a posiblity to get logging or
> > debug information so that I get a detailed output of what went wrong?
> If it's an Apache black/white 500 look into the server error log. If
> it's blueish, look into the zine.log in your instance folder :)
>
> If the 500 happens to be blue and you don't have an instance folder yet
> it probably means that a library is missing.  We have to improve the
> debugging stuff there so it either catches such problems or logs that
> into the apache log.
>
>
> Regards,
> Armin
>

Re: How to enable logging/tracing

From:
Armin Ronacher
Date:
2010-01-23 @ 14:08
Subject:
Re: How to enable logging/tracing
Hi,

Am 21.01.2010 22:00, schrieb Alex Rampp:
> I only can configure Apache via .htaccess but there I can not set the
> needed mod_wsgi directives (e. g. WSGIPythonHome). Is there any
> possibilty to install zine in such an environment?
Sure.  I think you want to use a virtual environment there.  Download
the source tarball and run the make virtualenv script from the scripts
folder.


Regards,
Armin

Re: How to enable logging/tracing

From:
Alexander Rampp
Date:
2010-01-24 @ 18:08
Subject:
Re: How to enable logging/tracing
No it works. I had to unzip the .egg files by hand to make it work with
the global Python interpreter. Thanks for your help :-)