stock Loggerhead provides no useful error information when exceptions hit the top of the wsgi stack - instead Internal Server Error" is shown
Bug #611603 reported by
Russel Winder
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loggerhead |
Triaged
|
Low
|
Unassigned | ||
loggerhead-breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
I am trying to set up Loggerhead (due to my server dying and having to lash up a quasi replacement pending getting a new one).
I have set up a viable /etc/serve-
In the end I found that there was a directory in the path that was not accessible to user loggerhead, fixed that fixed the problem, but it was pure guess work -- the error reporting by Loggerhead was just not good enough.
Changed in loggerhead: | |
status: | New → Triaged |
importance: | Undecided → Low |
summary: |
- Loggerhead provides no useful error information for "Internal Server - Error" + stock Loggerhead provides no useful error information when exceptions + hit the top of the wsgi stack - instead Internal Server Error" is shown |
Changed in loggerhead-breezy: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
If at least a little hint about how to make Loggerhead log errors in Ubuntu could be placed in /usr/share/ doc/loggerhead, it would be a great step forward. The command "sudo start-loggerhead -f" shown in http:// happypixels. com/blog/ setting- loggerhead- ubuntu do not apply to the latest versions of Ubuntu, so I'm just as lost as Russel Winder was when reporting this bug.