ASN lookup failing with empty files [solved]
-
Same here too ... I guess it has something to do with the api.bgpview.io ...
Maybe BBcan177 can clarify ... -
@fireodo It's back.
Apparently a transient error.
Perhaps a better d/l failure error for the logs is called for, or a backup ASN lookup API on another site for failover?
Today's pull:
Alias table IP Counts ----------------------------- 24420 total 16967 /var/db/aliastables/pfB_PRI1_v4.txt 3918 /var/db/aliastables/pfB_ASN_List_v6.txt 3455 /var/db/aliastables/pfB_ASN_List_v4.txt 51 /var/db/aliastables/pfB_PRI1_6_v6.txt 26 /var/db/aliastables/pfB_MyBlockedDomains_v4.txt 3 /var/db/aliastables/pfB_SCANNERS_v4.txtYesterday's incorrect pull:
Alias table IP Counts ----------------------------- 17055 total 16951 /var/db/aliastables/pfB_PRI1_v4.txt 51 /var/db/aliastables/pfB_PRI1_6_v6.txt 26 /var/db/aliastables/pfB_MyBlockedDomains_v4.txt 17 /var/db/aliastables/pfB_ASN_List_v4.txt 7 /var/db/aliastables/pfB_ASN_List_v6.txt 3 /var/db/aliastables/pfB_SCANNERS_v4.txtThe reason the ASN_List_v4 and v6 have some addresses is that they're the manually custom entered addresses at the end of the config entry.
-
@lohphat said in ASN lookup failing with empty files:
It's back.
Not here :-(
I see you have pfblockerNG-devel 3.1.0_7 i have 3.1.0_6 ... i dont know if there is any difference concerning the arised issue ...
-
@fireodo said in ASN lookup failing with empty files:
Not here :-(
Maybe the API server is unstable or overloaded and silently rejecting connections.
-
@lohphat said in ASN lookup failing with empty files:
@fireodo said in ASN lookup failing with empty files:
Not here :-(
Maybe the API server is unstable or overloaded and silently rejecting connections.
Would you mind to test this ASN: AS47890 ?
-
@fireodo said in ASN lookup failing with empty files:
Would you mind to test this ASN: AS47890
IPv4:
2.57.120.0/23 2.57.122.0/24 45.8.44.0/24 45.13.37.0/24 45.13.212.0/24 45.129.15.0/24 80.94.92.0/23 92.118.39.0/24 185.232.64.0/24 185.232.66.0/24 193.29.14.0/24 193.32.163.0/24 193.46.254.0/23 193.47.69.0/24IPv6:
2a0c:9f00::/48 2a0e:1d80:7::/48 2a10:9100:6::/48 2a10:9100:a::/48 -
@lohphat said in ASN lookup failing with empty files:
@fireodo said in ASN lookup failing with empty files:
Would you mind to test this ASN: AS47890
IPv4:
2.57.120.0/23 2.57.122.0/24 45.8.44.0/24 45.13.37.0/24 45.13.212.0/24 45.129.15.0/24 80.94.92.0/23 92.118.39.0/24 185.232.64.0/24 185.232.66.0/24 193.29.14.0/24 193.32.163.0/24 193.46.254.0/23 193.47.69.0/24IPv6:
2a0c:9f00::/48 2a0e:1d80:7::/48 2a10:9100:6::/48 2a10:9100:a::/48Thanks - thats correct ... I get only empty file here ...
-
@fireodo said in ASN lookup failing with empty files:
Thanks - thats correct ... I get only empty file here ...
Yeah...methinks it's that the API server is overloaded perhaps.
-
@lohphat said in ASN lookup failing with empty files:
Yeah...methinks it's that the API server is overloaded perhaps.
Could be ... this persists now for allmost 24 hours ... maybe I should be pacient :-D (not exactly my strength)
EDIT: Its back here too - this morning everything was as it should be!
@lohphat maybe you can edit the topic as resolved. -
@fireodo said in ASN lookup failing with empty files:
@lohphat maybe you can edit the topic as resolved.
I think only admins can change topic text, unless I just can't find where to edit it.
I still think that the failure mode could be better handled and alerted -- the logs indicated empty files, but was it due to d/l failure or the server returned an empty file? Something should throw an alert if possible.
-
@lohphat said in ASN lookup failing with empty files [solved]:
I still think that the failure mode could be better handled and alerted -- the logs indicated empty files, but was it due to d/l failure or the server returned an empty file? Something should throw an alert if possible.
Ofcourse that could be a good Idea!
