Masood,
warning: got unexpected signal SEGV.
These error are most related to the regex engine of Perl. Maybe the reason
is a very high (100%) CPU workload over some time.
Worker_2: Can't call method
fetchrow_arrayref on an undefined value at
The MySQL server was not able to do a
I tried this (although I changed delete to del to make sure it
functioned correctly).
It died three times overnight and duly restarted itself - but did not
log anything to asspdbg.log. It is a zero-byte file. assprst.log held
exactly what you expect:
Thu 03/18/2010 0:54:04.13
Thu 03/18/2010
The headers don¹t say that the score was less than the lower limit and show
no scoring other than than the bayesian, which meets the lower limit. The
sender wasn¹t whitelisted.
Any ideas why it wasn¹t tagged and was marked as ok mail? I¹m running
1.7.1.2 10
Mar-18-10 07:58:06
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
The headers dont say that the score was less than the lower limit
and show
no scoring other than than the bayesian, which meets the lower limit.
The
sender wasnt whitelisted.
The GUI says:
MessageScoring will tag messages
Fritz I will try to get the information for you on other v1 versions that I
have installed.
Thomas I have offloaded the DNS and MYSQL to separate servers now. This
server is only running ASSP. I have reduced it down to the default 5
threads. The external dns server I am using on my local
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
Fritz I will try to get the information for you on other v1 versions
that I
have installed.
No hurry about that. ASSP V1 is running robust and stable in several
thousand installations. As I said before, for me it is not
I'm going to try this again, but I'm going to get rid of the start
/wait, so that the perl process outputs its entire console output (as
well as redirecting the STDERR output) into the debug file instead of
opening in a second window, and see if there is something to see that way.
At 07:50 AM
AHA. This one did the trick. I logged several hours of resets, and
the same thing shows each time:
Mar-18-10 16:01:15 [Main_Thread] Info: Main_Thread got connection request
Out of memory!
Callback called exit at assp.pl line 17570.
Now this is interesting...because the server has lots ( 2GB
I noticed that the dbl.spamhaus.org had been added to the default for the
URIBL. So I decided to update it back to default and give that new one a
try. When I did that I started sending some test messages through from my
gmail account with a list of domains in the message and I turned the
Doing some research into this Out of memory! error from Perl, it
apparently only happens when a malloc() call within Perl fails,
because memory it wants is not available.
That said, my ASSP normally trundles along with about 2 GB of
physical memory available, and about the same amount of
I've now got 7 examples logged of this problem occurring, and every
time, it's line 17570 that is causing the out of memory error. This line is:
while (time - $itime = $maxBombSearchTime $text =~ s/($regex)//) {
At 10:09 PM 3/18/2010, Scott MacLean wrote:
Doing some research into this
I added this line just before line 17570 that was causing the exception:
mlog (0,%%%DEBUG: itime= $itime maxBombSearchTime =
$maxBombSearchTime text = $text regex = $regex);
I then let it run for a bit, until it crashed again with an out of
memory error. The result, extracted from
12 matches
Mail list logo
