>I tried to see where SaveConfig() SaveConfig() is called in the Main_Thread (Worker_0) every time, anything in the assp configuration was changed. And under normal cirumstances, after that, all workers are told to check there configuration (and reload) in relation to the new one (lists, files, recompile regexes ....).
> I >>think<< if I would have a problem with >"Saving config"< (which is a maintenance task) - I would increase the 'MaintenanceLog' level if I would have a problem with workers >"unable to transfer connection to any worker"< - I would enable WorkerLog and WorkerLogging example log: Oct-25-21 23:12:58 [Worker_10000] Downloading level-2-TLDlist via direct HTTP connection Oct-25-21 23:12:58 [Worker_10000] Level-2-TLDlist download completed Oct-25-21 23:12:58 [Worker_10000] Downloading level-3-TLDlist via direct HTTP connection Oct-25-21 23:12:59 [Worker_10000] Level-3-TLDlist download completed Oct-25-21 23:12:59 [Worker_10000] Info: next TLDlist download in 1 day 5 hours 58 minutes Oct-25-21 23:12:59 [Worker_10000] Info: file c:/assp/files/URIBLCCTLDS.txt updated for URIBLCCTLDS Oct-25-21 23:13:00 [Main_Thread] Saving config Oct-25-21 23:13:00 [Main_Thread] Info: no configuration changes detected - nothing to save - file c:/assp/assp.cfg is unchanged Oct-25-21 23:13:00 [Main_Thread] Adminupdate: file 'c:/assp/files/URIBLCCTLDS.txt' for config 'URIBLCCTLDS' was changed Oct-25-21 23:13:00 [Main_Thread] Option list file: 'c:/assp/files/URIBLCCTLDS.txt' reloaded (URIBLCCTLDS) with 12,280 records Oct-25-21 23:13:02 [Worker_1] Worker_1 wakes up Oct-25-21 23:13:02 [Worker_5] Worker_5 wakes up Oct-25-21 23:13:02 [Worker_4] Worker_4 wakes up Oct-25-21 23:13:02 [Worker_3] Worker_3 wakes up Oct-25-21 23:13:02 [Worker_2] Worker_2 wakes up Oct-25-21 23:13:03 [Worker_1] Worker_1 finished reloading configuration Oct-25-21 23:13:03 [Worker_1] Worker_1 will sleep now Oct-25-21 23:13:04 [Worker_2] Worker_2 finished reloading configuration Oct-25-21 23:13:04 [Worker_2] Worker_2 will sleep now Oct-25-21 23:13:05 [Worker_3] Worker_3 finished reloading configuration Oct-25-21 23:13:05 [Worker_3] Worker_3 will sleep now Oct-25-21 23:13:06 [Worker_4] Worker_4 finished reloading configuration Oct-25-21 23:13:06 [Worker_4] Worker_4 will sleep now Oct-25-21 23:13:07 [Worker_5] Worker_5 finished reloading configuration Oct-25-21 23:13:07 [Worker_5] Worker_5 will sleep now Oct-25-21 23:13:08 [Worker_10000] Worker_10000 finished reloading configuration Oct-25-21 23:13:10 [Worker_10001] Worker_10001 finished reloading configuration Oct-25-21 23:13:29 [Worker_10000] Downloading Extended Droplist via direct HTTP connection Oct-25-21 23:13:29 [Worker_10000] Extended Droplist already up to date Oct-25-21 23:13:29 [Worker_10000] Info: next droplist download in 7 hours 34 minutes debug may help for time related debugging, I (or some one who read the manual) would consider to use ConfigChangeSchedule notice: analyzing all the produced debug files (in general debug mode) is a very time consuming task Check your option files for bad (too greedy) regular expressions. Check, if there are other processes modifying assp files. Check that required services (DNS, SQL,ClamAV,..... ) are responsive at this time. If (for any reason) it is expected, that the config reload takes 30 seconds or longer - 'ConnectionTransferTimeOut' should be changed - or the "Warning: Main_Thread is unable to transfer connection to any worker - try again!" should be ignored. If the reload takes X seconds for the MainThread. Within these X seconds all new connections are queued by the OS. After this time (the reload) the MainThread tries to transfer all these new connections within some (milli)seconds to the workers - this may overload the SMTP-workers for some time. Thomas Von: "K Post" <nntp.p...@gmail.com> An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> Datum: 25.10.2021 17:20 Betreff: Re: [Assp-test] Main_Thread is unable to transfer connection to any worker - try again We are lucky to have a new (to us) faster server donated since this original May posting on the "unable to transfer connection to any worker" error. However, with the new box with Windows 2019 installation, fully patched, MySQL latest community, and Strawberry perl 5.32 it's still happening in spurts. Not a heavy load, 16gb ram. 12 cores total. ASSP uses about 1.7gb after running for a bit. MySQL seems fast, ClamAV in use. Sometimes I get the warning just once in a day, often it's every 5 minutes for a while. This morning, there were 3 occurrences with 10 minutes in between each. But always, when I look at the log, it's right after the "Saving config" process, always when there's no config changes. I tried to see where SaveConfig() is being called from every 5 minutes. I >>think<< it's when the ReloadOptionFiles timer hits, but I'm not sure. ReloadOptionFiles is set to 300 (5 minutes) AutoReloadCfg is enabled, though I'm never modifying assp.cfg without using the GUI What else should I be looking at? >From today: Oct-25-21 11:09:24 Saving config Oct-25-21 11:09:24 Info: no configuration changes detected - nothing to save - file d:/assp/assp.cfg is unchanged (a message processed) Oct-25-21 11:09:57 Info: notification message queued to sent to assp-not...@ourcharity.org Oct-25-21 11:09:57 Warning: Main_Thread is unable to transfer connection to any worker - try again! assp acts normally for 10 minutes, then: Oct-25-21 11:19:28 Saving config Oct-25-21 11:19:28 Info: no configuration changes detected - nothing to save - file d:/assp/assp.cfg is unchanged Oct-25-21 11:20:00 Info: notification message queued to sent to assp-not...@ourcharity.org Oct-25-21 11:20:00 Warning: Main_Thread is unable to transfer connection to any worker - try again! assp resumes Oct-25-21 11:29:32 Saving config Oct-25-21 11:29:32 Info: no configuration changes detected - nothing to save - file d:/assp/assp.cfg is unchanged (a single message processed fine here) Oct-25-21 11:30:04 Info: notification message queued to sent to assp-not...@ourcharity.org Oct-25-21 11:30:04 Warning: Main_Thread is unable to transfer connection to any worker - try again! On Mon, May 17, 2021 at 8:53 PM K Post <nntp.p...@gmail.com> wrote: I'm desperate for help. It seems that ASSP has thread problems frequently when it reloads the config. I see warnings that the Main_Thread is unable to transfer connection to any worker, often every 5 minutes for hours. May-17-21 20:40:35 Saving config May-17-21 20:40:35 Info: no configuration changes detected - nothing to save - file c:/assp/assp.cfg is unchanged May-17-21 20:41:08 Info: notification message queued to sent to assp-not...@ourcharity.org May-17-21 20:41:08 Warning: Main_Thread is unable to transfer connection to any worker - try again! Even when there's no settings detected (line 2 above), it can hang. I can't seem to figure out why. Windows 2012 R2 Strawberry Perl Latest ASSP Any guidance on where to start? Thank you _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net 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 Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
