On 10/03/2017 02:25 AM, Thomas Eckardt wrote: >>How do I discover what ASSP is doing when it gets so busy? > > GUI -> Worker-Status ???... > Here is a typical result: 1 0 s idle or damping 2 47 s sleeping 3 35 s sleeping 4 49 s sleeping 5 21 s sleeping 10000 1 s idle loop (5 s) 10001 23062 s schedule waiting
From the log when ASSP is shut down. I have noticed Worker_1 *always* has connections that must time out. Yet the worker monitor often shows it as sleeping. Worker_10001 is for the Rebuildspam scheduler? 2017-10-03_11:20:01 Initializing shutdown sequence 2017-10-03_11:20:01 Info: removing all SMTP and Proxy listeners 2017-10-03_11:20:01 Worker_1 has active connections. Will wait until all connections are finished but max 45 seconds! 2017-10-03_11:20:01 Waiting for all SMTP-Workers to be finished 2017-10-03_11:20:02 Worker_2 finished 2017-10-03_11:20:02 Worker_4 finished 2017-10-03_11:20:02 Worker_3 finished 2017-10-03_11:20:02 Worker_5 finished 2017-10-03_11:20:46 208.76.24.45 info: wrote all current available connection data to file /usr/local/bin/assp2/debug/con10.txt 2017-10-03_11:20:46 Worker_1 finished 2017-10-03_11:20:46 SMTP Workers finished 2017-10-03_11:20:46 Waiting for high Workers to be finished 2017-10-03_11:20:47 Worker_10000 finished 2017-10-03_11:20:50 Info: RebuildSpamdb Scheduler stopped 2017-10-03_11:20:52 Worker_10001 finished 2017-10-03_11:20:52 High workers finished work -- James Moe moe dot james at sohnen-moe dot com 520.743.3936 Think. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
