Thanks a lot, it works now!
Am 17.01.2017 um 16:45 schrieb Nate Coraor:
Hi Christopher,
It's been up for a while now. The IP address is now 128.118.250.24 -
is it still resolving to 128.118.250.10 for you?
--nate
On Mon, Jan 16, 2017 at 3:01 AM, Christopher Previti
Makis,
you need to run the downgrade command (sh manage_db.sh downgrade
--version=129) from the folder with the newer Galaxy. The old one does not
have the downgrading scripts.
Thanks for using Galaxy.
Martin
On Tue, Jan 17, 2017 at 7:33 AM Makis Ladoukakis
wrote:
>
Thanks Jelle,
now its running. I think matters where to put the conda statements
inside the galaxy.ini. It does not work if you put them at the end of
the file.
Cheers Jochen
On 17.01.2017 12:32, Jelle Scholtalbers wrote:
> Hi Jochen,
>
> generally updating the database shouldn't be an issue
Good morning Efthymios Ladoukakis
Yes I had this error and after repeated attempts if found out
sh manage_db.sh upgrade because your version is older than the current
releaase expects
You get a python vitural env error but
is fixed by running under sudo
sudo sh manage_db.sh
Try
Hello everyone,
I tried to download a newer version of Galaxy (I had 15.10 and pulled 16.01 in
a different directory) and now for some reason in my old working directory I
get the error:
Your database has version '133' but this code expects version '129'.
Please backup your database and
Hi Jochen,
generally updating the database shouldn't be an issue as this is handled by
the migration scripts that incrementally update your db schema to match the
version.
But I would do a backup just in case.
For the outdated ini files you can use the tool called Meld to spot
differences
Hi,
today we tried to update from 15.10 to 16.10 which included an update of
your database from 129 to 131.
Do we necessary run into problem if we update from an one year old
instance? How is the galaxy.ini updated? Or galaxy.ini does not know any
conda yet.
Thanks in advance.
Cheers Jochen