[ome-users] Omero Beta 4 installation problems
Zoltan Cseresnyes
zcseresn at gmail.com
Thu Apr 16 19:48:13 BST 2009
Steve,
If I may contribute a bit, although I'm nowhere near as conversant in these
as Chris, obviously. I had a similar problem as yours; the solution in my
case was to go back to postgres, drop the omero database and user and then
re-create the omero user and database (and language binding) again. Then
do the "bin/omero db script" and choose a NEW password for omero's root!!
Then run the psql bit for the OMERO4__0.sql and make sure that you get no
error messages. Then start the omero server and log in on webadmin with the
new password as root. It worked for me.
Hope this helps,
Zoltan
On Thu, Apr 16, 2009 at 7:25 PM, Steve Guerrero <guerrero.steve at gene.com>wrote:
> Hi Chris,
>
> Thanks for your help. I tried logging in as root with the password I
> assigned in the part you mentioned (in fact I have only used one
> password for everything so far, just to simplify my testing), but no
> luck, it still won't log in.
>
> I noticed there was a previous thread where someone had a similar
> problem to mine that turned out to be a problem with their postgres
> installation (the thread subject: "Omero Beta 4 installation problems").
>
> Although in my case, I only have one install of postgres, and that's
> from a fresh install of ubuntu server, could it also be something
> related to the db connectivity? How might I test it? This simple test
> seems to be successful:
>
> calm at omeserver1:~/ome/omero-Beta4.0.0$ psql -h localhost -U omero -l
> Password for user omero:
> List of databases
> Name | Owner | Encoding
> -----------+----------+----------
> omero | omero | UTF8
> postgres | postgres | UTF8
> template0 | postgres | UTF8
> template1 | postgres | UTF8
> (4 rows)
>
>
> Thanks again,
> -sg
>
>
> Chris Roome wrote:
> > Hi all,
> >
> > Fixed.
> >
> > In the end it was not a problem with the PostgreSQL database encoding,
> > it was a problem with the manually installed postgresql and newly
> > created database. There were some executables from an older version of
> > postgresql installed on the system which were not correctly removed.
> >
> > After removal of these and re-creating the database, the installation
> > and server start went through faultlessly. The database encoding can be
> > UTF8.
> >
> > Many, many thanks to Josh for helping with this!
> >
> > Regards,
> >
> > Chris.
> >
> >
> > Chris Roome wrote:
> >> Hi Josh,
> >>
> >> Sure - will do!
> >>
> >> Gone off list...
> >>
> >> Chris.
> >>
> >> josh.moore at gmx.de wrote:
> >>> Well, congratulations, Chris, looks like you've found a new and
> >>> interesting problem for us! I wouldn't think that this is related to
> >>> the encoding, though you can certainly try that out. Could you
> >>> possibly send me your log files zipped us off list?
> >>>
> >>> Thanks,
> >>> ~Josh.
> >>>
> >>> Chris Roome writes:
> >>> > There was no extra configuration for postgreSQL. The output of
> >>> > 'bin/omero config get' gives:
> >>> >
> >>> > local/omero-Beta4.0.0> bin/omero config get
> >>> > omero.data.dir=/usr/local/OMERO-DB
> >>> > omero.db.name=omero
> >>> > omero.db.pass=<my-password>
> >>> > omero.db.user=omero
> >>> > with the correct db name, password and user.
> >>> >
> >>> > 'psql -U omero -h localhost omero' gives:
> >>> >
> >>> > local/omero-Beta4.0.0> psql -U omero -h localhost omero
> >>> > Password for user omero:
> >>> > Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
> >>> >
> >>> > Type: \copyright for distribution terms
> >>> > \h for help with SQL commands
> >>> > \? for help with psql commands
> >>> > \g or terminate with semicolon to execute query
> >>> > \q to quit
> >>> >
> >>> > omero=> \q
> >>> >
> >>> > One thing I did notice when setting up the postgres db was that the
> >>> > encoding is 'UTF8' and not 'SQL_ASCII' as described in the
> installation
> >>> > instructions:
> >>> >
> >>> > local/omero-Beta4.0.0> psql -h localhost -U omero -l
> >>> > Password for user omero:
> >>> > List of databases
> >>> > Name | Owner | Encoding
> >>> > -----------+----------+----------
> >>> > omero | omero | UTF8
> >>> > postgres | postgres | UTF8
> >>> > template0 | postgres | UTF8
> >>> > template1 | postgres | UTF8
> >>> > (4 rows)
> >>> >
> >>> > Could this be the problem?
> >>> >
> >>> > Many thanks for all your help!
> >>> >
> >>> > Cheers,
> >>> >
> >>> > Chris.
> >>> _______________________________________________
> >>> ome-users mailing list
> >>> ome-users at lists.openmicroscopy.org.uk
> >>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
> >> _______________________________________________
> >> ome-users mailing list
> >> ome-users at lists.openmicroscopy.org.uk
> >> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
> >
>
> _______________________________________________
> ome-users mailing list
> ome-users at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
>
--
Zoltan Cseresnyes
Facility manager, Imaging Suite
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-users/attachments/20090416/b547c7ae/attachment.html>
More information about the ome-users
mailing list