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 > 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 clean --all" to make sure I was > working with a fresh install. > > Cheers, > > -E > -Evan Bollig > Research Associate | Application Developer | User Support Consultant > Minnesota Supercomputing Institute > 599 Walter Library > 612 624 1447 > e...@msi.umn.edu > boll0...@umn.edu > > > On Fri, May 16, 2014 at 2:39 PM, Dannon Baker <dannon.ba...@gmail.com> > wrote: > > 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 a sense, hence all the other migration steps. Can you provide > > more details about your configuration? Postgres version, whether you're > > using a virtualenv (or not), or anything else you think seems relevant? > > > > -Dannon >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
