Hello again,
I have an update to the below question. I had made the mistake of forgetting the appropriate DB connection - Both systems are configured with scaling/load balancing as described here: http://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling However we have a differently named "universe_wsgi.ini" file for each process. So the "manage_db.sh" script was using the default one, and thus updating the SQLite DB. My mistake.
However after fixing this, the manage_db.sh scripts runs and produces the following error. Any input is appreciated. Thanks again Chris
--------------------------------------------------------------------- Traceback (most recent call last): File "./scripts/manage_db.py", line 55, in <module> main( repository=repo, url=db_url ) File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/shell.py", line 150, in main ret = command_func(**kwargs) File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/api.py", line 221, in upgrade return _migrate(url, repository, version, upgrade=True, err=err, **opts) File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/api.py", line 327, in _migrate changeset = schema.changeset(version) File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/schema.py", line 173, in changeset changeset = self.repository.changeset(database, start_ver, version) File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/repository.py", line 170, in changeset changes = [self.version(v).script(database, op) for v in versions] File "/var/www/galaxy/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/version.py", line 161, in script assert ret is not None AssertionError ---------------------------------------------------------------------
On Fri, Oct 15, 2010 at 1:44 PM, Chris Zaleski zaleski@cshl.edu wrote:
Greetings,
I hope you can help with a question. I have a local installation of Galaxy we've been using for production runs with a certain project. In order to maintain consistency, we haven't done any upgrades in about a year. We recently installed a fresh up-to-date Galaxy on another server. Now that those production runs are almost complete, we'd like to migrate the data/files/histories from the old server to the new one. All the configuration between the old & new servers is exactly the same (same DB, same login criteria, same directory structures, etc). Also there is no data on the new server - it's perfectly fine to clobber it. I intended to try the following procedure:
- Copy the file repository from old to new.
- Dump & import the database from old to new.
- Upgrade the database schema on the new server.
However the upgrade procedure is failing with no status. As expected, the log file reports the following: "Exception: Your database has version '43' but this code expects version '57'. Please backup your database and then migrate the schema by running 'sh manage_db.sh upgrade'." But the manage_db.sh script simply does nothing but run & exit. The database does not get upgraded & there's no output from the script. I tried the "verbose", "debug", and "force" flags, but nothing happens.
Should this work? If so, do you have any suggestions how to get the DB upgraded? If my migration procedure is incorrect, how should I go about it?
Thanks very much, Chris Zaleski