[ome-users] (no subject)

Josh Moore josh at glencoesoftware.com
Mon Aug 30 13:27:18 BST 2010

Hi Bram,

Not turning off the server was a good idea. Can you do the following:

	kill -QUIT `bin/omero admin ice server pid Blitz-0`

and then also send the output of master.out? It should have something of the form:

	Full thread dump Java HotSpot(TM) 64-Bit Server VM (16.3-b01-279 mixed mode):

in there.


On Aug 30, 2010, at 1:59 PM, <b.gerritsen at nki.nl> wrote:

> Hello Josh,
> The entire file is >60MB. What I sent to you is a snippet of the first exception in the Blitz-0 file. Most of the log is a repeat of this exception with several others mixed in. I can no longer log into omero.web (it shows the log-in screen though). To add some more information I'll copy and paste a few extra pages from the log. See the attachment.
> I didn't shut down omero because it might be possible to glean more of its error state, so the log file has been growing quite a bit in the mean-time.
> Kind Regards,
> Bram
> ________________________________________
> From: Josh Moore [josh at glencoesoftware.com]
> Sent: Monday, August 30, 2010 12:14 PM
> To: Bram Gerritsen
> Cc: ome-users at lists.openmicroscopy.org.uk
> Subject: Re: [ome-users] (no subject)
> 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
> <Blitz-0_1000lines.log>

More information about the ome-users mailing list