Thank you Thomas!! I will run through these steps this weekend and report back.
On Wed, Sep 29, 2021 at 12:03 PM Thomas Eckardt <thomas.ecka...@thockar.com> wrote: > - check all the setting for the lists and hashes to be set to 'DB:' (using > mysql) > - check that the mysql server is working correctly (if not assp will > failover to plain files) > - check all settings related to the rebuildspamdb > - shutdown assp > - clear the folder 'tmpDB' > - remove all 'griplist....' related files from assp root folder > - check the file time of the assp.cfg (written at assp shutdown) > - check that the last line in assp.cfg is 'ConfigSavedOK:=1' > > - start assp at commandline > - wait 10 minutes , watch the log for normal maintenance > - stop assp > - start it as service > - wait 10 minutes > - start a rebuildspamdb task from the GUI or cmdqueue (in doubt enable the > debugging for the rebuild) > - wait until this task is finished > - stop assp > > - start assp from commandline - everythng should work like expected > - stop assp > - start the service > > Thomas > > > Von: "K Post" <nntp.p...@gmail.com> > An: "ASSP development mailing list" < > assp-test@lists.sourceforge.net> > Datum: 29.09.2021 16:41 > Betreff: [Assp-test] Rebuild SpamDB worker thread at startup hangs > ------------------------------ > > > > If I restart my server or just the ASSP windows service, I've discovered > that ASSP generally will no longer fully start automatically as a service. > I'm sure there's something misconfigured, corrupt, or broken on my > machine. If the Windows server crashes or does an after hours update > restart, ASSP needs to be started from the command line before it'll run > as a service, which presents a big problem. > > *The service does always run, but I cannot connect to the GUI nor to SMTP.* > At start, it uses about 10% of processor as expected. In task manager, I > see memory usage go ~300mb, ~600mb, then up to 984mb and stop. CPU then > goes down to 0.0% or 0.1% and it just hangs. In testing, I've left it for > over an hour like this. It just sits. No SMTP, no GUI. RAM usage stays > at 984mb. Nothing in maillog, nothing in the Windows system log that I can > find. > > If I start from command line, ASSP will work, but there is a delay on the: > starting rebuild SpamDB worker thread > line, memory sits at 984mb, then after a two minutes or so, memory grows a > bit more, I'll get the [OK] on the starting rebuild SpamDB line, and SMTP > and the GUI *start to work*. It'll run like this quite happily forever. > > I want it running as a service though, so I'll ctrl+c, then start ASSP > from the services manager. Task manager will show it again pausing at > 984mb, but this time, it always continues and operates normally! So the > temporary fix is to start on command line, ctrl+c, then start the service > normally. > > Everything is up to date, including all modules. I'm using MySQL. > useDB4Rebuild is checked > RebuildEsesFileModel is unchecked, though I did try this when it first > became an option. I turned it off because it used so much RAM and my > rebuild is already under 45 minutes. Could there be something lingering > because of this? > > Can you suggest anything that I should be checking? > Is there something that starting ASSP from command line could be clearing > out or resolving that starting it as a service wouldn't? > Is there a debug switch that would capture what's happening at this very > early stage of startup? There doesn't seem to be anything written to the > logs at all. > > I'm making do as is, but sure would like to fix this issue. > > 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 >
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
