Well I'm watching a bit more, and while it's not perfect, it's definitely much better. It ran for about an hour before it stopped responding. I started seeing more and more of these:
Mar-6-09 17:20:16 [Main_Thread] Info: Main_Thread got connection request Mar-6-09 17:20:16 [Worker_18] Worker_18 wakes up Mar-6-09 17:20:16 [Worker_18] Info: Worker_18 got connection from MainThread - 3/3 Mar-6-09 17:20:16 [Worker_18] Connected: 85.101.226.3:3578 -> 67.159.26.231:25 -> 192.168.0.60:6127 , 64-65 Mar-6-09 17:20:16 [Worker_18] Error: IO-subsystem error - unable to poll read handles on OS Mar-6-09 17:20:16 [Worker_18] Error: IO-handle : IO::Socket::INET=GLOB(0x44d2030c); fileno : 65; call : SMTPTraffic; localIP : 192.168.0.60:4111; peerIP : 192.168.0.60:6127; event : - will remove handle Mar-6-09 17:20:16 [Worker_18] Error: IO-handle : IO::Socket::INET=GLOB(0x3a5eba80); fileno : 64; call : SMTPTraffic; localIP : 67.159.26.231:25; peerIP : 85.101.226.3:3578; event : - will remove handle Mar-6-09 17:20:16 [Worker_18] Disconnected: 85.101.226.3 - command list was 'n/a' - insite 0 SocketCalls Mar-6-09 17:20:16 [Main_Thread] Info: Main_Thread freed by idle Worker_18 in 0.023 seconds Mar-6-09 17:20:16 [Worker_18] Worker_18 will sleep now Unlike before, where once the Poll Handles error started, it was like cancer, and would start filling the logs until everything died, these are more sporadic, and the other threads continue to operate, for the most part. For whatever reason, a great number of these errors, regardless of the thread, shows fileno 64 and 65 in the logs, as shown above. At 05:16 PM 3/6/2009, Scott MacLean wrote: >I've got 14.11 installed and running on my server, and whereas >previous versions would die out after about 5 minutes with Poll >Handles errors, this one has now been running for 20, and it looks >good. I saw only one instance of a Poll Handles error: > >Mar-6-09 16:54:51 [Worker_9] Error: IO-subsystem error - unable to >poll read handles on OS >Mar-6-09 16:54:51 [Worker_9] Error: IO-handle : >IO::Socket::INET=GLOB(0x2c529854); fileno : 25; call : SMTPTraffic; >localIP : 67.159.26.231:25; peerIP : 84.50.208.13:1028; event : - >will remove handle >Mar-6-09 16:54:51 [Worker_9] Error: IO-handle : >IO::Socket::INET=GLOB(0x2c5297dc); fileno : 30; call : SMTPTraffic; >localIP : 0.0.0.0:3335; peerIP : 192.168.0.60:3027; event : - will >remove handle >Mar-6-09 16:54:51 [Worker_9] Disconnected: 84.50.208.13 - command >list was 'EHLO,MAIL FROM' - insite 2 SocketCalls > >Immediately afterward, Worker_9 recovered, and continued to process >mail. This is different from previous instances, where worker threads >would simply go dead and die after a Poll handles error. > >I'll keep watching it, but my fingers are crossed. > >Incidentally, I've upped it to 20 worker threads, as it suggested to >me. Seems to be handling the load quite well, just about a gig of RAM in use. >------------------------------------------------------------------------------ >Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA >-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise >-Strategies to boost innovation and cut costs with open source participation >-Receive a $600 discount off the registration fee with the source code: SFAD >http://p.sf.net/sfu/XcvMzF8H >_______________________________________________ >Assp-test mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
