Migrating from old (5.1.2) to latest version: the safest way

[foisys]

Hi,

All done! I moved to v.5.4.10 and everything works a-ok so far I had to follow the section to modify the XML files for SSL in the install guide for Debian and both the CLI and OMERO.insight are working.

Now to get OMERO.web working

Best regards

S

[mtbc]

Excellent! Thank you for keeping us posted. I guess you already noticed the move to WSGI. Given that, I can't think of any other issues you might run into.

Cheers,
Mark

[foisys]

Hi,

Actually, I have problems with OMERO.web... I followed the instructions found at https://docs.openmicroscopy.org/omero/5 ... ce3.6.html and I get something like this:

Code: Select all

ViewDoesNotExist at /webclient/
Could not import 'webgateway.views.open_with_options'. Parent module webgateway.views does not exist.


And lots of other stuff... Any clues?

Best regards

S

[mtbc]

What's "bin/omero web diagnostics" telling you?

Cheers,
Mark

[foisys]

Hi,

I get this:

Code: Select all

./omero web diagnostics

================================================================================
OMERO Diagnostics (web) 5.4.10-ice36-b105
================================================================================
       
OMERO.web status... [RUNNING] (PID 31544)
Django version: 1.8.19

Log dir:    /home/OMS/apps/OMERO/OMERO.server-5.4.10-ice36-b105/var/log exists
Log file :  OMEROweb.log                   84.0 KB       errors=0    warnings=4   


Not much to go by...

Best regards

S

[manics]

Hi

Could you try running OMERO.web in development mode following: https://docs.openmicroscopy.org/omero/5 ... ent-server

and try to connect using http://localhost:4080/ ?

Could you also show us your configuration:

Code: Select all

omero config get


And see whether there's anything useful in OMEROweb.log

Thanks, Simon

[foisys]

Hi,

Ok, proceeded with switching to Django and got this from the CLI at the end of starting omero.web:

Code: Select all

System check identified no issues (1 silenced).
February 11, 2019 - 14:07:21
Django version 1.8.19, using settings 'omeroweb.settings'
Starting development server at http://127.0.0.1:4080/
Quit the server with CONTROL-C.
Error: That port is already in use.


Ok, I kind of had a flash and went over my list of processes ran by the omero user and discovered that I had leftover processes related to former 5.2 version tests... I cleaned them and I now have this (output from lynx since this server has not other browser on it...):

Code: Select all


   Request Method: GET
    Request URL:   http://localhost:4080/omero/omero/webclient/

   Using the URLconf defined in omeroweb.urls, Django tried these URL patterns, in this order:
    1. ^favicon\.ico$
    2. ^(?i)webgateway/
    3. ^(?i)webadmin/
    4. ^(?i)webclient/
    5. ^(?i)url/
    6. ^(?i)feedback/
    7. ^(?i)api/
    8. ^index/$ [name='webindex_custom']
    9. ^$ [name='index']
   10. ^omero\/static\/(?P<path>.*)$

   The current URL, omero/webclient/, didn't match any of these.

   You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.


This is the output from omero config get output:

Code: Select all

$ ./omero config get
omero.data.dir=/home/OMS/OMERO.data
omero.db.name=omero_database
omero.db.pass=********
omero.db.user=db_omero_usr
omero.ldap.base=OU=ALL,dc=RG,dc=local
omero.ldap.config=true
omero.ldap.group_filter=(&(objectClass=group)
omero.ldap.group_mapping=name=cn
omero.ldap.new_user_group=:query:(cn=IG_OMERO_USRs))
omero.ldap.password=********
omero.ldap.sync_on_login=true
#  I removed the real address...
omero.ldap.urls=ldap://192.168.xyz.xyz:389
omero.ldap.user_filter=(objectClass=user)
omero.ldap.user_mapping=omeName=sAMAccountName,firstName=givenName,lastName=sn,email=mail
omero.ldap.username=cn=LDAP AD. Search,ou=devices,ou=Users,ou=RG,ou=ALL,dc=RG,dc=local
omero.security.password_provider=chainedPasswordProvider
omero.security.trustStore=/home/OMS/OMERO.data/keystore/keystore.jks
omero.web.application_server=development
omero.web.debug=True
omero.web.prefix=/omero
omero.web.static_url=/omero/static/


Best regards

S

[foisys]

Hi,

Follow up on the issue: looking at the Lynx output, I observed this line:

Code: Select all

http://localhost:4080/omero/omero/webclient/

The 'omero/omero' part tells me that it came from the config info from my previous install. So I changed a few config keys:

From:
omero.web.prefix=/omero
To
omero.web.prefix=/

And
omero.web.static_url=/omero/static/
To
omero.web.static_url=/static/

And restarted the development web env. I now get this from Lynx:

Code: Select all

[custom_login_logo.png]
   [logo_login_web.png]
   [omero:4064]
   Username: ______________________
   Password: ______________________
   Login

   Forgot your password?

   OMERO.web 5.4.10-ice36-b105.
   © 2007-2019 University of Dundee & Open Microscopy Environment
   OMERO is distributed under the terms of the GNU GPL. For more information, visit openmicroscopy.org


I can log in and I get into an ugly command-line interpretation of the web's GUI. So success? Not sure... Switching from 'development' to 'wcgi-tcp', restarting both nginx and omero.web gives me new error messages: a 404 Page not found for http://myserver/omero with a return link to OMERO.web and when I click on this, I get another 404 error... In OMeroweb.log, I see instances of these messages:

Code: Select all

2019-02-12 13:15:35,001 WARNI [django.request] (proc.30835) get_response():170 Not Found: /omero
2019-02-12 13:15:35,001 WARNI [django.request] (proc.30835) get_response():170 HTTP 404 <WSGIRequest: GET '/omero'>



Am I getting colder or hotter on fixing this?

Best regards

S

[manics]

It sounds like your Nginx config might be incorrect.

Could you unset the following properties so they'll take on their default values:
- omero.web.prefix
- omero.web.static_url
- omero.web.application_server

And regenerate your Nginx config?

[foisys]

Hi,

Success Resetting everything and recreating the nginx conf file did the trick!!

Migration completed! Thanks for all the inputs and I'll log our discussions in our internal doc for future reference.

Best regards

S