Thanks for responding!
I did a dump of the database and can see the new hostname in django_site.
However, the old hostname is littered through these tables:
changedescs_changedescription
hostingsvcs_hostingserviceaccount
reviews_comment
reviews_review
reviews_reviewrequest
Do I need to do a global searchreplace on old_host in those tables, too?
Also, here's the ssl_error_log entries I get when trying to load the site:
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] mod_wsgi (pid=1689):
SystemExit exception raised by WSGI script
'/var/www/reviews.siginnovations.com/htdocs/reviewboard.wsgi' ignored.
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] Traceback (most recent
call last):
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/core/handlers/wsgi.py,
line 187, in __call__
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165]
self.load_middleware()
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/core/handlers/base.py,
line 44, in load_middleware
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] for
middleware_path in settings.MIDDLEWARE_CLASSES:
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/conf/__init__.py,
line 54, in __getattr__
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] self._setup(name)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/conf/__init__.py,
line 49, in _setup
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] self._wrapped =
Settings(settings_module)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/conf/__init__.py,
line 128, in __init__
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] mod =
importlib.import_module(self.SETTINGS_MODULE)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/Django-1.6.7-py2.6.egg/django/utils/importlib.py,
line 40, in import_module
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] __import__(name)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.11-py2.6.egg/reviewboard/settings.py,
line 282, in module
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165]
dependency_error('Unable to import settings_local.py: %s' % exc)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] File
/usr/lib/python2.6/site-packages/ReviewBoard-2.0.11-py2.6.egg/reviewboard/settings.py,
line 235, in dependency_error
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] sys.exit(1)
[Fri Jan 23 16:38:02 2015] [error] [client 10.32.57.165] SystemExit: 1
I don't understand why it would be unable to import settings_local.py since the
absolute path to the site files has not changed.
And input helpful.
Thanks,
--Jamie
Jamie Gruener
Norton Street Business Services
www.nortonstreet.biz
ja...@nortonstreet.biz
main 919.688.1900
mobile 919.624.9760
skype jamie.gruener
www.facebook.com/nortonstreet
-Original Message-
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On
Behalf Of Stephen Gallagher
Sent: Thursday, January 15, 2015 8:40 AM
To: reviewboard@googlegroups.com
Subject: Re: Permanent Review Board is taking a nap after attempting a server
name change
On Wed, 2015-01-14 at 14:28 -0800, Jamie Gruener wrote:
I'm running ReviewBoard 2.11 on a CentOS 6.5 VM.
We recently changed our internal IP addresses and domain names. After
updating the DNS server and resolv.conf entries Review Board behaved
normally again.
Next I changed the ssl certificate and tried to update the site name.
That's when the real trouble started.
Where can I start looking to resolve this? I tried moving the folder
path to match the site name, changed permissions to allow apache
access to the moved folder, put it back, updated ALLOWED_HOSTS to
permit [*], a bunch of other things.
The site name is encoded in a number of places in the Review Board database.
It's non-trivial to change the public name of a Review Board deployment. After
it's already broken, you're probably going to need to get direct access to the
database and fix it up there.
At the least, you're going to need to change the value of the domain name in
the django_site table.
Running rb-site manage /my/site/path test ends with
pipeline.exceptions.CompilerError: /usr/bin/env: lessc: No such file
or directory
Running manage requires more stuff than the runtime, so you may need to do
'yum-builddep ReviewBoard' to pull it all in.
And yet easy_install django_pipeline tells me I have the current one
installed (1.3.24).
I don't want to have to
