On Tue, 14 Oct 2014, shmick_at_riseup.net wrote:
> opendkim-rephistory: connected to database
> opendkim-rephistory: recording current reputation data for all domains
> opendkim-rephistory: INSERT/SELECT failed: Unknown column 'msglimit' in 'field list'
Did you execute reputation/mkdb-rep.mysql first? It augments the basic
schema with fields needed for reputation work. It would add this field
for you.
> opendkim-genrates: started at Wed Oct 8 00:01:14 2014
> opendkim-genrates: using standard score 1.15
> opendkim-genrates: connected to database
> opendkim-genrates: report started in ge$.6927
> opendkim-genrates: computing low-time threshold
> opendkim-genrates: unable to determine low-time threshold
There was other traffic about this problem on the list recently. The
problem has to do with the fact that your database doesn't contain enough
reports of spam. The "low-time threshold" is a prediction about how long
spammy domains tend to exist before being abandoned, and it feeds into the
rest of the spam estimates for your system. Without enough spam data, it
can't compute this limit.
> what is the recommended ordering of script execution ?
> above ok ?
Yes.
> segfault after every service restart [not start]
>
> opendkim[4085]: segfault at 38 ip 00007f9ee456f274 sp 00007f9eddd51c00
> error 4 in libpthread-2.19.so[7f9ee4565000+18000]
Unfortunately I have no idea how to make use of those syslog entries. I'd
need to see a stack trace from gdb or something equivalent to be able to
debug what's going on here.
-MSK
Received on Fri Oct 31 2014 - 06:45:04 PST
This archive was generated by hypermail 2.3.0
: Fri Oct 31 2014 - 06:54:00 PST