Try running owserver --debug
and watch for error messages. S. On 28 Mar 2014, at 23:33, Colin Reese <colin.re...@gmail.com> wrote: > I've no idea where to even start on this. > > > On 3/28/2014 14:49, Stefano Miccoli wrote: >> This error is entirely on the owserver side... owpython and the friends >> seem not to be responsible. >> >>> pyownet.protocol.OwnetError >> >> exceptions are raised when the remote owserver answers with an error >> code, in this case -5, that according to >> >> owserver --help=error >> >> is >> >> 5. legacy - IO error >> >> you shoud inspect the owserver code to find out. >> >> Stefano >> >> On 28 Mar 2014, at 22:23, Colin Reese <colin.re...@gmail.com >> <mailto:colin.re...@gmail.com>> wrote: >> >>> And I've now successfully duplicated the error in pyownet: >>> >>> File "/usr/lib/iicontrollibs/cupid/owfslib.py", line 27, in owbuslist >>> for dir in OwnetProxy(host).dir(): >>> File "/usr/lib/iicontrollibs/resource/pyownet/protocol.py", line 408, >>> in dir >>> raise OwnetError(-ret, self.errmess[-ret], path) >>> resource.pyownet.protocol.OwnetError: [Errno 5] legacy - IO error: '/' >>> >>> What on earth is nuking the directory? >>> >>> Colin >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > > ------------------------------------------------------------------------------ > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
