[ome-users] OmeroBeta 4.0.2 - Instalation Problems

[Colin Blackburn]

Mathieu Marchand wrote:
> Hi

Hi Mathieu,

> I have the exact same problem with OMERO.FS and pyinotify 0.7.1 on
> Centos 5.2 x86
> I have tested pyinotify 0.7.1 separately from Omero to monitor a
> directory and it seems to work.
> I can't test easily with pyinotify 0.8.x as it requires python 2.5 and
> my system defaults with python 2.4

I think there is an import problem (at least for OMERO.fs) for pyinotify 
0.7.x depending on how it was installed. Could you to let me know the 
full path for the file pyinotify.py ?

> The omero server/clients seems unaffected by this problem, but the CPU
> usage is much higher (probably the omero.fs trying to restart).

There should only be a limited number of retries. I'll look into why 
this might not be happening for this exception.

Cheers,

Colin


> 2009-05-01 10:43:09,080 INFO: fs.fsRunFSDropBox - Trying to start
> OMERO.fs DropBox client
> 2009-05-01 10:43:12,821 ERROR: fs.fsMonitorServer - Failed to create
> monitor: 'module' object has no attribute 'IN_CLOSE_WRITE'
> 2009-05-01 10:43:12,823 ERROR: fs.fsDropBox - Failed to access proxy :
> Traceback (most recent call last):
>   File "/usr/local/omero/lib/python/fsDropBox.py", line 81, in run
>     config.blacklist, pathMode, mClientProxy)
>   File "/usr/local/omero/lib/python/omerofs_ice.py", line 311, in createMonitor
>     return _M_monitors.MonitorServer._op_createMonitor.invoke(self,
> ((eType, pathString, whitelist, blacklist, pMode, proxy), _ctx))
> OmeroFSError: exception ::monitors::OmeroFSError
> {
>     reason = Failed to create monitor: 'module' object has no
> attribute 'IN_CLOSE_WRITE'
> }
> 
> 
> 
> 
>