Page 1 of 1

Omero.web and Client Log In Issue

PostPosted: Mon Mar 14, 2011 4:10 pm
by gtg182x
We currently have an install of 4.2 on a RHEL machine which was working well until recently. Now no users can log into either the web or desktop clients. When attempting to log into the web client we receive "Error: Server is not responding, please contact administrator." I've tried looking through our log files and here and still cannot figure out our issue.

Here is the output from bin/omero admin diagnostics:
Code: Select all
================================================================================
OMERO Diagnostics Beta4.2.1-r8614-Beta4.2-b41
================================================================================
       

Commands:   java -version                  1.6.0     (/usr/java/jdk1.6.0_21/bin/java -- 2 others)
Commands:   python -V                      2.6.5     (/opt/python/bin/python -- 2 others)
Commands:   icegridnode --version          3.3.1     (/opt/Ice-3.3.1/bin/icegridnode)
Commands:   icegridadmin --version         3.3.1     (/opt/Ice-3.3.1/bin/icegridadmin)
Commands:   psql --version                 8.1.21    (/usr/bin/psql)

Server:     icegridnode                    running
Server:     Blitz-0                        inactive (disabled)
Server:     DropBox                        inactive (disabled)
Server:     FileServer                     active (pid = 29247, enabled)
Server:     Indexer-0                      inactive (disabled)
Server:     MonitorServer                  inactive (disabled)
Server:     OMERO.Glacier2                 active (pid = 29252, enabled)
Server:     OMERO.IceStorm                 active (pid = 29263, enabled)
Server:     Processor-0                    activating (enabled)
Server:     Repository-1                   error: node `repo' couldn't be reached:
the node is not active
Server:     Tables-0                       inactive (disabled)
Server:     TestDropBox                    inactive (enabled)

Log dir:    /var/home/omero/omero/var/log  exists

Log files:  Blitz-0.log                    22.0 MB       errors=1084 warnings=10619
Log files:  Blitz-0.log.1                  512.0 MB      errors=119  warnings=237
Log files:  Blitz-0.log.2                  512.0 MB      errors=31   warnings=50 
Log files:  Blitz-0.log.3                  512.0 MB      errors=122  warnings=147
Log files:  Blitz-0.log.4                  512.0 MB      errors=24   warnings=35 
Log files:  Blitz-0.log.5                  512.0 MB      errors=89   warnings=154
Log files:  Blitz-0.log.6                  512.0 MB      errors=40   warnings=54 
Log files:  Blitz-0.log.7                  512.0 MB      errors=28   warnings=39 
Log files:  Blitz-0.log.8                  512.0 MB      errors=1423 warnings=1530
Log files:  Blitz-0.log.9                  512.0 MB      errors=8706 warnings=8738
Log files:  DropBox.log                    1.0 KB        errors=4    warnings=0   
Log files:  FileServer.log                 0.0 KB       
Log files:  Indexer-0.log                  7.0 MB        errors=363  warnings=3098
Log files:  MonitorServer.log              1.0 KB        errors=2    warnings=0   
Log files:  OMEROweb-DEBUG.log             18.0 KB       errors=2    warnings=1   
Log files:  OMEROweb.log                   1.0 MB        errors=3306 warnings=27 
Log files:  Processor-0.log                3.0 MB        errors=973  warnings=6811
Log files:  Processor-0.log.1              4.0 MB        errors=1394 warnings=9758
Log files:  Processor-0.log.2              4.0 MB        errors=1394 warnings=9758
Log files:  Processor-0.log.3              4.0 MB        errors=1394 warnings=9757
Log files:  Processor-0.log.4              4.0 MB        errors=425  warnings=6149
Log files:  Processor-0.log.5              4.0 MB       
Log files:  Processor-0.log.6              4.0 MB       
Log files:  Processor-0.log.7              4.0 MB       
Log files:  Processor-0.log.8              4.0 MB        errors=0    warnings=20 
Log files:  Tables-0.log                   n/a
Log files:  TestDropBox.log                n/a
Log files:  master.err                     3.0 KB       
Log files:  master.out                     0.0 KB       
Log files:  Total size                     4682.53 MB


Environment:OMERO_HOME=(unset)             
Environment:OMERO_NODE=(unset)             
Environment:OMERO_MASTER=(unset)           
Environment:PATH=/usr/java/jdk1.6.0_21/bin/:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/java/jdk1.6.0_21/bin/:/opt/python/bin:/opt/Ice-3.3.1/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin
Environment:ICE_HOME=(unset)               
Environment:LD_LIBRARY_PATH=/opt/python/lib::/usr/local/samba/lib:/usr/local/lib
Environment:DYLD_LIBRARY_PATH=(unset)     

OMERO data dir: '/ext/omero'   Exists? True   Is writable? True
OMERO.web status... [RUNNING] (PID 12136)


Please let me know what else you need to help diagnose our issue.

Re: Omero.web and Client Log In Issue

PostPosted: Mon Mar 14, 2011 7:54 pm
by jmoore
Server: Blitz-0 inactive (disabled)


The main Java server is not running. You can try restarting the entire stack with:
Code: Select all
bin/omero admin restart


At the same time, could you send us the latest Blitz-0.log file from var/log so we can try to figure out why the server's shutdown?

Thanks,
~Josh.