[ome-users] PixelData errors

[Harri Jäälinoja]

Hi Tjelvar,

I'd also be interested in having a look at the Ansible script. I don't 
know Ansible yet, and this would be an interesting case to learn.

Josh and others have already worked on Dockerfiles for building OMERO 
Docker images. With the little I read about Ansible I got the impression 
it might be useful both in building containers and managing them. You 
could have an Ansible playbook that describes the OMERO installation and 
then you can include this in a Dockerfile, or use it on a plain server. 
Or in some other container system! And then you could have other 
playbooks for managing the containers. For example, now I'm going into 
the database container with docker exec to get a database dump, this 
sounds like something that could/should be nicely automated. I'd like to 
see how the automation would look like in Ansible vs. in shell scripts. 
Also it is interesting to see if and how Ansible plays together with Fig 
/ Docker Compose, or if it would even replace the latter altogether.

Best,
Harri

On 31/10/14 14:26, Tjelvar Olsson (JIC) wrote:
> Hi Josh,
>
> Thank you for the work around. It worked, and once applied it seemed to
> also speed up the startup of the server.
>
> If you need a reproducible test case I could send you my ansible script.
> I intend to make it more generally available once I have tested it a bit
> more.
>
> Cheers,
>
> Tjelvar
>
> On Wed, 2014-10-29 at 14:26 +0100, Josh Moore wrote:
>> On Oct 28, 2014, at 1:27 PM, Tjelvar Olsson (JIC) wrote:
>>
>>> Dear all,
>> Hi Tjelvar,
>>
>>
>>> I have been working on creating an ansible script for automating the
>>> installation of an OMERO server on Centos 6.5.
>>>
>>> The ansible script seems to be working and I can create a clean
>>> installation from scratch.
>> Interesting! Let us know how that goes.
>>
>>
>>> However, when I run the diagnostic tool on a clean install I get a
>>> number of warnings and some errors.
>>> Log files:  PixelData-0.log                18.0 KB       errors=7
>>>
>>> My question is: should I be worried about the PixelData errors (log file
>>> attached)?
>>> What do they mean and why are they raised?
>>>
>>> Example error:
>>>
>>> org.springframework.dao.DuplicateKeyException:
>>> PreparedStatementCallback; SQL [insert into configuration (name, value)
>>> values (?,?)]; ERROR: duplicate key value violates unique constraint
>>> "configuration_pkey"; nested exception is
>>> org.postgresql.util.PSQLException: ERROR: duplicate key value violates
>>> unique constraint "configuration_pkey"
>> Yes, this is a problem that's popped up a few times. See
>> http://trac.openmicroscopy.org.uk/ome/ticket/10181
>>
>> Unfortunately, we haven't worked out a fix yet. Running the
>> following should restart the service and the bottom of the log
>> should look happier:
>>
>>    bin/omero admin ice server stop PixelData-0
>>
>>
>>> Kind regards,
>>> Tjelvar
>> Cheers,
>> ~Josh
> _______________________________________________
> ome-users mailing list
> ome-users at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users