500 "Server got itself in trouble"

[Alex Polite]

Most of my requests produce

500 Internal error
Server got itself in trouble.

There's no debugging information to stdout.
There's no debugging information to the server.logFile I've set.
I've also set "server.logTracebacks = True"

What's my next move?

alex

--
Alex Polite
http://flosspick.org - finding the right open source

[christian]

Alex Polite wrote:
> Most of my requests produce
>
> 500 Internal error
> Server got itself in trouble.
>
> There's no debugging information to stdout.
> There's no debugging information to the server.logFile I've set.
> I've also set "server.logTracebacks = True"
>
> What's my next move?

I imagine you are running in "production" mode. You could try
"development" mode to get tracebacks in the browser.

I'm not sure why logTracebacks isn't working for you. Can you try
running the following script on your machine and see if successfully
logs errors?
http://www.dowski.com/python/logtest.py

That script logs tracebacks on my system. Just visit
http://localhost:8080/anerror to trigger a 500 error. It should get
logged.

Maybe you could paste your config somewhere if that doesn't get you any
further.

HTH,

Christian
http://www.dowski.com

[Alex Polite]

On 9/10/05, christian <dowsk...@gmail.com> wrote:
>
> I imagine you are running in "production" mode. You could try
> "development" mode to get tracebacks in the browser.

You were right. Fixed that and got trace backs to both screen and
log file.

There error had was caused by changed sessions syntax. It's been fixed
and flosspick.org is once again operational.

Thanks for all the help.