cannot log in to omero root account

[jmoore]

Hi Max,

In this step:

Code: Select all

Username: [omero]


you're looking for the username: "root". You are currently logged in as the Ubuntu user "omero" so `bin/omero login` assumes that you also want to login as the OMERO user user "omero". But that account doesn't exist yet. OMERO_ROOT_PASSWORD is for use with the only existing (sysadmin) account in a fresh OMERO: "root".

Hope that helps,
~Josh

[maxgitt]

This may seem like a silly question. But how do I add other accounts. The server and webclient installation pages for ubuntu don't specify what username and password would be valid for the login page or let alone how to add accounts. I just tried your solution but no bite:

Code: Select all

root@maxgitt-pc:/home/omero/OMERO.server# bin/omero login
FATAL: Running bin/omero as root can corrupt your directory permissions.


Any tips?

[jmoore]

Hi Max,

As the "omero" Ubuntu user, use `bin/omero login root@localhost` providing OMERO_ROOT_PASSWORD. Once you've done . Once you've done that (still as the "omero" Ubuntu user), take a look at `bin/omero user add -h` for information on creating new users, or simiarly, `bin/omero group add -h`.

Cheers,
~Josh.

[maxgitt]

Thank you so much. Below was the solution:

Code: Select all

bin/omero login root@maxgitt-pc
Previously logged in to maxgitt-pc:4064 as root
Password:
Created session b6d81c98-6075-402f-91e1-2b360049a43d (root@maxgitt-pc:4064). Idle timeout: 10 min. Current group: system


I also managed to login to the webclient via:
root
omero_root_password.

As an aside, is there documentation somewhere that gives a tutorial on the above? I can't imagine I'm the first to ask why the tutorial seems to be cut short.

Lastly, I ran the diagnostics command:

Code: Select all

omero@maxgitt-pc:~/OMERO.server$ bin/omero admin diagnostics
================================================================================
OMERO Diagnostics 5.3.4-ice36-b69
================================================================================
       
Commands:   java -version                  1.8.0     (/usr/bin/java)
Commands:   python -V                      2.7.12    (/usr/bin/python)
Commands:   icegridnode --version          3.6.4     (/usr/bin/icegridnode)
Commands:   icegridadmin --version         3.6.4     (/usr/bin/icegridadmin)
Commands:   psql --version                 9.6.5     (/usr/bin/psql)

Server:     icegridnode                    running
Server:     Blitz-0                        active (pid = 4055, enabled)
Server:     DropBox                        active (pid = 4075, enabled)
Server:     FileServer                     active (pid = 4084, enabled)
Server:     Indexer-0                      active (pid = 4085, enabled)
Server:     MonitorServer                  active (pid = 4088, enabled)
Server:     OMERO.Glacier2                 active (pid = 4086, enabled)
Server:     OMERO.IceStorm                 active (pid = 4091, enabled)
Server:     PixelData-0                    active (pid = 4089, enabled)
Server:     Processor-0                    active (pid = 4096, enabled)
Server:     Tables-0                       active (pid = 4108, enabled)
Server:     TestDropBox                    inactive (enabled)

Log dir:    /home/omero/OMERO.server-5.3.4-ice36-b69/var/log exists
Log files:  Blitz-0.log                    14.0 MB       errors=0    warnings=35 
Log files:  DropBox.log                    6.0 KB        errors=0    warnings=2   
Log files:  FileServer.log                 0.0 KB       
Log files:  Indexer-0.log                  107.0 KB     
Log files:  MonitorServer.log              3.0 KB       
Log files:  OMEROweb.lock                  0.0 KB       
Log files:  OMEROweb.log                   0.0 KB       
Log files:  PixelData-0.log                44.0 KB     
Log files:  Processor-0.log                480.0 KB      errors=0    warnings=1   
Log files:  Tables-0.log                   4.0 KB        errors=0    warnings=1   
Log files:  TestDropBox.log                n/a
Log files:  master.err                     3.0 KB        errors=2    warnings=1   
Log files:  master.out                     0.0 KB       
Log files:  Total size                     14.93 MB


Environment:OMERO_HOME=(unset)             
Environment:OMERO_NODE=(unset)             
Environment:OMERO_MASTER=(unset)           
Environment:OMERO_USERDIR=(unset)         
Environment:OMERO_TMPDIR=(unset)           
Environment:PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
Environment:PYTHONPATH=(unset)             
Environment:ICE_HOME=(unset)               
Environment:LD_LIBRARY_PATH=(unset)       
Environment:DYLD_LIBRARY_PATH=(unset)     

OMERO SSL port:4064                           
OMERO TCP port:4063                           
OMERO data dir:'/OMERO'                       Exists? True   Is writable? True
OMERO temp dir:'/home/omero/omero/tmp'        Exists? True   Is writable? True   (Size: 0)

JVM settings: Blitz-${index}                -Xmx2495m -XX:MaxPermSize=1g -XX:+IgnoreUnrecognizedVMOptions
JVM settings: Indexer-${index}              -Xmx1663m -XX:MaxPermSize=1g -XX:+IgnoreUnrecognizedVMOptions
JVM settings: PixelData-${index}            -Xmx2495m -XX:MaxPermSize=1g -XX:+IgnoreUnrecognizedVMOptions
JVM settings: Repository-${index}           -Xmx1663m -XX:MaxPermSize=1g -XX:+IgnoreUnrecognizedVMOptions

OMERO.web status... [NOT STARTED]
Django version: 1.8


Is the second to last line "OMERO.web status ... NOT STARTED" a problem?

[wmoore]

Hi,

When you say the tutorial is cut short, is it just the username and passwords to use with web login or

Code: Select all

$ bin/omero login


that are needed?


Have you deployed OMERO.web and OMERO.server together?
E.g. did you do this to start web?

Code: Select all

~/OMERO.server$ bin/omero web start


If so, then I would expect you to see something like

Code: Select all

OMERO.web status... [RUNNING] (PID 40307)


However, we now recommend that you install OMERO.server https://docs.openmicroscopy.org/omero/5 ... ice36.html and OMERO.web separately https://docs.openmicroscopy.org/omero/5 ... ce3.6.html.
In this case, you'd need to run the diagnostics command from the web install ("/OMERO.py" in the docs above) to see the web status, and you wouldn't expect the see web status 'RUNNING' from the OMERO.server location.

In 5.4.0 (released next week) we have separated this into 2 commands to be run on the appropriate OMERO.server vv OMERO.web installs:

Code: Select all

$ bin/omero admin diagnostics
# and
$ bin/omero web diagnostics


Hope that helps,

Will.

[maxgitt]

What I mean by cut short is that the Omero.server installation refers to the Omero.web installation (https://docs.openmicroscopy.org/omero/5.3.4/sysadmins/unix/install-web/walkthrough/omeroweb-install-ubuntu-ice3.6.html) but doesn't explain it's significance or that I should be running

Code: Select all

bin/omero web start

Maybe there's a misunderstanding but I was under the impression that Omero.web had to be run within OMERO.server-5.3.4-ice36-b69. What exactly is the difference between OMERO.server and OMERO.server-5.3.4-ice36-b69?

I tried your strategy and ran

Code: Select all

~/OMERO.server$ bin/omero web start

In a separate terminal I ran a status but the reply remains the same as before:

Code: Select all

~/OMERO.server$ bin/omero web status
OMERO.web status... DEVELOPMENT: You will have to kill processes by hand!


[wmoore]

Hi,

I see. I guess we don't include "bin/omero web start" since it's included in the omero-web-init.d file to be run on startup etc.
But you're right, it would be useful to have that as a final step in the install.
I'll create a ticket to fix this... https://trello.com/c/nwwvjS6G/72-bin-om ... stall-docs


You can run OMERO.web from within OMERO.server (the OMERO.server distribution contains all the OMERO.web code etc), but we now recommend that they're installed and managed separately since the dependencies of each are then independent etc.

The OMERO.py download contains all the resources that are in the OMERO.server/lib/python directory including all the OMERO.web code, so you can use the OMERO.py download to run OMERO.web without needing the full OMERO.server download.

OMERO.server is just a short-hand name for e.g. OMERO.server-5.3.4-ice36-b69 (or any other version) and we use it in our docs because the docs can cover multiple minor versions/builds.
We tend to sym-link OMERO.server -> OMERO.server-5.3.4-ice36-b69 (or whatever your current version is) so that OMERO.server can then be used to refer to the server "home" directory.

Code: Select all

ln -s OMERO.py-* OMERO.py

Now you're seeing

Code: Select all

OMERO.web status... DEVELOPMENT: You will have to kill processes by hand!


which is not the same as before:

Code: Select all

OMERO.web status... [NOT STARTED]


Have you followed the latest install docs and installed OMERO.web separately in it's own virtualenv? If so then you don't need to have OMERO.web running from within the OMERO.server. So the status "OMERO.web status... [NOT STARTED]" in OMEOR.server is OK (you had web successfully running in a separate install when you saw this originally?)

So you can stop the

Code: Select all

~/OMERO.server$ bin/omero web start


which is running in that terminal simply with Ctrl-C.

Hope that helps,

Will.