Hey Dannon,
I managed to resolve this on my own.
The postgres version is 9.1, and I'm on Ubuntu 12.04. The instance is
an OpenStack VM. It turned out that the dir contained files that were
outdated from a previous version of galaxy-dist. After I realized that
they were part of hgignore, I ran hg
Ok, great, glad you're up and running! I'll scratch this one off the list
of things to think about.
On Mon, May 19, 2014 at 4:00 PM, Evan Bollig boll0...@umn.edu wrote:
Hey Dannon,
I managed to resolve this on my own.
The postgres version is 9.1, and I'm on Ubuntu 12.04. The instance is
I have an empty posgresql database:
psql -c create database galaxy;
I'm trying to launch run.sh from the latest version of galaxy-dist.
Migration proceeds normally up to this point:
#
galaxy.model.migrate.check INFO 2014-05-16 19:11:17,121
galaxy.model.migrate.check INFO 2014-05-16
On Fri, May 16, 2014 at 3:33 PM, Evan Bollig boll0...@umn.edu wrote:
InvalidVersionError: 103 is not 105
This would indicate to me that migration script 104 failed.
My question is: why can't the manage_db.sh upgrade step be included
automatically when the initial DB build fails?
It is, in
