ON attempted restart after error, I get the following, but no additional
messages from owfs or owserver on read fails.
For what it's worth, I've duplicated this on another master with a
different sensor. Same OS image cloned some time ago.
DEBUG: ow_daemon.c:(166) main thread id = 3069485584
CONNECT: ow_avahi_link.c:(68) No Avahi support. Library libavahi-client
couldn't be loaded
CONNECT: ow_dnssd.c:(82) Zeroconf/Bonjour is disabled since dnssd
library isn't found
CALL: ow_parsename.c:(99) path=[]
DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1B
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(397) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(423) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(149) Cannot detect an i2c DS2482-x00 on /dev/i2c-1:ALL
DEFAULT: owlib.c:(56) No valid 1-wire buses found
DEBUG: ow_exit.c:(18) Exit code = 1
CALL: ow_lib_close.c:(21) Starting Library cleanup
CALL: ow_lib_stop.c:(23) Clear Cache
DEBUG: ow_cache.c:(296) Flipping cache tree (purging timed-out data)
DEBUG: ow_cache.c:(314) flip cache. tdestroy() will be called.
DEBUG: ow_cache.c:(296) Flipping cache tree (purging timed-out data)
DEBUG: ow_cache.c:(314) flip cache. tdestroy() will be called.
CALL: ow_lib_stop.c:(25) Closing input devices
CALL: ow_lib_stop.c:(27) Closing output devices
DEBUG: ow_connect_out.c:(56) Freeing outbound (null) #0
CALL: ow_lib_close.c:(35) Finished Library cleanup
DEBUG: ow_lib_close.c:(43) Libraries closed
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
