On 01/10/2018 01:25 PM, Jens Schleusener wrote:
On Wed, 10 Jan 2018, Dave Jones wrote:
On 01/10/2018 08:48 AM, Kevin A. McGrail wrote:
Can you turn on debugging and perhaps add it to retry again? I am
trying to figure out if it is one server with an issue.
We have added a number of new
On 01/10/2018 10:03 AM, Dave Jones wrote:
On 01/10/2018 08:48 AM, Kevin A. McGrail wrote:
Can you turn on debugging and perhaps add it to retry again? I am
trying to figure out if it is one server with an issue.
We have added a number of new sa-update mirrors recently. Check the
On Wed, 10 Jan 2018, Dave Jones wrote:
On 01/10/2018 08:48 AM, Kevin A. McGrail wrote:
Can you turn on debugging and perhaps add it to retry again? I am trying
to figure out if it is one server with an issue.
We have added a number of new sa-update mirrors recently. Check the
On 01/10/2018 08:48 AM, Kevin A. McGrail wrote:
Can you turn on debugging and perhaps add it to retry again? I am
trying to figure out if it is one server with an issue.
We have added a number of new sa-update mirrors recently. Check the
MIRRORED.BY file and do ping/traceroutes AND
Can you turn on debugging and perhaps add it to retry again? I am
trying to figure out if it is one server with an issue.
On 1/10/2018 9:25 AM, Dale Blount wrote:
I get them randomly starting a few months back. My cronjob is set for
4:40am Eastern. Normally it won't fail two days in a
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1
+ mv
