[ome-users] Beta 3.1.1 does not start

[josh.moore at gmx.de]

Everyone,

Thanks for all the feedback on this. First and foremost, it's
important to say that nothing has happened to or is wrong with any of
your databases.  Alexandre's intuition was correct, the issue was with
Postgres versions and upgrading to 8.2+ would in fact solve this. As
Jason pointed out, we don't actively test on 8.1 or below, and so this
slipped through the crack. Our apologies.

However, it was possible to rewrite the upgrade to be backwards
compatible. You can download the new file at:

  https://trac.openmicroscopy.org.uk/omero/browser/trunk/sql/psql/OMERO3A__11/OMERO3A__5.sql?format=txt

While we're looking to expanding the number of tested configurations,
there'll always be a limit, so we'll be asking for feedback in the
near future. Those tests and the other build products are visible to
the community at:

   http://hudson.openmicroscopy.org.uk/

We will also be packaging a 3.1.2 server with the modified upgrade
script and a few other minor fixes soon.

Thanks again for all your support,
~Josh

P.S. for anyone who is interested, this was filed as:
https://trac.openmicroscopy.org.uk/omero/ticket/1108

Jason Swedlow writes:
 > Hi All-
 > 
 > Sorry for the radio silence-- we are working against a bunch of  
 > deadlines in the next couple of days, so have been juggling alot.
 > 
 > We didn't test upgrade on Postgres 8.1-- we just started our new  
 > grant cycle (thanks to the Wellcome Trust and thanks all for your  
 > support!)  and didn't have the test servers that were just funded all  
 > up and running  to test installs of all versions of PostgreSQL.  One  
 > of our priorities is automating our testing across all operating  
 > systems and installation configs.  Do the math-- it is pretty scary.   
 > With the new funding, we now have the hardware, but needed to get a  
 > few other things done before getting these all up and running.
 > 
 > We are working on this here tonight (burning the late night IM) and  
 > will be back with you shortly with an update on status.
 > 
 > Thanks again for all the feedback-- it is very very helpful.  Keep it  
 > coming!
 > 
 > Cheers,
 > 
 > Jason
 > 
 > On 14 Oct 2008, at 20:20, Alexandre Cunha wrote:
 > 
 > > Howdy,
 > >
 > > We were about to install the new 3.1.1 server but given the recent
 > > emails I was wondering if upgrading postgres to 8.3 would help in any
 > > way solve the reported problems. Please advise.
 > >
 > > Thanks,
 > > - Alex.
 > >
 > > Paulo Almeida wrote:
 > >> Hi,
 > >>
 > >> I get the same error when upgrading, using PostgreSQL 8.1.11 :
 > >>
 > >> CREATE VIEW
 > >> ERROR:  syntax error at or near "," at character 975
 > >> LINE 23:         FOR dup1, dup2 IN EXECUTE sql LOOP
 > >>                          ^
 > >> ERROR:  current transaction is aborted, commands ignored until end of
 > >> transaction block
 > >>
 > >>
 > >> - Paulo
 > >>
 > >> On Tuesday 14 October 2008 12:56, josh.moore at gmx.de wrote:
 > >>> Hi Mario,
 > >>>
 > >>> Mario Valle writes:
 > >>>> Dear all,
 > >>>> inital testing of 3.0.1 were successful. Now upgraded to 3.1.1  
 > >>>> and no
 > >>>> way to start the server.
 > >>>> OK, I was not able to upgrade the database due the SQL syntax error
 > >>>> (covered on another mail on the list).
 > >>>> I do not know if the hanging of the server during initialization  
 > >>>> is due
 > >>>> to the incomplete upgrade or not. But here it is.
 > >>>
 > >>> Yes, the server will refuse to start if the database does not  
 > >>> have the
 > >>> proper version. Can you clarify: you are having the same SQL upgrade
 > >>> error as Oliver:
 > >>>
 > >>> CREATE VIEW
 > >>>
 > >>> FEHLER:  Fehler »syntax error« bei »,« bei Zeichen 975
 > >>>
 > >>> ZEILE 23:         FOR dup1, dup2 IN EXECUTE sql LOOP
 > >>>
 > >>>
 > >>> (though probably without the German) ? What postgres version are you
 > >>> working with?
 > >>>
 > >>> ~Josh
 > >>>
 > >>>> The last line of the server log  is:
 > >>>>
 > >>>> 10:30:41,434 INFO  [Log4jService$URLWatchTimerTask] Configuring  
 > >>>> from
 > >>>> URL: resource:jboss-log4j.xml
 > >>>>
 > >>>> If I try to connect using the WebAdmin interface, the message is:
 > >>>>
 > >>>> Connection failure: Error creating bean with name 'init' defined in
 > >>>> class path resource [ome/client/spring.xml]: Cannot resolve  
 > >>>> reference to
 > >>>> bean 'managed-ome.api.ISession' while setting bean property
 > >>>> 'sessionService'; nested exception is
 > >>>> org.springframework.beans.factory.BeanCreationException: Error  
 > >>>> creating
 > >>>> bean with name 'managed-ome.api.ISession': FactoryBean threw  
 > >>>> exception
 > >>>> on object creation; nested exception is ome.client.OutOfService:  
 > >>>> Cannot
 > >>>> initialize service proxy
 > >>>>
 > >>>> Thanks for your help!