[ome-users] Image J Login Problem

[Curtis Rueden]

Hi everyone,

I heard back from Dennis that he solved the ImageJ login problem with
his OME server. The issue was that the RedHat Linux 4 installation has
enabled an auto-update feature that had upgraded Apache to v2, but
mod_perl only partially.

According to Dennis: "It did not update the API in mod perl because
the auto updater cannot update mod perl from v1.5 (my old version) to
v2.x. After I corrected this I was able to connect to OME with Image
J.  I am surprised that mod perl worked at all under this condition
but it appeared to function well enough to pass the test(s) that OME
performed when installed."

I am posting this information to the list in case anyone else has a
similar issue and searches the archives for a solution.

-Curtis

On Nov 16, 2007 7:37 AM, Dennis A. Simpson <dsimpson at med.unc.edu> wrote:
> Curtis
> I am still troubleshooting this issue.  I am using Apache 2/mod_per 2.
> Looking back I have a note that the old Shoola lost its ability to
> connect at the same time as Visbio.  This appears to be about the time
> OME stopped using SOAP:LITE.  I will keep researching this but at this
> point I fear it has moved well beyond my abilities.  It does appear to
> be a configuration issue on my end though.  Thanks for the help.  If I
> get it figured out I will let you know what I found.
>
> Dennis
>
> Curtis Rueden wrote:
> > Hi Dennis,
> >
> > I believe Apache/Constants.pm is part of mod_perl. If your mod_perl is
> > not configured properly, that could explain the problems you're seeing
> > the OME Java, though I would be surprised if the web interface worked
> > correctly either in that case.
> >
> > What version of Apache are you running? What version of mod_perl? We
> > recommend you use either Apache 2/mod_perl 2 or Apache 1/mod_perl
> > 1.2x. And especially stay away from mod_perl 1.99 if possible.
> >
> > -Curtis
> >
> > On Nov 13, 2007 11:31 AM, Dennis A. Simpson <dsimpson at med.unc.edu> wrote:
> >
> >> Curtis
> >> I did some more searching.  Found one error message buried in the Apache
> >> error log.  Error says can't locate Apache/Constants.pm.  I looked and
> >> we are using Apache2 but I believe we have the correct support files
> >> since the web login works fine.  By the way, I did a clean install of
> >> OME, no change.  Any more tips on what this file is and where it might
> >> actually be?  Thanks for your time.
> >>
> >> Dennis
> >>
> >>
> >> Curtis Rueden wrote:
> >>
> >>> Hi Dennis,
> >>>
> >>> Yes, OME and OMERO can live on the same machine.
> >>>
> >>> As for the OME connectivity issue, I have heard of similar problems
> >>> happening to other users, but am not sure what causes it. To debug it
> >>> you could study the interaction on both the client and server, and
> >>> analyze what's being sent and received at the XML-RPC level.
> >>> Unfortunately we have not had time to add any sort of "debugging" mode
> >>> to the plugin.
> >>>
> >>> Alternately, one simple thing to try is to wipe your OME installation
> >>> completely ("dropdb ome" and "rm -rf /OME") but it sounds like you
> >>> have quite a few users, so you certainly want to back up everything
> >>> first. Or you could install OME 2.6.1 on a second machine, see if you
> >>> have the same problem, and if not, migrate the data from the original
> >>> server over to the new machine.
> >>>
> >>> Sorry I can't give you a more surefire answer. I will say that it is
> >>> only a matter of time before we provide the same sort of connectivity
> >>> between ImageJ & VisBio and OMERO, and it will be better supported, as
> >>> OMERO is our long term path forward as an image database solution.
> >>>
> >>> -Curtis
> >>>
> >>> On 11/9/07, Dennis A. Simpson <dsimpson at med.unc.edu> wrote:
> >>>
> >>>
> >>>> Curtis
> >>>> I can connect to your test server with out a problem.  There are no old
> >>>> OME libraries in my Image J setup..  I have also noted that both VisBio
> >>>> and Shooloa are not able to connect.  I did have Omero installed and was
> >>>> able to connect with it.  The problem with OME started some time ago.
> >>>> Unfortinuatly I did not pay much attention at the time since I was
> >>>> primarily using the Web interface.  --An unrelated question, can OME and
> >>>> OMERO peacefully co-exist on the same machine?
> >>>>
> >>>> Curtis Rueden wrote:
> >>>>
> >>>>
> >>>>> Hi Dennis,
> >>>>>
> >>>>> Here is the login information for our OME test server:
> >>>>>
> >>>>> server: skyking.microscopy.wisc.edu
> >>>>> user: omeguest
> >>>>> pass: showmethedata
> >>>>>
> >>>>> If you click through the search dialog, you should see two image
> >>>>> thumbnails available for download. Let me know whether it works.
> >>>>>
> >>>>> Thanks,
> >>>>> Curtis
> >>>>>
> >>>>> On 11/8/07, Dennis A. Simpson <dsimpson at med.unc.edu> wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Hi all.
> >>>>>> I am not sure if this is the correct list for this question.  Starting
> >>>>>> with OME 2.6.0 we were not able to login with Image J using LOCI's
> >>>>>> Bioformats jar file.  I ignored the problem because so few of us were
> >>>>>> using OME at the time but that has changed now.  I have upgraded to OME
> >>>>>> 2.6.1 and have the latest Image J and Bioformats.jar files but still no
> >>>>>> good.  The login returns an incorrect user ID/password error.  OME is
> >>>>>> installed on a Red Hat Linux v4 box. I was able to log in using this
> >>>>>> method several upgrades ago.  Sorry for the lack of information on
> >>>>>> this.  I am at a loss since I can find no logs recording any errors.
> >>>>>> _______________________________________________
> >>>>>> ome-users mailing list
> >>>>>> ome-users at lists.openmicroscopy.org.uk
> >>>>>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users