Page 1 of 1
continue not asking DCC Errors
Posted: 11 Apr 2017 13:34
by sharktech
afternoon
can anyone help with the error "continue not asking DCC", server got hammered earlier and since that i keep getting that error.
Its urgent if someone can help
Thanks
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 13:41
by shawniverson
Did you hit the DCC Clearinghouse free limit threshold (100,000 queries)?
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 13:41
by sharktech
Hi Shawn
Sorry not sure how to check
Thanks
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 13:56
by shawniverson
Let's assume its not that for a moment.
Try running this command to reset the map (I think).
Code: Select all
sudo /usr/local/bin/cdcc “load map.txt”
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:00
by sharktech
Hi Shaun
Details Below
Code: Select all
# 04/11/17 14:59:47 BST /var/dcc/map
# Re-resolve names after 16:59:43
# 12 total, 0 working servers
# continue not asking DCC server 30 seconds after 1 failures
IPv6 on version=3
dcc1.dcc-servers.net,- RTT+1000 ms anon
# 74.92.232.243,-
# not answering
# 137.208.8.63,-
# not answering
# 209.169.14.29,-
# not answering
dcc2.dcc-servers.net,- RTT+1000 ms anon
# 67.66.138.141,-
# not answering
# 192.84.137.21,-
# not answering
# 194.119.212.6,-
# not answering
dcc3.dcc-servers.net,- RTT+1000 ms anon
# 209.169.14.27,-
# not answering
# 212.223.102.90,-
# not answering
dcc4.dcc-servers.net,- RTT+1000 ms anon
# 69.12.221.230,-
# not answering
dcc5.dcc-servers.net,- RTT+1000 ms anon
# 136.199.199.160,-
# not answering
# 212.223.15.198,-
# not answering
@,- RTT-1000 ms 32768 secret14216735570y1242
# *127.0.0.1,-
# not answering
################
# 04/11/17 14:59:47 BST greylist /var/dcc/map
# Re-resolve names after 16:59:47
# 1 total, 0 working servers
# continue not asking greylist server 32 seconds after 1 failures
@,- Greylist 32768 secret14216735570y1242
# *127.0.0.1,6276
# not answering
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:02
by sharktech
Wondering if it was the hit i got this morning that has caused it.
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:09
by shawniverson
Yeah, this looks like you been cut off (hopefully temporarily) from querying DCC, most likely from the volume.
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:16
by sharktech
looking at the output, it says
Do you think this is the reactivate time for me to be able to? i've had to blacklist the old customer lol for the time being.
On Another note the Dcc log folder had 30k in files, is there a cleanup job for this folder?
Thanks
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:16
by sharktech
Cheers for the quick replies by the way
, much appreciated
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 14:27
by shawniverson
Maybe, I think that will be when the list is refreshed.
Hmm...doesn't appear to be a cleanup for that folder......maybe need to do something there...
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 15:54
by sharktech
Hi Had 30k in files, took ages to list the directory lol
Re: continue not asking DCC Errors
Posted: 11 Apr 2017 15:54
by sharktech
How can i disable dcc for now and maybe activate it tomorrow?
Re: continue not asking DCC Errors
Posted: 12 Apr 2017 14:21
by shawniverson
Sorry, missed this post. You can simply shut down the dcc process (sudo service adcc stop).
Re: continue not asking DCC Errors
Posted: 12 Apr 2017 20:56
by henk
Could be wrong, but Housekeeping on dcc should be done by /etc/cron.daily/cron-dccd
Code: Select all
[root@sansspam cron.daily]# ls -l
total 56
lrwxrwxrwx. 1 root root 26 May 25 2015 cron-dccd -> /var/dcc/libexec/cron-dccd
Where in /var/dcc/dcc_conf
Code: Select all
# days to keep files in DCC log directories
DBCLEAN_LOGDAYS=1
Since EFA is still on Centos6, You can use tmpwatch also to do some housekeeping.
By default, tmpwatch dates files by their atime (access time)
the /var/spool/MailScanner/incoming/SpamAssassin-Temp is perfect candidate for tmpwatch
just add in /etc/cron.daily/tmpwatch at the end:
Code: Select all
# ----- User defined cleanup-jobs -----
# MailScanner_incoming
/usr/sbin/tmpwatch -u 48 /var/spool/MailScanner/incoming/SpamAssassin-Temp
Re: continue not asking DCC Errors
Posted: 12 Apr 2017 21:06
by Zwabber
Sure its not a firewall issue?
See also post;
viewtopic.php?t=981