>but there is no BDB DB or ENV file there BDB file is for example whitelist.bdb for each BDB there is a subfolder in tmpDB, which contains the ENV files __db.001 to __db.00x
does it make sense to have both import files ? /Applications/assp/mysql/dbimport/whitelist.rpl and /Applications/assp/mysql/dbimport/whitelist.add if the whitelist.bdb is destroyed - repair it - remove the tmpDB/whitelist ( I refer to the oracle BDB documentation - how to repair a BDB) OR - remove it - remove the tmpDB/whitelist - copy a known good backup to /Applications/assp/mysql/dbimport/whitelist.add - start assp. (same for each DB) If there is a BDB problem at startup - you'll not see it in the maillog.txt. You need to disable the daemon-mode (--AsADaemon:=0) and to start assp at commandline. make a copy of assp.cfg or record the setting for AsADaemon (or change this value) perl /Applications/assp/assp.pl /Applications/assp --AsADaemon:=0 Shared BerkeleyDB's are subject to get destroyed if the engine (the controlling thread) was not shutdown cleanly - e.g. rc script does not wait, the system was crashing, assp was crashing For this reason, I don't recommend to use BerkeleyDB in production mode. BerkeleyDB is really fine if it runns well, but hard to handle if it failes. Thomas Von: "James Brown via Assp-test" <assp-test@lists.sourceforge.net> An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> Kopie: "James Brown" <jlbr...@bordo.com.au> Datum: 22.01.2019 08:09 Betreff: Re: [Assp-test] ASSP failing to startup with BerkeleyDB Thanks Thomas. I deleted everything in tmpDB, set useBerkeleyDB to 1 and restarted ASSP: Jan-22-19 17:46:56 [init] All Threads are started Jan-22-19 17:46:56 [init] Info: CPU priority changed for Worker_10000 from 31 to 2 Jan-22-19 17:46:56 [init] Info: CPU priority changed for Worker_10001 from 31 to 2 Jan-22-19 17:46:56 [init] Try using BerkeleyDB database <> for selected tables Jan-22-19 17:46:56 [init] Info: list Whitelist is using 'BerkeleyDB' version 6.0 - cachesize is 12.5MB Jan-22-19 17:46:57 [init] Database import started for table whitelist Jan-22-19 17:46:57 [init] Backup: starting backup database table Whitelist to file /Applications/assp/mysql/dbbackup/whitelist - keeping 10 backup versions Jan-22-19 17:47:00 [Worker_10001] Info: starting RebuildSpamdb Scheduler with '0 1 * * *' - next RebuildSpamdb is scheduled for Jan-23-19 01:00:00 Jan-22-19 17:47:13 [init] Backup: 1,366,838 records of database table Whitelist to file /Applications/assp/mysql/dbbackup/whitelist Jan-22-19 17:47:13 [init] Replacing records in table whitelist with records in file /Applications/assp/mysql/dbimport/whitelist.rpl Jan-22-19 17:47:14 [init] Adding records in file /Applications/assp/mysql/dbimport/whitelist.add to table whitelist Jan-22-19 17:47:14 [init] Successfully added 1 records in to BerkeleyDB Whitelist And then nothing. :-( The tmpDB folder was repopulated, but there is no BDB DB or ENV file there. James. On 22 Jan 2019, at 5:30 pm, Thomas Eckardt <thomas.ecka...@thockar.com> wrote: There are no changes related to BerkeleyDB in build 19019. It looks like any BDB DB or ENV (in tmpDB) is destroyed. shutdown assp clean the tmpDB folder start assp On nix and MAC this is mostly caused by a bad shutdown script. EVERY rc shutdown script has to wait untill the assp is finished - which may take up to 45 seconds (MaxFinConWaitTime). Examples for rc scripts are in the rc folder. All threads are sharing the BDB. Large parts of the BDB DB but at least the BDB-ENV are shared in memory. At shutdown the last terminating thread is waiting until all other threads are finished - then it closes all BDB DB's and ENV (writes them to disk) and terminates itself. If the rc script does not wait at shutdown, the BDB files are left at an opened state - which may or may not prevent them from being opened again (at next start). Thomas _______________________________________________ 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
