I've been experiencing the same thing throughout the day (from aws
us-east-1), seems to be intermittent, at least for me. My HIDS has been
going crazy :) Looks OK right now, only a couple failures
$> host db.us.clamav.net | awk '/address/ { print $NF }' | xargs -L1 ping
-c 1
PING 155.98.64.87 (155.98.64.87) 56(84) bytes of data.
--- 155.98.64.87 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 168.143.19.95 (168.143.19.95) 56(84) bytes of data.
--- 168.143.19.95 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 194.8.197.22 (194.8.197.22) 56(84) bytes of data.
64 bytes from 194.8.197.22: icmp_seq=1 ttl=43 time=99.9 ms
--- 194.8.197.22 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 99.923/99.923/99.923/0.000 ms
PING 194.186.47.19 (194.186.47.19) 56(84) bytes of data.
--- 194.186.47.19 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 198.148.78.4 (198.148.78.4) 56(84) bytes of data.
64 bytes from 198.148.78.4: icmp_seq=1 ttl=49 time=2.67 ms
--- 198.148.78.4 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.675/2.675/2.675/0.000 ms
PING 200.236.31.1 (200.236.31.1) 56(84) bytes of data.
64 bytes from 200.236.31.1: icmp_seq=1 ttl=41 time=255 ms
--- 200.236.31.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 255.204/255.204/255.204/0.000 ms
PING 204.130.133.50 (204.130.133.50) 56(84) bytes of data.
64 bytes from 204.130.133.50: icmp_seq=1 ttl=42 time=23.3 ms
--- 204.130.133.50 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 23.337/23.337/23.337/0.000 ms
PING 207.57.106.31 (207.57.106.31) 56(84) bytes of data.
--- 207.57.106.31 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 208.72.56.53 (208.72.56.53) 56(84) bytes of data.
--- 208.72.56.53 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 64.6.100.177 (64.6.100.177) 56(84) bytes of data.
--- 64.6.100.177 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 64.22.33.90 (64.22.33.90) 56(84) bytes of data.
--- 64.22.33.90 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 69.12.162.28 (69.12.162.28) 56(84) bytes of data.
64 bytes from 69.12.162.28: icmp_seq=1 ttl=41 time=85.1 ms
--- 69.12.162.28 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 85.174/85.174/85.174/0.000 ms
PING 69.163.100.14 (69.163.100.14) 56(84) bytes of data.
64 bytes from 69.163.100.14: icmp_seq=1 ttl=40 time=86.3 ms
--- 69.163.100.14 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 86.349/86.349/86.349/0.000 ms
PING 104.131.196.175 (104.131.196.175) 56(84) bytes of data.
64 bytes from 104.131.196.175: icmp_seq=1 ttl=45 time=8.63 ms
--- 104.131.196.175 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 8.633/8.633/8.633/0.000 ms
PING 128.199.133.36 (128.199.133.36) 56(84) bytes of data.
64 bytes from 128.199.133.36: icmp_seq=1 ttl=37 time=235 ms
--- 128.199.133.36 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 235.303/235.303/235.303/0.000 ms
PING 150.214.142.197 (150.214.142.197) 56(84) bytes of data.
64 bytes from 150.214.142.197: icmp_seq=1 ttl=42 time=141 ms
--- 150.214.142.197 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 141.670/141.670/141.670/0.000 ms
On Wed, Aug 23, 2017 at 1:36 PM, Simon Mousey Smith <
simonsmith5...@gmail.com> wrote:
> Same here from UK Liverpool datacenter
>
> Was able to download a few hours ago but then stopped again
>
> Simon
>
> Sent from my iPhone
>
> > On 23 Aug 2017, at 18:33, Maarten Broekman <maarten.broek...@gmail.com>
> wrote:
> >
> > Similar issues with addresses for db.us.clamav.net. 7 of 16 mirrors
> aren't
> > reachable.
> >
> > $ host db.us.clamav.net
> > db.us.clamav.net is an alias for db.us.big.clamav.net.
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 208.72.56.53*
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 64.6.100.177*
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> 64.22.33.90*
> > db.us.big.clamav.net has address 69.12.162.28
> > db.us.big.clamav.net has address 69.163.100.14
> > db.us.big.clamav.net has address 104.131.196.175
> > db.us.big.clamav.net has address 128.199.133.36
> > db.us.big.clamav.net has address 150.214.142.197
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 155.98.64.87*
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 168.143.19.95*
> > db.us.big.clamav.net has address 194.8.197.22
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 194.186.47.19*
> > db.us.big.clamav.net has address 198.148.78.4
> > db.us.big.clamav.net has address 200.236.31.1
> > db.us.big.clamav.net has address 204.130.133.50
> > *db.us.big.clamav.net <http://db.us.big.clamav.net> has address
> > 207.57.106.31*
> >
> > $ host db.us.clamav.net | awk '/address/ { print $NF }' | xargs -L1
> ping -c
> > 1
> >
> > *--- 208.72.56.53 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > *--- 64.6.100.177 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > *--- 64.22.33.90 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > --- 69.12.162.28 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 69.163.100.14 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 104.131.196.175 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 128.199.133.36 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 150.214.142.197 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > *--- 155.98.64.87 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > *--- 168.143.19.95 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > --- 194.8.197.22 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > *--- 194.186.47.19 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> > --- 198.148.78.4 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 200.236.31.1 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > --- 204.130.133.50 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >
> > *--- 207.57.106.31 ping statistics ---*
> > *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >
> >
> > On Wed, Aug 23, 2017 at 1:26 PM, Maarten Broekman <
> > maarten.broek...@gmail.com> wrote:
> >
> >> For me, 3 of the 5 db.local.clamav.net addresses have 100% packet loss:
> >>
> >> $ host db.local.clamav.net
> >> db.local.clamav.net is an alias for db.us.rr.clamav.net.
> >> db.us.rr.clamav.net has address 200.236.31.1
> >> db.us.rr.clamav.net has address 208.72.56.53
> >> db.us.rr.clamav.net has address 69.12.162.28
> >> db.us.rr.clamav.net has address 150.214.142.197
> >> db.us.rr.clamav.net has address 194.186.47.19
> >>
> >> $ host db.local.clamav.net | awk '/address/ { print $NF }' | xargs -L1
> >> ping -c 1
> >> --- 200.236.31.1 ping statistics ---
> >> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >>
> >> *--- 208.72.56.53 ping statistics ---*
> >> *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >>
> >> --- 69.12.162.28 ping statistics ---
> >> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> >>
> >> *--- 150.214.142.197 ping statistics ---*
> >> *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >>
> >> *--- 194.186.47.19 ping statistics ---*
> >> *1 packets transmitted, 0 received, 100% packet loss, time 0ms*
> >>
> >>
> >>
> >>
> >> On Wed, Aug 23, 2017 at 12:48 PM, Dennis Peterson <denni...@inetnw.com>
> >> wrote:
> >>
> >>> nslookup db.local.clamav.net |awk '/Address:/ {print $2}' |xargs -L1
> >>> ping -c 1
> >>>
> >>> nslookup db.us.clamav.net |awk '/Address:/ {print $2}' |xargs -L1 ping
> >>> -c 1
> >>>
> >>> nslookup db.ca.clamav.net |awk '/Address:/ {print $2}' |xargs -L1 ping
> >>> -c 1
> >>>
> >>> nslookup db.ru.clamav.net |awk '/Address:/ {print $2}' |xargs -L1 ping
> >>> -c 1
> >>>
> >>> nslookup db.uk.clamav.net |awk '/Address:/ {print $2}' |xargs -L1 ping
> >>> -c 1
> >>>
> >>>
> >>> Nobody home.
> >>>
> >>> dp
> >>>
> >>>
> >>>> On 8/23/17 12:26 AM, lukn555 wrote:
> >>>>
> >>>> Good Day ClamAV List
> >>>>
> >>>> Since yesterday at around noon CET I've been having issues downloading
> >>>> the ClamAV database:
> >>>>
> >>>> freshclam --version
> >>>> ClamAV 0.99.2/23696/Tue Aug 22 14:36:14 2017
> >>>>
> >>>>
> >>>> # /usr/local/bin/freshclam --verbose
> >>>> Current working dir is /usr/local/share/clamav
> >>>> Max retries == 3
> >>>> ClamAV update process started at Wed Aug 23 09:11:52 2017
> >>>> Using IPv6 aware code
> >>>> Querying current.cvd.clamav.net
> >>>> TTL: 609
> >>>> Software version from DNS: 0.99.2
> >>>> main.cvd version from DNS: 58
> >>>> main.cld is up to date (version: 58, sigs: 4566249, f-level: 60,
> >>>> builder: sigmgr)
> >>>> daily.cvd version from DNS: 23700
> >>>> Retrieving http://database.clamav.net/daily-23697.cdiff
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> WARNING: getpatch: Can't download daily-23697.cdiff from
> >>>> database.clamav.net
> >>>> Retrieving http://database.clamav.net/daily-23697.cdiff
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> WARNING: getpatch: Can't download daily-23697.cdiff from
> >>>> database.clamav.net
> >>>> Retrieving http://database.clamav.net/daily-23697.cdiff
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> WARNING: getpatch: Can't download daily-23697.cdiff from
> >>>> database.clamav.net
> >>>> WARNING: Incremental update failed, trying to download daily.cvd
> >>>> Whitelisting short-term blacklisted mirrors
> >>>> Retrieving http://database.clamav.net/daily.cvd
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> Ignoring mirror 130.59.113.36 (due to previous errors)
> >>>> Ignoring mirror 193.230.240.8 (due to previous errors)
> >>>> WARNING: Can't download daily.cvd from database.clamav.net
> >>>> Trying again in 5 secs...
> >>>>
> >>>>
> >>>> # dig database.clamav.net +short
> >>>> db.local.clamav.net.
> >>>> db.centraleu.clamav.net.
> >>>> 130.59.113.36
> >>>> 193.230.240.8
> >>>>
> >>>>
> >>>> # wget http://database.clamav.net/daily-23697.cdiff
> >>>> --2017-08-23 09:14:16-- http://database.clamav.net/daily-23697.cdiff
> >>>> Resolving database.clamav.net (database.clamav.net)... 193.230.240.8,
> >>>> 130.59.113.36
> >>>> Connecting to database.clamav.net
> >>>> (database.clamav.net)|193.230.240.8|:80... connected.
> >>>> HTTP request sent, awaiting response... 403 Forbidden
> >>>> 2017-08-23 09:14:16 ERROR 403: Forbidden.
> >>>>
> >>>>
> >>>> Is this an issue on my side or on ClamAV mirror side?
> >>>> Any help is appreciated.
> >>>> _______________________________________________
> >>>> clamav-users mailing list
> >>>> clamav-users@lists.clamav.net
> >>>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> >>>>
> >>>>
> >>>> Help us build a comprehensive ClamAV guide:
> >>>> https://github.com/vrtadmin/clamav-faq
> >>>>
> >>>> http://www.clamav.net/contact.html#ml
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> clamav-users mailing list
> >>> clamav-users@lists.clamav.net
> >>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> >>>
> >>>
> >>> Help us build a comprehensive ClamAV guide:
> >>> https://github.com/vrtadmin/clamav-faq
> >>>
> >>> http://www.clamav.net/contact.html#ml
> >>>
> >>
> >>
> > _______________________________________________
> > clamav-users mailing list
> > clamav-users@lists.clamav.net
> > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> >
> >
> > Help us build a comprehensive ClamAV guide:
> > https://github.com/vrtadmin/clamav-faq
> >
> > http://www.clamav.net/contact.html#ml
> _______________________________________________
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
