Verbose Debug Info?

[ddu...@aviationintertec.com]

Installing Review Board for the first time and can't get past a "500 - Internal Server Error" page on start up. I followed all of the set up instructions from the webpage,checked to make sure that Apache is using wsgi, and confirmed that the username and password I gave ReviewBoard work correctly with PostgresSQL.

Is there a way to enable logging from the command line? Or at least get more verbose debugging info? As of right now Review Board is not writing any log files, and there are no errors in the Apache log file, so I have no leads on how to fix this problem.

Installation Info
Ubuntu 16.04.3 LTS
Apache 2.4.18
PostgreSQL 9.5.9
rb-site 2.5.16
Python 2.7.12

[Christian Hammond]

Hi,

It's not normal on an Ubuntu install to hit a 500 error like this. If you're seeing a 500 this early, it's usually something failing before any requests even get to Review Board. These might appear in the apache error_log in the Review Board site directory's logs/ directory, or maybe in Apache's main error_log in /var/logs. Start by checking those and see if you can find anything that stands out.

Is this server being used for any other web services?

Christian

--
Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Christian Hammond

President/CEO of Beanbag

Makers of Review Board

[ddu...@aviationintertec.com]

Hi Christian,

Thank you for the reply.

There is no log being generated in the Review Board folder, but I did see something I hadn't noticed before in the apache log:

[Thu Oct 05 06:25:03.401752 2017] [wsgi:warn] [pid 17317:tid 140477232400256] mod_wsgi: Compiled for Python/2.7.11.
[Thu Oct 05 06:25:03.401833 2017] [wsgi:warn] [pid 17317:tid 140477232400256] mod_wsgi: Runtime using Python/2.7.12.
[Thu Oct 05 06:25:03.401988 2017] [mpm_event:notice] [pid 17317:tid 140477232400256] AH00489: Apache/2.4.18 (Ubuntu) mod_wsgi/4.3.0 Python/2.7.12 configured -- resuming normal operations
[Thu Oct 05 06:25:03.402013 2017] [core:notice] [pid 17317:tid 140477232400256] AH00094: Command line: '/usr/sbin/apache2'
[Thu Oct 05 19:42:51.964780 2017] [wsgi:error] [pid 29333:tid 140477126346496] No handlers could be found for logger "djblets.log.middleware"

I looked through the djblets.log.middleware documentation on the review board site but couldn't find anything about handlers. Have you seen this error before? If so what steps were needed to solve it?

Thank you for your time,
David

To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[ddu...@aviationintertec.com]

Forgot to mention in last message: I talked it over with my supervisor and, to the best of our knowledge, there are no other Web Services running on that server.

[Christian Hammond]

That log-related message is harmless, but interesting. It does mean it's reaching Review Board code.

This is generally not something you'll want to turn on unless advised by us, but in your $sitedir/conf/settings_local.py, set:

    DEBUG = True

Then restart Apache and load the page. See if you get a more detailed error.

After we resolve this, you'll want to set DEBUG back to False. This actually changes a lot of behavior and makes your install slower and less secure.

Christian

To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[ddu...@aviationintertec.com]

Now this is interesting.

When I set DEBUG to True I can actually access the Review Board site, or at least I no longer got the 500 error. Going to the apache log reveals that the original error message has changed to:

[Fri Oct 06 13:40:51.039585 2017] [core:error] [pid 45622:tid 140492367812352] [client 192.168.10.154:53661] AH00037: Symbolic link not allowed or link target not accessible: /var/www/reviewboard/htdocs/static/djblets, referer: http://reviewboard/r/

It repeats this message dozens of times. Looking at the details of the folder /var/www/reviewboard/htdocs/static revealed:

lrwxrwxrwx 1 root     root       70 Oct  3 14:04 admin -> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/admin
lrwxrwxrwx 1 root     root       78 Oct  3 14:04 djblets -> /home/me/.local/lib/python2.7/site-packages/djblets/htdocs/static/djblets
drwxr-xr-x 2 www-data www-data 4096 Oct  3 14:04 ext
lrwxrwxrwx 1 root     root       68 Oct  3 14:04 lib -> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/lib
lrwxrwxrwx 1 root     root       67 Oct  3 14:04 rb -> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/rb

Pip was installing to my local directory, not /usr/local/lib/. I checked and it turns out the my $PYTHONPATH variable was not set up. To resolve this:

1. Removed Review Board
2. Set up $Pythonpath in my my .bashrc
3. Logged out, then logged back in
4. Installed djblets using pip
5. Re-installed Review Board

Originally I removed Djblets from my local directory, but this caused Review Board installation to fail. For some reason Review Board was still verifying the existence Djblets in my local folder. Despite that, after setting up Review Board again the symbolic link was pointing to /usr/local/lib.

Review Board is now working as expected.

Thank you for your help! Without that debug info I never would have been able to reach this next step.

Have a good one,

David