Hi, On a Debian 7, with web2py 2.9.12-stable+timestamp.2015.02.13.23.31.09 (Running on Apache, Python 2.7.3) - WSGI with https
I have a problem I can't figure out. On a healthy instance of Web2PY, when an error occurs, we have an "Internal Error" message, and a Ticket Issued with a link pointing to the stack trace at the event of the crash. On my buggy instance, I have a different behavior when the app crashes or I just "raise Exception" in the code: - I have the Internal Error page with a "Ticket Issued: unknown" instead of the link to the stack trace that only admin has access to. - The error ticket is properly created, as it's available in the errors sub-folder. - I can see the error ticket, if I explicitly go to the "Errors" link on top of the page. - I also have the error trace in the Apache error.log. To reproduce the problem, just creating a single table app from the wizard triggers it. So it's not application dependent. I checked with the same Apache config file than the one I have on a working server. What can be wrong? What should I check? Thanks, François -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
