We're Hiring!

Upgrade from 5.0.2 to 5.1.3 with home-brew faild

Having a problem deploying OMERO? Please ask new questions at https://forum.image.sc/tags/omero
Please note:
Historical discussions about OMERO. Please look for and ask new questions at https://forum.image.sc/tags/omero

The OMERO.server installation documentation begins here and you can find OMERO.web deployment documentation here.

Re: Upgrade from 5.0.2 to 5.1.3 with home-brew faild

Postby Lipplab » Wed Aug 10, 2016 2:08 pm

Dear Sebastian,

thank yyou for your help. Sorry , I had someting to in the lab . I'm little bit late.
I got a question
is it a good idea to remove all omero versions? I would just run brew install omero.

Code: Select all
me-www:omero benjaminS$ brew remove omero
Error: omero has multiple installed versions
Use `brew uninstall --force omero` to remove all versions.
ome-www:omero benjaminS$ brew upgrade omero
Error: ome/alt/omero52 not installed
ome-www:omero benjaminS$ info brew remove

thanks Julia
Lipplab
 
Posts: 54
Joined: Thu Sep 12, 2013 9:56 am

Re: Upgrade from 5.0.2 to 5.1.3 with home-brew faild

Postby sbesson » Wed Aug 10, 2016 3:31 pm

Hi Julia,

in the general sense, removing old versions of the server should be safe once the configuration files and other files of interest have been copied. That being said, if you want to be on the safe side, you should be able to copy the entire content of the servers outside the Homebrew prefix before removing the remaining versions and re-installing the new version e.g.

Code: Select all
$ mkdir ~/OMERO.server-backups
$ cp -r usr/local/Cellar/omero/* ~/OMERO.server-backups/
$ brew uninstall --force omero
$ brew install omero


Best,
Sebastien
User avatar
sbesson
Team Member
 
Posts: 421
Joined: Tue Feb 28, 2012 7:20 pm

Re: Upgrade from 5.0.2 to 5.1.3 with home-brew faild

Postby Lipplab » Thu Aug 11, 2016 11:48 am

Dear Sebastien,

thank you a lot for your great support.
The update is fine.
Omero is running.
But I have one more question.

I've created a folder named omero_data_pic_extent on /Volumes/Drobo16TB to upload new files on the Drobo 16TB.
The managed Repository is on the /Volume/Drobo_Ex_02

I've configured the fs.omero path with
Code: Select all
bin/omero config set 'omero_data_pic_extent/%user%_%userID%//%year%-%month%/%day%/%time%'

and linked the folder with
Code: Select all
ln -s /Volumes/Drobo_Ex02/ /Volumes/Drobo16TB/omero_data_pic_extent/

and restarted the server.
Now I want to check, if the uploaded data are stored at /Volumes/Drobo16TB/omero_data_pic_extent/.
I recocnized that i don't actually see the data, but the space on the Drobo is used.
In the omero insight, the uploaded data exist.
My question is:
Is it working in the right way?
Thanks Julia
Last edited by Lipplab on Fri Aug 12, 2016 1:13 pm, edited 2 times in total.
Lipplab
 
Posts: 54
Joined: Thu Sep 12, 2013 9:56 am

Re: Upgrade from 5.0.2 to 5.1.3 with home-brew faild

Postby cblackburn » Fri Aug 12, 2016 9:51 am

Hi Julia,

As the upgrade issues are now resolved I have split the rest of the thread off under a different topic name, see https://www.openmicroscopy.org/community/viewtopic.php?f=5&t=8095

Cheers,

Colin
cblackburn
 
Posts: 85
Joined: Mon May 25, 2009 9:03 pm

Previous

Return to Installation and Deployment

Who is online

Users browsing this forum: No registered users and 1 guest