In 15.00 is nothing changed related to the poll problem ! 

!!!!    will be fixed in 2.0.0_15.01  !!!!

Thomas




Scott MacLean <[email protected]> 
10.03.2009 18:49
Bitte antworten an
ASSP development mailing list <[email protected]>


An
ASSP development mailing list <[email protected]>
Kopie

Thema
Re: [Assp-test] Antwort:  2.0 poll read handles error






I put 15.00 on it, and the same thing is still happening.

I also noticed that it is not necessarily always at the initial 
connection. Sometimes it drops the connection at the end:

Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x330a8800);  fileno : 66; call : SMTPTraffic; 
localIP : 192.168.0.60:2010; peerIP : 192.168.0.60:6127; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Disconnected: 201.67.188.144  - 
command list was 'n/a' - insite 0 SocketCalls
Mar-10-09 12:46:01 [Worker_13] Error: IO-subsystem error - unable to 
poll read handles on OS
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x330c5988);  fileno : 57; call : SMTPTraffic; 
localIP : 192.168.0.60:1878; peerIP : 192.168.0.60:6127; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x330ff70c);  fileno : 54; call : SMTPTraffic; 
localIP : 67.159.26.231:25; peerIP : 189.26.11.141:4270; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Disconnected: 189.26.11.141  - command 
list was 'EHLO,MAIL FROM,RCPT TO,RCPT TO,RCPT TO,RCPT TO,RCPT TO,RCPT 
TO,DATA' - insite 10 SocketCalls
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x101a0420);  fileno : 69; call : SMTPTraffic; 
localIP : 67.159.26.231:25; peerIP : 90.154.242.135:3205; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x331245b8);  fileno : 62; call : SMTPTraffic; 
localIP : 192.168.0.60:1762; peerIP : 192.168.0.60:6127; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x2e4e196c);  fileno : 70; call : SMTPTraffic; 
localIP : 192.168.0.60:2012; peerIP : 192.168.0.60:6127; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Disconnected: 90.154.242.135  - 
command list was 'n/a' - insite 0 SocketCalls
Mar-10-09 12:46:01 [Worker_13] Error: IO-handle : 
IO::Socket::INET=GLOB(0x330c67b0);  fileno : 35; call : SMTPTraffic; 
localIP : 67.159.26.231:25; peerIP : 213.252.76.120:1987; event :  - 
will remove handle
Mar-10-09 12:46:01 [Worker_13] Disconnected: 213.252.76.120  - 
command list was 'EHLO,MAIL FROM,RCPT TO,DATA' - insite 5 SocketCalls
Mar-10-09 12:46:01 [Worker_13] Worker_13 will sleep now


At 01:25 PM 3/10/2009, Thomas Eckardt/eck wrote:

>It is good to know, that ASSP is not dying on this error anymore. The
>early close of the connection will be fixed in 2.0.0_15.01! At this time,
>you can set ConnectionLog to standard to prevent ASSP logging the
>poll-error. But I want you, to let ConnectionLog on verbose, because
>poll.pm returns -1 which meens that the system has a problem to poll the
>IO-handles via clib! This could be happend for several reasons. What I'm
>currently looking for, is to fixup an 'reported' issue in poll.pm . I 
dont
>want to go in to details, this is not the right place to talk about this.
>
>Thomas
>
>
>
>
>
>
>Scott MacLean <[email protected]>
>10.03.2009 17:21
>Bitte antworten an
>ASSP development mailing list <[email protected]>
>
>
>An
>ASSP development mailing list <[email protected]>
>Kopie
>
>Thema
>[Assp-test] 2.0 poll read handles error
>
>
>
>
>
>
>I am still having poll read handles errors occurring on my 2.0.0
>(14.11) (Win2003 Perl 5.8.9) install. The main difference is that
>ASSP is not dying from the errors anymore. However, I now have a new
>problem. When the error occurs, it is when a user first connects,
>before the HELO even occurs. The connection is established, and ASSP
>sends:
>
>421 <servername.com> closing transmission channel
>
>ASSP terminates the connection immediately afterwards.
>
>When this occurs, the following is logged in ASSP:
>
>Mar-9-09 10:38:50 [Worker_17] Worker_17 wakes up
>Mar-9-09 10:38:50 [Worker_17] Info: Worker_17 got connection from
>MainThread - 7/7
>Mar-9-09 10:38:50 [Worker_17] Connected: 99.255.139.87:56212 ->
>67.159.26.231:25 -> 192.168.0.60:6127 , 64-65
>Mar-9-09 10:38:50 [Worker_17] Error: IO-subsystem error - unable to
>poll read handles on OS
>Mar-9-09 10:38:50 [Worker_17] Error: IO-handle :
>IO::Socket::INET=GLOB(0x45c74b84);  fileno : 64; call : SMTPTraffic;
>localIP : 67.159.26.231:25; peerIP : 99.255.139.87:56212; event :  -
>will remove handle
>Mar-9-09 10:38:50 [Worker_17] Error: IO-handle :
>IO::Socket::INET=GLOB(0x3b2f58dc);  fileno : 65; call : SMTPTraffic;
>localIP : 192.168.0.60:1416; peerIP : 192.168.0.60:6127; event :  -
>will remove handle
>Mar-9-09 10:38:50 [Worker_17] Disconnected: 99.255.139.87 - command
>list was 'n/a' - insite 0 SocketCalls
>Mar-9-09 10:38:50 [Main_Thread] Info: Main_Thread freed by idle
>Worker_17 in 0.172 seconds
>Mar-9-09 10:38:50 [Main_Thread] Info: Main_Thread got connection request
>Mar-9-09 10:38:50 [Worker_17] Worker_17 will sleep now
>
>
>I wouldn't mind if this was an occasional event, but it is happening
>enough that I am having multiple users report it, and they are
>complaining loudly. Looking at my ASSP log from 3/9, I see that it
>happened 2735 times in 24 hours (with a message volume of 153,776
>messages received over that same time period). Can we get this poll
>read handles error fixed, or at least figure out what is causing it?
>------------------------------------------------------------------------------
>_______________________________________________
>Assp-test mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>DISCLAIMER:
>*******************************************************
>This email and any files transmitted with it may be confidential, legally
>privileged and protected in law and are intended solely for the use of 
the
>
>individual to whom it is addressed.
>This email was multiple times scanned for viruses. There should be no
>known virus in this email!
>*******************************************************
>
>------------------------------------------------------------------------------
>_______________________________________________
>Assp-test mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/assp-test
------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to