[ome-users] shoola how to debug?

[Ilya Goldberg]

On Apr 28, 2005, at 4:59 AM, Alastair Kerr wrote:

> thanks Ilya,
> weird, the update did not complain about anything and even asked to
> update the latest SOAP module.
>
> 1. If I use the tarball and run update I assume that nothing in the
> original install directory will be required (only /OME)

Its important to diagnose what went wrong before trying to fix things, 
as depending on what happened, doing this could compound the problem.

>
> 2. anyway to find the version of what I have installed?  It would be
> nice to have this on the splash page of the web site

Try this:
psql ome
ome=# select value from configuration where name = 'db_version';

Current versions should output:
  value
-------
  2.15
(1 row)
Also, try this (though this is less informative because it doesn't tell 
us what Apache is using):
perl -MOME -e 'print "$OME::VERSION\n"'

The version number is in the splash page of the web-site in current 
versions.  That was the first indication that your update didn't 
"take".
You may have updated the DB but the server is still using an old 
version of the software (i.e. you have software installed in two 
different places).
The files in the /var/tmp/OME/Install/ directory would provide a much 
more detailed description of what happened during the update process, 
and make things much easier to diagnose.  Can you email me these files 
separately (i.e. off-list)?

-Ilya

>
> - Al
>
>
>
>
> On Wed, 2005-04-27 at 19:11, Ilya Goldberg wrote:
>> Hi Alastair
>> It appears that you are not running a "current" system on
>> 129.215.237.167.
>> Its not a stable version that comes in the tar-ball at
>> http://cvs.openmicroscopy.org.uk/snapshots/stable.tar.gz
>> Stable versions use the "corporatized" OME logo as seen on
>> http://openmicroscopy.org/ (affectionately known as the alka-selzer
>> logo)
>> Development versions continue to use the "Eye" logo to indicate that
>> you're on the bleeding edge.
>>
>> Also, it doesn't appear to be a current development version either.
>> Both by the older version of the "Eye" logo on login and the fact that
>> the version number is not reported on the home page immediately
>> following "Open Microscopy Environment" page title.  As to what exact
>> version you're actually running, I don't have a way of finding out
>> without more information.  Are you sure that the installation/update
>> worked without errors?  Can you send back the contents of the
>> /var/tmp/OME/install/ directory?
>>
>> This would explain why shoola isn't working - its recognizing an 
>> older,
>> incompatible version of the server.
>>
>> Things are definitely not as they should be...
>> -Ilya
>>
>>
>>
>> On Apr 27, 2005, at 10:17 AM, Alastair Kerr wrote:
>>
>>> ok thanks,
>>> anything I can tinker with on my site? (sorry: I would need quite
>>> specific instructions) Please don't waste anytime with me if you are
>>> working on a general fix.
>>>
>>> - Al
>>>
>>>
>>>
>>> On Wed, 2005-04-27 at 15:02, Jean-Marie Burel wrote:
>>>> Hi
>>>> sorry for not answering earlier
>>>> The problem is not directly coming from the values of the static
>>>> fields as
>>>> written before
>>>> (BTW we should put that into the config file!)
>>>>
>>>> but directly from OMEDS/OME-JAVA
>>>> Now the function RemoteCaller.getServerVersion() now returned null
>>>> so we have A nullPointerException that we wrap into a
>>>> DSOutOfServiceException.
>>>> It used work so.....
>>>>
>>>> jmarie
>>> -- 
>>> Alastair Kerr, Ph.D.,
>>> Bioinformatician, Wellcome Trust Centre for Cell Biology,
>>> COIL, Swann Building, The University of Edinburgh
>>> Edinburgh, EH9 3JR, UK
>>> Tel: 44-(0)131-650-7527
>>>
> -- 
> Alastair Kerr, Ph.D.,
> Bioinformatician, Wellcome Trust Centre for Cell Biology,
> COIL, Swann Building, The University of Edinburgh
> Edinburgh, EH9 3JR, UK
> Tel: 44-(0)131-650-7527
>