Could it be that I poll the same device (26.6447E7000000) on different
readings (temperature and vis) at the same time? And that it some how hangs?
Polling is made from bash scripts invoked using crontab at the same
intervall.
-Patrik
Den 9 mars 2010 21.29 skrev Patrik Åkerfeldt <[email protected]>:
> I've been adding a new device to my 1-wire network that I regularly poll (a
> solar sensor + temp from hobby-boards). Since then (I think!), owserver
> seems to stop responding after a while. Sometimes it takes 6-10h before it
> "hangs" and sometimes just a couple of minutes.
>
> The last time I started owserver with --error_level=9 and this is the
> output when owserver is malfunctioning:
>
> DEBUG: to_client.c:ToClient(63) Send delay message
> DEBUG: handler.c:SingleHandler(239) NOPING handler {43}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(229) PING handler {51}
> /26.6447E7000000/temperature
> DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
>
> DEBUG: to_client.c:ToClient(63) Send delay message
> DEBUG: handler.c:SingleHandler(239) NOPING handler {53}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {55}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(239) NOPING handler {60}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {59}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(229) PING handler {57}
> /26.6447E7000000/temperature
> DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
>
> DEBUG: to_client.c:ToClient(63) Send delay message
> DEBUG: handler.c:SingleHandler(239) NOPING handler {47}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {45}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(239) NOPING handler {49}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(239) NOPING handler {43}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {51}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {53}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {55}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(239) NOPING handler {60}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(239) NOPING handler {59}
> /26.6447E7000000/vis
> DEBUG: handler.c:SingleHandler(239) NOPING handler {57}
> /26.6447E7000000/temperature
> DEBUG: handler.c:SingleHandler(229) PING handler {47}
> /26.6447E7000000/temperature
> DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
>
>
> I can't tell what's wrong from these messages but perhaps somebody else
> can?
> The issue is temporary resolved by restarting owserver.
>
> owserver is started this way: /opt/owfs/bin/owserver -u -p 3001
> --usb_regulartime --timeout_volatile=0 --foreground --error_level=9
> Running owserver from owfs-2.7p26.
>
> Thanks,
> -Patrik
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
