[ome-users] Thing we've got a bug with 4.4.3 - moving files from one owner/group to another.

Josh Moore josh at glencoesoftware.com
Tue Sep 11 09:54:05 BST 2012


On Sep 11, 2012, at 10:43 AM, Jake Carroll wrote:

> Josh,
> 
> Please find attached the Blitz.log.

Thanks for the log, Jake.

Judging on the basis of just the Blitz log, it is likely the same issue. Once a fix is available for 9435 you can either try it out yourself, or if you would like to send a database dump, I can try it out here.

That being said, it concerns me that you can no longer find the file. I can see in the log that you try to move Project 156 to the system group (id=0). When this fails:

2012-09-11 09:49:48,065 INFO  [                 org.perf4j.TimingLogger] (2-thread-5) start[1347320988064] time[1] tag[omero.chgrp.step.ome.model.acquisition.FilterSetExcitationFilterLink.child]
2012-09-11 09:49:48,066 INFO  [                 org.perf4j.TimingLogger] (2-thread-5) start[1347320988065] time[1] tag[omero.chgrp.step.ome.model.acquisition.LightPathExcitationFilterLink.child]
2012-09-11 09:49:48,067 INFO  [                 org.perf4j.TimingLogger] (2-thread-5) start[1347320988059] time[8] tag[omero.request.step.115]
2012-09-11 09:49:48,070 INFO  [        omero.cmd.basic.DoAllI. at 69652a97] (2-thread-5) Cancelled

The transaction should be rolled back, leaving the project in the previous group. Does it re-appear if you refresh and/or logout and back in?

Cheers,
~Josh


> It's 11MB. It'll uncompress to around 370MB.
> 
> Luke - can you provide Josh the insight-log from your laptop, please?
> 
> Thanks.
> 
> --JC
> 
> On 11/09/12 6:21 PM, "Josh Moore" <josh at glencoesoftware.com> wrote:
> 
>> 
>> On Sep 11, 2012, at 2:00 AM, Jake Carroll wrote:
>> 
>>> Hi,
>> 
>> Hi Jake,
>> 
>>> I think we have a bug in 4.4.3, running on:
>>> 
>>> Linux omero 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC
>>> 2012 x86_64 x86_64 x86_64 GNU/Linux
>>> * ICE install is 3.4
>>> * Backend omero storage is off a high performance 10GbE NFS host.
>>> * 4 x vCore's
>>> * 16GB of RAM.
>>> 
>>> It would appear that when a user attempts MOVE a file in the insight
>>> client into a different GROUP, a warning comes up, says (after trying to
>>> move the image for a few seconds), "Unable to move file". At this point,
>>> we go hunting in the location again, and the file is gone/deleted. We
>>> then login as the "super" or all powerful/all permitted user, and the
>>> file is not there either. Almost as if it's disappeared completely.
>>> 
>>> We're wondering if it's possible to recover the file that Omero seams
>>> to have eaten!
>>> 
>>> Kind of worried about this, given we'd like to use Omero as a
>>> production image and analysis system for large scale microscopy
>>> facilities!
>>> 
>>> Any logs you need, or duplication steps you'd like us to take ­ please
>>> let us know ASAP. We want to make this work as well as it can.
>> 
>> This may be related to [9435], which will be included in the upcoming
>> release. Could you send your insight log (~/omero/log/omeroinsight.log)
>> and your server log (var/log/Blitz-0.log) so we can verify?
>> 
>> Thanks,
>> ~Josh.
>> 
>> 
>>> Thank you for your time.
>>> 
>>> --JC
>>> 
>> 
>> [9435] https://trac.openmicroscopy.org.uk/ome/ticket/9435
>> 
> 
> <Blitz-0.log.bz2>




More information about the ome-users mailing list