Which version are these error messages from?

On Sat, May 28, 2011 at 4:17 AM, Michael Weber <[email protected]> wrote:
> I analysed the crashes a bit more and noticed:
>
> a. owserver does not run at all if I do not use "flex timing"
> b. if I turn off fifo-buffering at the terminal server, and enable 
> hardware-flowcontrol, things appear more stable (fewer crashes)
> c. all crashes appear to be after a TRAFFIC OUT to a file descriptor, like:
>
> TRAFFIC OUT <to server data> file descriptor=12
> Byte buffer FD, length=12
> --000: 20 20 20 20 20 31 39 2E 31 38 37 35
>   <     19.1875>
> CRASHED Fri May 27 16:03:57 UTC 2011
>
> We always had write and read problems before, because we have long bus lines, 
> but for a long time now the owserver daemon(s) were rock solid, and the 
> bottom line was that things worked well except during really dry periods (and 
> I guess most components in the chain are not specified for single-digit 
> humidity values).
>
> Michael
>
>
> Am 27.05.2011 um 12:47 schrieb Michael Weber:
>
>> We had a owserver 2.7p17 running on an old debian server, without problems. 
>> We read from 3 serial devices (via a MOXA terminal server) using 
>> python/ownet and java/ownet interfaces. there is only one instance from the 
>> java part, and one from the python part, so there could be at most two 
>> requests at the same time.
>>
>> Everything went fine until we replaced the server with a new one running 
>> debian squeeze. First we tried owfs 2.8p8, but owserver crashed very 
>> frequently. Then we moved back to 2.7p17 and also tried 2.7p39: Here 
>> owserver froze (no answers) but the daemon was still there. Now we moved 
>> back to 2.6p9 and monitor the daemon and restart it when necessary. Not a 
>> very stable configuration.
>>
>> The logfile just before it crashed one time yesterday looks like this, I 
>> think it is strange that the TRAFFIC IN occurs at the moddle of the line 
>> just before the crash.
>>
>> Any ideas would be greatly appreciated.
>>
>> TRAFFIC IN  <NETREAD> bus=0 (/dev/ttyr04)
>> Byte buffer DS9097U, length=2
>> --000: 1F B2
>>   <..>
>> TRAFFIC OUT <to server data> file descriptor=9
>> Byte buffer FD, length=0TRAFFIC IN  <NETREAD> bus=2 (/dev/ttyr05)
>> Byte buffer DS9097U, length=9
>> --000: 40 01 C2 FF 7F FF 10 10 DD
>>   <@........>
>> TRAFFIC OUT <to server data> file descriptor=12
>> Byte buffer FD, length=12
>> --000: 20 20 20 20 20 20 20 20 20 20 32 30
>>   <          20>
>>
>>
>> Michael
>
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to