stock Loggerhead provides no useful error information when exceptions hit the top of the wsgi stack - instead Internal Server Error" is shown

[Russel Winder]

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-branches.conf and serve-branches gets started via the init script. However on alighting at the Loggerhead page, I just get "Internal Server Error". The logs for Loggerhead have no explanatory information, so you end up having to divine what is wrong using runes and tea leaves ;-)

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.

[Ketil Vestby (ketil-vestby)]

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.