Re: Clean install of 1.6.1 serves up 404 error
Anton, you're correct, I'm using the SLES 11 SP1 Apache pretty much out of the box (but with the PHP, Python, Perl and Env modules enabled) and those settings came from apache2ctl (an alias for httpd?) -S -M . Sorry, Christian, should've been clearer about where they came from. Anton, I've moved the reviewboard.test.com.conf file from /etc/apache2/conf.d/ to /etc/apache2/vhosts.d/ where it obviously should be. I don't think that's made a difference though, httpd was clearly still correctle registering the virtual host. The Apache error_log is registering the following errors: [Thu Sep 22 04:39:55 2011] [error] [client 134.244.156.17] client denied by server configuration: /var/www/reviewboard.test.com/htdocs/ [Thu Sep 22 13:08:44 2011] [error] [client 134.244.156.17] client denied by server configuration: /var/www/reviewboard.test.com/htdocs/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] client denied by server configuration: /var/www/reviewboard.test.com/htdocs/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 14:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/djblets, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/djblets, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 14:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/djblets, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:04 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ [Thu Sep 22 06:17:06 2011] [error] [client 134.244.156.17] Symbolic link not allowed or link target not accessible: /var/www/ reviewboard.test.com/htdocs/media/rb, referer: http://cpli6011.net.plm.eds.com/ Which, was sufficiently instructive that I managed to fix the issue by adding the bold lines to my reviewboard conf file: Directory /var/www/reviewboard.test.com/htdocs AllowOverride All *Options -Indexes FollowSymLinks **Allow from all* /Directory Anton, Christian, thanks for the help, I now have a new issue :) but I'll start another thread for that. Sandeep On Fri, Sep 23, 2011 at 4:10 AM, Anton Cohen an...@antoncohen.com wrote: On Thu, Sep 22, 2011 at 4:31 PM, Christian Hammond chip...@chipx86.com wrote: The logs keep referencing this HTTP_FORBIDDEN.html.var. This is not provided by us or by any listed config. There are at least 16 other .conf files included in the config. SUSE might have taken the idea of modular configs a little too far. My hunch is that this is somehow related to you having compiled your own Apache. Fortunately, I think he is using the version shipped with SLES 11, the settings probably came from something like httpd -V. Sandeep, Can you look at or provide the apache error logs, they are probably in /var/log/apache2. They should list what is causing the error. According to the httpd.conf provided, on SLES virtual host files belong in /etc/apache2/vhosts.d/. Try moving reviewboard.test.com.conf to /etc/apache2/vhosts.d/. -Anton -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at
Upgrading database/site from 1.0 to 1.6.1
Okay, so I have a shiny, new, *working*,* *instance of Reviewboard 1.6.1.
and my plan to migrate my data from my old site was to run rb-site upgrade
on the old site and then copy the newly upgraded database to the new site.
Unfortunately, the database still seem to have a certain amount of 1.0ness
to it and it spat back the Manual server updates required Review Board
page attached. The only thing I did apart from copy over the database was to
change the SECRET_KEY in /conf/settings_local.py. What have I missed? Or am
I going about this all wrong?
I also thought I might as well see the carnage that ensued if I tried to
just get the upgraded old site running and, sure enough, I get a 500 Error
back with the attached Apache error_log.
As always, your help and time are much appreciated,
Sandeep
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en[Fri Sep 23 13:43:45 2011] [crit] [client 134.244.156.17] (13)Permission
denied: /var/www/reviewboard.test.com/htdocs/.htaccess pcfg_openfile: unable to
check htaccess file, ensure it is readable
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] mod_python
(pid=29883, interpreter='reviewboard_reviewboard_test_com',
phase='PythonHandler', handler='django.core.handlers.modpython'): Application
error
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] ServerName:
'cpli6011.net.plm.eds.com'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] DocumentRoot:
'/var/www/reviewboard.test.com/htdocs'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] URI:
'/error/HTTP_FORBIDDEN.html.var'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Location: '/'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Directory: None
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Filename:
'/usr/share/apache2/error/HTTP_FORBIDDEN.html.var'
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] PathInfo: ''
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] Traceback (most
recent call last):
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1537, in
HandlerDispatch\ndefault=default_handler, arg=req, silent=hlist.silent)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1229, in
_process_target\nresult = _execute_target(config, req, object, arg)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/lib64/python2.6/site-packages/mod_python/importer.py, line 1128, in
_execute_target\nresult = object(arg)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/modpython.py,
line 212, in handler\nreturn ModPythonHandler()(req)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/modpython.py,
line 174, in __call__\nself.load_middleware()
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/base.py,
line 39, in load_middleware\nfor middleware_path in
settings.MIDDLEWARE_CLASSES:
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/utils/functional.py,
line 276, in __getattr__\nself._setup()
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/conf/__init__.py,
line 42, in _setup\nself._wrapped = Settings(settings_module)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/conf/__init__.py,
line 87, in __init__\nmod = importlib.import_module(self.SETTINGS_MODULE)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/utils/importlib.py,
line 35, in import_module\n__import__(name)
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/settings.py,
line 163, in module\ndependency_error('Unable to read
settings_local.py.')
[Fri Sep 23 13:43:45 2011] [error] [client 134.244.156.17] File
/usr/local/lib64/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/settings.py,
line 150, in dependency_error\nsys.exit(1)
[Fri Sep 23 13:43:45
Re: Upgrading database/site from 1.0 to 1.6.1
By the way, the old site used an SQLite backend. I was going to get access to the legacy code reviews by having an SQLite site alongside the production MySQL site that we'll use going forwards. I notice that We don’t * officially* support converting a database from SQLite to other databases. How about unofficially? Could I get around my problems by importing my data from my 1.0 SQLite db into a 1.6.1 MySQL db? On Fri, Sep 23, 2011 at 3:00 PM, Sandeep Tailor s.tai...@insysion.netwrote: Okay, so I have a shiny, new, *working*,* *instance of Reviewboard 1.6.1. and my plan to migrate my data from my old site was to run rb-site upgrade on the old site and then copy the newly upgraded database to the new site. Unfortunately, the database still seem to have a certain amount of 1.0ness to it and it spat back the Manual server updates required Review Board page attached. The only thing I did apart from copy over the database was to change the SECRET_KEY in /conf/settings_local.py. What have I missed? Or am I going about this all wrong? I also thought I might as well see the carnage that ensued if I tried to just get the upgraded old site running and, sure enough, I get a 500 Error back with the attached Apache error_log. As always, your help and time are much appreciated, Sandeep -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
