No. Details below ... I have since done the following:
Rewrote without ownet or owpython to read directory listings from owserver mounted on owfs. Sensor directory still disappears. Stopping running owserver and mounted owfs directly to interface. Sensor directory still disappears, after 10-20 reads. The thing that is so bizarre is that what makes it fail is code that is totally unrelated to owfs. I can run this forever: https://github.com/iinnovations/iicontrollibs/blob/master/cupid/mytest.py I can also run the read operations in owfslib (where the functions live), as I have been for years, without anything disappearing. But the same calls in the middle of this will make the bus disappear, after an inconsistent number of reads. https://github.com/iinnovations/iicontrollibs/blob/master/cupid/updateio.py I've noted that when using pyownet it would systematically fail quickly if I included all of the query build and executes, but with only a dab of it I could get it to run for a few reads or more before the directory died. I have noted that on debug start I get the message : owfs fuse: warning: library too old, some operations may not not work I've checked my fuse and it is most recent in my package listing: ii fuse 2.9.0-2+deb7u1 armhf Filesystem in Userspace ii gvfs-fuse 1.12.3-4 armhf userspace virtual filesystem - fuse server ii libfuse2:armhf 2.9.0-2+deb7u1 armhf Filesystem in Userspace (library) I'm going to build and install 2.9p3 as a hail mary here. Any ideas welcome. Colin On 3/29/2014 13:35, paul.alfille wrote: > That's discouraging. Do you have a simple test case that triggers the error? > > > Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone > > > > -------- Original message -------- > From: Colin Reese <colin.re...@gmail.com> > Date: 03/29/2014 1:32 PM (GMT-05:00) > To: "OWFS (One-wire file system) discussion and help" > <owfs-developers@lists.sourceforge.net> > Subject: Re: [Owfs-developers] ow Python makes sensors disappear > > > Well, this isn't quite over yet. Still randomly crapping out. > > Can someone please help me debug this? > > Thanks, > Colin > > > On 3/28/2014 16:52, Colin Reese wrote: > > and ... drum roll ... the answer was to remove all double quotes from > > sqlite query preparation statements in the calling script, escaping > > included single quotes. > > > > I don't understand it, but it fixed it. > > > > Colin > > > > > > > > > > On 3/28/2014 15:55, Stefano Miccoli wrote: > >> Try running > >> > >> owserver --debug > >> > >> and watch for error messages. > >> > >> S. > >> > >> On 28 Mar 2014, at 23:33, Colin Reese <colin.re...@gmail.com > >> <mailto: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> > >>>> <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 > >>>> <mailto:Owfs-developers@lists.sourceforge.net> > >>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers > >>>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> Owfs-developers mailing list > >>> Owfs-developers@lists.sourceforge.net > >>> <mailto: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 > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > 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
