Thomas, Yes, Telnet was run on same system as ASSP. MTA is on same system. I had open terminal session to system. I opened a command prompt and telnet to MTA. No issue.
CPU usage was minimal. ASSP ran for 10 hours with no issue. However, start up was just after local midnight, The first 7 hours are extremely light. Under load, It wouldn't run for more than 2-3 hours. ASSP system is running as a virtual. No issue with three other virtuals on host system. System is mostly idle. I rolled back assp.pl and started. Michael Thomas Mathbox 978-687-3300 Toll Free: 1-877-MATHBOX (1-877-628-4269) On 4/30/2013 3:27 AM, Thomas Eckardt wrote: > Michael, > >> Note below that 208.69.48.43:125 is the correct IP/port. Also, Telnet to >> 208.69.48.43 125 returned immediate SMTP response. > > did you start the telnet from the assp system to 208.69.48.43:125? > >> 13-Apr-29 14:14:54 [Main_Thread] Warning: poll cycle has taken >> 28.9289960861206 seconds - it is too long > > Seems your OS was going crasy. The maximum time used for a poll cycle is > exactly one second. The call to the OS-poll call is out of our controll. > In human words assp and perl are telling the OS: tell me all registered > sockets that could be handled by me now (read/write) - do this as fast as > possible, if at least one socket is available or there are sockets in an > error condition - otherwise you should wait, but to a maximum of one > second. > > If the worker knows that he has also some other work to do at this time, > the max-wait-time is reduced to some microseconds - which was the case in > your example. > > So, if the call to poll takes ~29 seconds - the OS has taken this time for > any of 1000 reasons. > In the past I saw this behavior in case of a NIC reset or switch error - > or if all cores were running at 100% because of an overload (caused by any > application). > > Thomas > > > > > Von: Michael Thomas <[email protected]> > An: ASSP development mailing list <[email protected]>, > Datum: 29.04.2013 21:51 > Betreff: [Assp-test] Build 113118 - Workers stuck - ASSP crashed > > > > Thomas, > > Note below that 208.69.48.43:125 is the correct IP/port. Also, Telnet to > 208.69.48.43 125 returned immediate SMTP response. > > 13-Apr-29 14:14:25 [Worker_2] Worker_2 wakes up > 13-Apr-29 14:14:25 [Worker_2] Info: Worker_2 got connection from > MainThread > 13-Apr-29 14:14:25 [Worker_2] *** 208.69.48.43:125 didn't work, trying > others... > 13-Apr-29 14:14:25 [Worker_2] Couldn't create server socket to > 208.69.48.43:125 -- aborting connection > 13-Apr-29 14:14:25 [Main_Thread] Info: Main_Thread freed by idle > Worker_2 in 0.018 seconds > 13-Apr-29 14:14:25 [Worker_2] [SMTP Status] 421 > <mx03-scanner.mathbox.net> service temporarily unavailable, closing > transmission > 13-Apr-29 14:14:54 [Main_Thread] Warning: poll cycle has taken > 28.9289960861206 seconds - it is too long > 13-Apr-29 14:14:54 [Worker_4] Warning: poll cycle has taken > 29.1989479064941 seconds - it is too long > 13-Apr-29 14:14:54 [Worker_1] Warning: poll cycle has taken > 28.2500360012054 seconds - it is too long > 13-Apr-29 14:14:54 [Worker_5] Warning: poll cycle has taken > 28.2487299442291 seconds - it is too long > --------------------------------------------- > 13-Apr-29 14:15:57 [Main_Thread] Warning: Main_Thread is unable to > transfer connection to any worker - try again! > 13-Apr-29 14:16:28 [Main_Thread] Warning: Main_Thread is unable to > transfer connection to any worker - try again! > 13-Apr-29 14:16:59 [Main_Thread] Warning: Main_Thread is unable to > transfer connection to any worker - try again! > 13-Apr-29 14:17:30 [Main_Thread] Info: Loop in Worker_2 was not active > for 185 seconds > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_2 : last sigoff in main, > sub main::ThreadStart, 47, main::ThreadMain, 1, , , at 13-29-3 14:1422 > 1367259262.71313 - 8 > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_2 : last sigon in main, > sub main::ThreadStart, 47, main::ThreadMain, 1, , , at 13-29-3 14:1422 > 1367259262.71302 - 243 > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_2 : last action was : > NoLoopSyswrite - write: 4 > 13-Apr-29 14:17:30 [Main_Thread] Warning: try to terminate > inactive/stucking Worker_2 > 13-Apr-29 14:17:30 [Main_Thread] Info: Loop in Worker_3 was not active > for 185 seconds > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_3 : last sigoff in main, > sub main::DKIMpreCheckOK, 6, main::DKIMpreCheckOK_Run, 1, , , at > 13-29-3 14:1425 1367259265.92567 - 59 > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_3 : last sigon in main, > sub main::SMTPTraffic, 13, main::sigonTry, 1, , , at 13-29-3 14:1425 > 1367259265.92077 - 13 > 13-Apr-29 14:17:30 [Main_Thread] Info: Worker_3 : last action was : > DKIM: SOAs: *.mailengine1 > 13-Apr-29 14:17:30 [Main_Thread] Warning: try to terminate > inactive/stucking Worker_3 > 13-Apr-29 14:17:30 [Main_Thread] Warning: Main_Thread is unable to > transfer connection to any worker - try again! > > > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > > > > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
