[ome-users] (no subject)

[Josh Moore]

Hi Bram,

"DatabaseBusy" doesn't mean that PostgreSQL is failing in general, but just that OMERO's access to it has blocked.

Is the Blitz-0.log the entire contents of the file? If so, then the log file probably got rolled over just before you sent it to us. Having Blitz-1.log would be helpful too then.

Cheers,
~Josh

On Aug 30, 2010, at 10:38 AM, <b.gerritsen at nki.nl> wrote:

> Dear all,
> 
> Import of a high content plate from the BD Pathway into omero 4.2 failed after having successfully imported one or two similar plates just before it. At the time of failure I was using the omero.web interface to look at already imported images when suddenly the web interface became unresponsive and the import of the second or third 384 well plate failed. Although a database busy exception is thrown by omero, the postgresql database was still responsive to another program that was using the same posgresql server. Included in the attachments is a snippet from the blitz log where the first exception occurred and the output from the command "omero admin diagnostics".
> 
> I would appreciate it if you could take a look and maybe point me in the direction to solving this issue.
> 
> Kind Regards,
> Bram