[ome-devel] webemdb timeout
Will Moore
will at lifesci.dundee.ac.uk
Tue Apr 24 16:44:22 BST 2012
Hi Ingvar,
Just to be sure if the '10 minutes' is due to omero session timeout, you could change this with
E.g
$ bin/omero config set omero.sessions.timeout 3600000 # timeout in millisecs!
You'll need to do
$ bin/omero admin restart
and check that this varies your Apache timeout.
Then at least we know for sure that it's the same 10 mins, not a coincidence.
Will
On 24 Apr 2012, at 16:37, Aleksandra Tarkowska wrote:
> Hi Ingvar
>
> Could you please send us log files from omero/dist/var/log,
> as well as your omero apache config file and output of bin/omero config get.
>
> Could you please make sure you have web debugging on via:
>
> bin/omero config get
> and check if omero.web.debug is True
>
> if not please set by:
> bin/omero config set omero.web.debug True
>
> Thanks
>
> Kind regards
> Aleksandra
>
> Aleksandra Tarkowska, M.Sc, Engg.
> Software Engineer
> Open Microscopy Environment
> http://www.openmicroscopy.org
>
>
> On 24 Apr 2012, at 16:21, Ingvar Lagerstedt wrote:
>
>> Hello,
>>
>> I am trying to use the webemdb interface with Apache on an RHEL6WS box. I
>> can access the pages fine as long as there is a valid session, but as soon
>> as the session ends I get an AttributeError. If I at that point connect
>> to the WebClient, I can then access webemdb for another 10 min.
>> I do not see this behaviour when using the development server on a Mac, so
>> suspect that this is down to either some security feature of RHEL6WS or
>> Apache, or just some Apache settings that I am unfamiliar with. Any
>> suggestions appreciated.
>>
>> The error message is attached, and the output from
>> bin/omero admin diagnostics
>> is given below
>>
>>
>> ================================================================================
>> OMERO Diagnostics OMERO4.3.3
>> ================================================================================
>>
>> WARNING:omero.util.UpgradeCheck:UPGRADE AVAILABLE:Please upgrade to
>> Beta-4.3.4 See http://trac.openmicroscopy.org.uk/omero for the latest
>> version
>>
>> Commands: java -version 1.6.0 (/usr/bin/java)
>> Commands: python -V 2.6.6 (/usr/bin/python)
>> Commands: icegridnode --version 3.4.2 (/usr/bin/icegridnode)
>> Commands: icegridadmin --version 3.4.2 (/usr/bin/icegridadmin)
>> Commands: psql --version 8.4.9 (/usr/bin/psql)
>>
>> Server: icegridnode running
>> Server: Blitz-0 active (pid = 3200, enabled)
>> Server: DropBox active (pid = 3218, enabled)
>> Server: FileServer active (pid = 3244, enabled)
>> Server: Indexer-0 active (pid = 3220, enabled)
>> Server: MonitorServer active (pid = 3243, enabled)
>> Server: OMERO.Glacier2 active (pid = 3222, enabled)
>> Server: OMERO.IceStorm active (pid = 3245, enabled)
>> Server: PixelData-0 active (pid = 3246, enabled)
>> Server: Processor-0 active (pid = 3251, enabled)
>> Server: Tables-0 inactive (disabled)
>> Server: TestDropBox inactive (enabled)
>>
>> Log dir: /var/www/html/omero/dist/var/log exists
>>
>> Log files: Blitz-0.log 139.0 MB errors=8
>> warnings=77
>> Log files: DropBox.log 22.0 KB errors=2
>> warnings=8
>> Log files: FileServer.log 2.0 KB
>> Log files: Indexer-0.log 218.0 KB errors=16
>> warnings=20
>> Log files: MonitorServer.log 11.0 KB
>> Log files: OMEROweb.log 3.0 MB errors=39
>> warnings=59
>> Log files: OMEROweb_request.log 1.0 KB errors=0
>> warnings=13
>> Log files: PixelData-0.log 133.0 KB errors=18
>> warnings=30
>> Log files: Processor-0.log 30.0 KB errors=5
>> warnings=16
>> Log files: Tables-0.log n/a
>> Log files: TestDropBox.log n/a
>> Log files: master.err 7.0 KB
>> Log files: master.out 0.0 KB
>> Log files: Total size 143.05 MB
>>
>> Parsing Blitz-0.log:[line:410] => Server restarted <=
>> Parsing Blitz-0.log:[line:623855] => Server restarted <=
>> Parsing Blitz-0.log:[line:872912] Your postgres hostname and/or port is
>> invalid
>> Parsing Blitz-0.log:[line:873012] => Server restarted <=
>> Parsing Blitz-0.log:[line:873506] => Server restarted <=
>>
>> Environment:OMERO_HOME=/var/www/html/omero/dist
>> Environment:OMERO_NODE=(unset)
>> Environment:OMERO_MASTER=(unset)
>> Environment:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/ingvar/bin
>> Environment:ICE_HOME=/usr
>> Environment:LD_LIBRARY_PATH=(unset)
>> Environment:DYLD_LIBRARY_PATH=(unset)
>>
>> OMERO data dir: '/var/OMERO'
>> Exists? True Is writable? True
>> OMERO.web status... [RUNNING] (PID 3474)
>>
>> The postgres error in Blitz-log happened when I got a new IP-address, and
>> should not be relevant here. The problem describe was seen both before
>> and after that event.
>>
>>
>> Let me know if there are any further details that may be useful.
>> /Ingvar
>>
>> ---
>> Ingvar Lagerstedt, PDBe - EMBL/EBI, A2-24
>> Hinxton, Cambridge CB10 1SD, UK
>> <webemdb_timeout.error>_______________________________________________
>> ome-devel mailing list
>> ome-devel at lists.openmicroscopy.org.uk
>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>
>
> The University of Dundee is a registered Scottish Charity, No: SC015096
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20120424/a47fea85/attachment-0001.html>
More information about the ome-devel
mailing list