Anyone have any further suggestions on how to debug 'ReviewBoard is
taking a nap' after a fresh install? Maybe there are some diagnostics
I can run on my reviewboard site instance using rb-site manage or
shell?
I've tried validate and test, results are below (there was a problem
running test)
Hi Daniel,
I've been on vacation, so I'm just now reading this.
The test command won't work on an installed site. It requires a development
checkout.
I'd recommend editing your site's conf/settings_local.py and setting DEBUG
to True (note the capital 'T'). Then restart your web server and see
I'm just installed rc 1.5 and I'm getting the same message. I tried
the following so far
* enable debug but get the same screen no log files created in
project-root/logs
* changed permissions of project/media/uploaded
I'm running centos 5.4, python 2.6, mod_wsgi, mod_python, sqlite3, and
Glad you got it working, Eric!
I've updated the docs to make this more clear, and they'll appear on the
website during the docs refresh in a couple hours.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On
Hi (me again),
I have all my dependency issues sorted, and I've installed my first
Review Board site per the documentation.
When I go to visit the site, I see the 'Review Board is taking a nap'
dialog box.
In my Apache error_log, I see some errors:
[error] [client 127.0.0.1] mod_python
I've yet to do an install like that, and someone else may correct me, but
normally that message means that the apache user does not have write access
to bothr the sqlite file and the folder that contains it.
Try tracking that down and changing the permissions/owner.
--Jeff
2009/6/25 Eric P
I actually ran rb-site w/o those params. I just wanted to convey that
info (should've done it another way).
I gave web server ownership to the 'db' directory (running sqlite3)
and its content, and that did the trick. Thanks! That step should
probably be added to the docs for those who use
Not sure about what you are seeing in the logs because I did not look
at my logs. But I was getting that error when SELinux was enabled.
Try turning off SELinux.
On Jun 25, 12:34 pm, Eric P eric.maill...@gmail.com wrote:
Hi (me again),
I have all my dependency issues sorted, and I've
Yep, I did that as well while I was trying to get this all working.
Thanks,
Eric
On Thu, Jun 25, 2009 at 1:18 PM, grimbeavertbrez...@gmail.com wrote:
Not sure about what you are seeing in the logs because I did not look
at my logs. But I was getting that error when SELinux was enabled.
Try
