As much as I hate to disable selinux, I did that earlier in the thread.
Surprisingly it is not the culprit, even after a restorecon -r.
Newer info has static as the proper systemd call for clamd. I've found that in
using your .service my whole cloud instance would HANG a few seconds later, and
Am 09.11.2017 um 00:13 schrieb Colony.three:
Yes my first posts were not close to the problem, as there was an evolution in
my thinking through the thread. It was only in the last couple posts that I'd
narrowed down the cause.
Well that's a pretty impressive setup. I've gone through line-b
Yes my first posts were not close to the problem, as there was an evolution in
my thinking through the thread. It was only in the last couple posts that I'd
narrowed down the cause.
Well that's a pretty impressive setup. I've gone through line-by-like and made
my system very similar. Now I a
The last three updates did not have the error. Below is the last error I got:
--
ClamAV update process started at Wed Nov 08 13:13:12 2017
WARNING: DNS record is older than 3 hours.
WARNING: Invalid DNS reply. Falling back to HTTP mode.
securiteinfo.hdb is up to
It's working now. The last error in the log was about 30 minutes
after the report below.
Thanks.
Location is US central time zone with local DNS resolver FWIW.
-- Noel Jones
On 11/8/2017 1:47 PM, David Raynor wrote:
> The DNS records are being updated at the source properly now. If you ar
The DNS records are being updated at the source properly now. If you are
still seeing an error, then the proper record is not reaching the server
you are contacting for DNS or not propagating correctly to your area or
something like that.
If you are still seeing those errors, let us know what the
I'm still getting these errors too. :\
-- Noel Jones
On 11/8/2017 9:50 AM, Joel Esler (jesler) wrote:
> The team working on these issues is seeing these emails, so it’s good that
> you are writing in, if you are still experiencing issues.
>
__
The team working on these issues is seeing these emails, so it’s good that you
are writing in, if you are still experiencing issues.
Sent from my iPad
On Nov 8, 2017, at 9:05 AM, Simon Mousey Smith
mailto:simonsmith5...@gmail.com>> wrote:
Maybe not every day but every week maybe?
Has the issu
Maybe not every day but every week maybe?
Has the issue been resolved yet?
Simon
> On 8 Nov 2017, at 14:02, Reindl Harald wrote:
>
>
>
> Am 08.11.2017 um 14:43 schrieb Jeff:
>> Since October 31st, I get the following DNS warnings every time freshclam
>> runs:
>> ...
>> ClamAV update process
Am 08.11.2017 um 14:43 schrieb Jeff:
Since October 31st, I get the following DNS warnings every time freshclam
runs:
...
ClamAV update process started at Tue Nov 07 09:26:33 2017
+++WARNING: DNS record is older than 3 hours.+++
+++WARNING: Invalid DNS reply. Falling back to HTTP mode.+++
do
Since October 31st, I get the following DNS warnings every time freshclam
runs:
...
ClamAV update process started at Tue Nov 07 09:26:33 2017
+++WARNING: DNS record is older than 3 hours.+++
+++WARNING: Invalid DNS reply. Falling back to HTTP mode.+++
securiteinfo.hdb is up to date (version: custo
On 11/07/17 19:37, Emanuel wrote:
> I use exim with clamav.
>
> Everything is working fine and mails with attachment get scanned,and if
> malware is found, these are rejected. BUT I have lots of
>
> malware acl condition: error while creating mbox spool file
>
> eximscan 100M 100M
12 matches
Mail list logo
