Open Microscopy Environment

I have a new setup that appears to be basically working: After starting omero and omero web, I'm able to bring up the OMERO.web login page but am unable to log in using the omero root user credentials. Also, I cannot log in to the root account from the command line.

According to the Diagnostics output, it appears that everything's up and running (except DropBox).

I've confirmed that i can connect to the DB and that DB creation/configuration is ok

Here's a summary of the platform:

Dell Precision 370
2GB RAM (I'll be increasing this to 8GB asap)
4TB HD
CentOS 6.5 (yeah, I know...., but I followed the guidelines for setting up Python 2.7 & Ice 3.5 on CentOS 6 and think I have things in place)

I'm attaching copies of the Diagnostics and the Blitz-0 log file and a terminal snippet of the DB access operations.

Any suggestions would be appreciated.

Almost forgot to mention: I've reset the omero root password. The initial version had a special character in it and I wanted to make sure that wasn't the problem.

Hi, Could you also send us OMEROweb*.log ?

Ola

Here's the OMEROweb.log from my system.

You'll notice that it complains about the lack of PIL. I've confirmed PIL (Pillow-2.9.0) is installed. I can import any of the appropriate modules from the command line (e.g. python -c 'from PIL import Image''. Don't understand why the same command in webclient_gateway.py doesn't work.

I didn't think this would be involved in logins to the root account from the command line.

dpb

Hi,

Did you set up your bash like stated in the doc https://www.openmicroscopy.org/site/sup ... requisites?

Code: Select all

# Environment file for OMERO

ICE_HOME=/opt/Ice-3.5.1
export PATH="${ICE_HOME}/bin:/home/omero/omeroenv/bin:$PATH"
#Remove commented out export below if Ice is not set globally accessible
#export LD_LIBRARY_PATH="${ICE_HOME}/lib64:${ICE_HOME}/lib:$LD_LIBRARY_PATH"
export PYTHONPATH="${ICE_HOME}/python:$PYTHONPATH"
export SLICEPATH="${ICE_HOME}/slice"


echo source /home/omero/omero-centos6py27ius.env >> /home/omero/.bashrc


Is Pillow installed in your virtualenv?

Code: Select all

/home/omero/omeroenv/lib64/python2.7/site-packages

If you started OMERO.web withouth previously activating omeroenv this will result in missing Pillow

Ola

as

Code: Select all

$ omero login
Server: [localhost:4064]
Username: [omero]root
Password:
Password check failed for 'root': [id=0]
Password:Cancelled
InternalException: Failed to connect: die called: Cancelled

dod you use correct password?

could you also show me the output of

Code: Select all

omero --debug=debug,trace login

Ola

Yes, I've confirmed that my bashrc is configured as directed.

And yes, Pillow (2.9.0) is installed in my virtualenv and I can import PIL modules from the command line (after activating virtualenv).

I've started OMERO.web after activating omeroenv and still see "Pillow not installed" in my OMEROweb.log following an attempt to log in from the OMERO.web interface.

I've double-checked the omero root user password and I'm confident I'm using the correct pw. Still getting

Code: Select all

Password check failed for 'root': [id=0]

I've attached the output form a login attempt using

Code: Select all

omero --debug=debug,trace login

Hi

Log files: Blitz-0.log n/a

Is the server running?

If you have any stale processes, you need to kill them

Try bin/omero admin stop , delete content of OMERO.server/var and then bin/omero admin start

Ola

Yes, I've always made sure I've had a fresh restart of omero (as well as omero.web) prior to all of my attempts to login as root.

The most recent effort followed the deletion of the contents of OMERO.server/var as you suggested.

I've attached the terminal output of this most recent attempt, which includes the diagnostics output.

Unless you have a better suggestion, I think I'm going to start over and build a new system de novo. This time I'll try CentOS 7 to obviate the need for all of the alternate Python installation mischief.

Have you ever been able to login to the server? How did you reset the root password? I wonder if some console handling has affected the hashing. For example, if you have openssl installed you can double check that the SQL for updating the password matches:

Code: Select all

$ bin/omero db password --no-salt ome
UPDATE password SET hash = 'vvFwuczAmpyoRC0Nsv8FCw==' WHERE experimenter_id  = 0;

$ echo -n ome | openssl md5 -binary | openssl base64
vvFwuczAmpyoRC0Nsv8FCw==


Cheers,
~Josh.

Bingo!!

I'd never succeeded with any omero root login attempts. And as I mentioned, suspecting my original pw was problematic, I reset it thus:

Code: Select all

[omero@omero ~]$ omero db password
Please enter password for OMERO root user:
Please re-enter password for OMERO root user:
UPDATE password SET hash = 'ibTzrADXfsKFfNwBdQsa+g==' WHERE experimenter_id  = 0;
[omero@omero ~]$

Thought that was all there was to it. Didn't realize that the hash wouldn't propagate to the db, which it hadn't:

Code: Select all

[omero@omero ~]$ psql -h localhost omdbprim -U omdbusr1 -c " select * from password"
Password for user omdbusr1:
experimenter_id |           hash           | changed
-----------------+--------------------------+---------
               0 | kO7cztnXqU33M8Hk5kr6DQ== |
               1 |                          |
(2 rows)

So, today I did so manually and double-checked that it matches:

Code: Select all

[omero@omero ~]$ psql -h localhost omdbprim -U omdbusr1 -c "UPDATE password SET hash = 'ibTzrADXfsKFfNwBdQsa+g==' WHERE experimenter_id  = 0;"
Password for user omdbusr1:
UPDATE 1
[omero@omero ~]$
[omero@omero ~]$
[omero@omero ~]$ psql -h localhost omdbprim -U omdbusr1 -c " select * from password"
Password for user omdbusr1:
experimenter_id |           hash           | changed
-----------------+--------------------------+---------
               1 |                          |
               0 | ibTzrADXfsKFfNwBdQsa+g== |
(2 rows)

And lo and behold, I can now log in to the root account from the command line!

I can authenticate for the root account as well using the OMERO.web client. However, whenever I try to do anything within the web interface, I get returned to the login screen.

I suspect this is probably due to OMERO.web still not recognizing that I have PIL installed (yes, in the omeroenv). OMEROweb log still says "No Pillow installed...."

Any suggestions for a resolution of this last problem?