Re: Mysterious socket error

Looks like your TCP connection is broken.  revents=0x19/0x19 means 
POLLIN | POLLERR | POLLHUP.

I've been fiddling with beepcore-c for a few months, haven't noticed 
frames getting lost - can you tell how to trigger that kind of error?

Thanks,
Lei

 David C Niemi wrote:

>I am again working on my application built on beepcore-c (under Linux).  
>I occasionally have BEEP sessions (or at least channels) just drop for no
>apparent reason.  The log file shows this:
>
>01/08 10:33:00 beepd-re 2.core start logging
>01/08 10:33:00 beepd-re 2.wrap loaded profile for http://www.adeptech.com/beryllium/BERYL/RECEIVE
>01/08 10:33:00 beepd-re 1.wrap duplicate library libberyl.so, continuing...
>01/08 10:33:00 beepd-re 2.wrap loaded profile for http://www.adeptech.com/beryllium/BERYL/SEND
>01/08 10:33:00 beepd-re 2.wrap listening on 5 (backlog 128)
>01/08 10:33:32 beepd-re 0.wrap wrapper created: 6
>01/08 10:33:32 beepd-re 1.wrap wrote 218 octets
>01/08 10:33:32 beepd-re 1.wrap wrote 15 octets
>01/08 10:33:33 beepd-re 1.wrap read 67 octets
>[...]
>01/08 10:36:04 beepd-re 1.wrap read 18 octets
>01/08 10:36:04 beepd-re 1.wrap wrote 395 octets
>01/08 10:36:04 beepd-re 1.wrap wrote 1913 octets
>01/08 10:36:04 beepd-re 1.wrap wrote 353 octets
>[normal so far]
>01/08 10:36:04 beepd-re 2.wrap id=0 fd=6 revents=0x19/0x19
>01/08 10:36:04 beepd-re 0.wrap socket error: 6
>01/08 10:36:04 beepd-re 0.wrap stopping iostate: 6
>01/08 10:36:04 beepd-re 0.wrap deleting iostate: 6
>
>What is a socket error, and how can I prevent it or recover from it?
>
>I am also seeing problems with frames getting lost, I'm not quite sure 
>why yet but perhaps they are related.  The traffic is over a lightly 
>loaded 100TX network.
>
>>From the peer's perspective, I see messages like this:
>12/30 10:49:16 runberyl 2.wrap id=0 fd=5 revents=0x11/0x1
>12/30 10:49:16 runberyl 0.wrap socket error: 5
>12/30 10:49:16 runberyl 0.wrap stopping iostate: 5
>12/30 10:49:16 runberyl 0.wrap deleting iostate: 5
>12/30 10:49:29 runberyl 2.core start logging
>12/30 10:49:29 runberyl 0.wrap wrapper created: 5
>12/30 10:49:29 runberyl 1.wrap wrote 150 octets
>[...]
>12/30 10:49:29 runberyl 1.wrap wrote 15 octets
>12/30 10:49:29 runberyl 1.wrap read 16 octets
>12/30 10:49:50 runberyl 0.wrap wrapper destroyed: 5
>12/30 10:49:50 runberyl 0.wrap stopping iostate: 5
>12/30 10:49:50 runberyl 0.wrap deleting iostate: 5
>12/30 10:49:50 runberyl 2.core done logging
>
>
>
>
>-------------------------------------------------------
>-- David C. Niemi           Adeptech Systems, Inc.   --
>-- Reston, Virginia, USA    http://www.adeptech.com/ --
>-------------------------------------------------------
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Perforce Software.
>Perforce is the Fast Software Configuration Management System offering
>advanced branching capabilities and atomic changes on 50+ platforms.
>Free Eval! http://www.perforce.com/perforce/loadprog.html
>_______________________________________________
>Beepcore-c-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/beepcore-c-users
>
>





-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html