Hi Thomas,
I didn't have to wait long, it turns out two runs of rebuildspamdb are
enough to fill a 1GB tempdb folder now.
I have added the entry and ASSP starts back up without coredumping. tmpDB
does remain 100% full though
Has anything changed recently that would increase the tmpDB
Hi all.
Since clearing the tempdb folder rebuilds have slowed to a crawl.
The affected part is griplist and bounce reports as per logs:
2014-04-09 23:40:33 building new GripList records and bounce report
2014-04-09 23:40:33 processing Logfile /usr/local/assp/maillog.txt
2014-04-10 07:00:15
check ulimit
Thomas
Von:James Brown jlbr...@bordo.com.au
An: ASSP development mailing list assp-test@lists.sourceforge.net,
Datum: 10.04.2014 03:30
Betreff:[Assp-test] Upgraded Perl, now getting error re
BerkeleyDB Too many open files
I took Thomas’s suggestion and
Apparently I spoke too soon, ASSP cleared out the folder after starting fully
All the best,
Colin Waring
On 11 Apr 2014 07:50, Colin Waring co...@lanternhosting.co.uk wrote:
Hi Thomas,
I didn't have to wait long, it turns out two runs of rebuildspamdb are
enough to fill a 1GB tempdb
Has anything changed recently that would increase the tmpDB requirements?
Thins could happen - it depends on the config and the count of files and
words in the corpus.
How ever 1GB for tmpDB is also too less for my system.
There are some improvements for BDB cache calculation in the latest
I'm running ASSP 2.4.1 (14097), and once a week I find my assp crashed due to
too many files open. I have the system limit set to 30 files. At the tail
of the assp log I see the following errors:
rker_2] Error: Worker_2 accept to client failed
IO::Socket::INET=GLOB(0x7f762ec3d060)
I'm running ASSP version 2.4.1(14097)? and have DB: set for all files/caches.
I see the assp database is created, as well as other tables.
However, while ASSP is running I still see new message files being created in
the spam folder. Why? ASSP has been restarted many times and I startup I
The problem: I have some customers at a law firm. Their messages invariably
would evaluate as Spam; but
usually all is well because they submit authenticated, and their recipients are
whitelisted before they reply, but
Occasionally there is a breakdown in an ongoing conversation where a
