You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[INFO] Checking for updates
[WARN] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=0 : 2 time
[WARN] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=0 : 3 time
[WARN] Retrying request /rest/json/cves/2.0?resultsPerPage=2000&startIndex=0 : 4 time
[WARN] NVD API request failures are occurring; retrying request for the 5 time
[WARN] NVD API request failures are occurring; retrying request for the 6 time
Repeatedly and doesn't end.
On the /var/log/messages of the gateway,
If I used the lastest 11.1.1, there will be new errors and it will end,
[WARN] NVD API request failures are occurring; retrying request for the 9 time
[WARN] NVD API request failures are occurring; retrying request for the 10 time
[WARN] NVD API request failures are occurring; retrying request for the 11 time
[ERROR] Error updating the NVD Data
org.owasp.dependencycheck.data.update.exception.UpdateException: Error updating the NVD Data
at org.owasp.dependencycheck.data.update.NvdApiDataSource.processApi(NvdApiDataSource.java:397)
at org.owasp.dependencycheck.data.update.NvdApiDataSource.update(NvdApiDataSource.java:117)
at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:906)
at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:878)
at org.owasp.dependencycheck.App.runUpdateOnly(App.java:431)
at org.owasp.dependencycheck.App.run(App.java:175)
at org.owasp.dependencycheck.App.main(App.java:90)
options {
listen-on port 53 { 127.0.0.1; any; };
listen-on-v6 port 53 { ::1; any; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
secroots-file "/var/named/data/named.secroots";
recursing-file "/var/named/data/named.recursing";
allow-query { localhost; };
/*
- If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
- If you are building a RECURSIVE (caching) DNS server, you need to enable
recursion.
- If your recursive DNS server has a public IP address, you MUST enable access
control to limit queries to your legitimate users. Failing to do so will
cause your server to become part of large scale DNS amplification
attacks. Implementing BCP38 within your network would greatly
reduce such attack surface
*/
recursion yes;
dnssec-validation yes;
managed-keys-directory "/var/named/dynamic";
geoip-directory "/usr/share/GeoIP";
pid-file "/run/named/named.pid";
session-keyfile "/run/named/session.key";
/* https://fedoraproject.org/wiki/Changes/CryptoPolicy */
include "/etc/crypto-policies/back-ends/bind.config";
};
My gateway have two networks (external-192.168.133.0/24 and internal-192.168.99.0/24). I'm running from the client of internal.
The squid log have no errors, so even if I turned off squid, still the same error, meaning the error is only on the bind/dns.
[root@centos9 ~]# tail -f /var/log/squid/
access.log access.log-20241223 cache.log cache.log-20241223
[root@centos9 ~]# tail -f /var/log/squid/access.log
1734991799.552 355 192.168.99.91 TCP_MISS/200 468 POST https://eastus-1.in.applicationinsights.azure.com/v2.1/track - HIER_DIRECT/52.179.73.44 application/json
1734991799.557 360 192.168.99.91 TCP_MISS/200 468 POST https://eastus-1.in.applicationinsights.azure.com/v2.1/track - HIER_DIRECT/52.179.73.44 application/json
1734991802.343 659 192.168.99.91 TCP_MISS/200 468 POST https://westus-0.in.applicationinsights.azure.com/v2.1/track - HIER_DIRECT/20.189.172.33 application/json
1734991802.356 672 192.168.99.91 TCP_MISS/200 468 POST https://westus-0.in.applicationinsights.azure.com/v2.1/track - HIER_DIRECT/20.189.172.33 application/json
1735009581.138 553 192.168.99.91 TCP_MISS/301 449 GET http://salesforce.com/ - HIER_DIRECT/104.109.11.129 -
1735010154.549 71 192.168.99.91 TCP_MISS/301 278 GET http://nist.gov/ - HIER_DIRECT/129.6.13.49 -
1735010167.952 66 192.168.99.91 TCP_MISS/301 278 GET http://nist.gov/ - HIER_DIRECT/129.6.13.49 -
1735011402.145 636 192.168.99.91 TCP_MISS/301 278 GET http://nist.gov/ - HIER_DIRECT/129.6.13.49 -
1735011429.835 79 192.168.99.91 TCP_MISS/301 278 GET http://nist.gov/ - HIER_DIRECT/129.6.13.49 -
1735013077.883 647 192.168.99.91 TCP_TUNNEL/200 3549 CONNECT services.nvd.nist.gov:443 - HIER_DIRECT/18.235.227.114 -
1735014284.781 373 192.168.99.91 TCP_TUNNEL/200 3549 CONNECT services.nvd.nist.gov:443 - HIER_DIRECT/54.85.30.225 -
[root@centos9 ~]# tail -f /var/log/squid/cache.log
2024/12/23 23:22:58 kid1| Max Mem size: 262144 KB
2024/12/23 23:22:58 kid1| Max Swap size: 0 KB
2024/12/23 23:22:58 kid1| Using Least Load store dir selection
2024/12/23 23:22:58 kid1| Set Current Directory to /var/spool/squid
2024/12/23 23:22:58 kid1| Finished loading MIME types and icons.
2024/12/23 23:22:58 kid1| HTCP Disabled.
2024/12/23 23:22:58 kid1| Squid plugin modules loaded: 0
2024/12/23 23:22:58 kid1| Adaptation support is off.
2024/12/23 23:22:58 kid1| Accepting HTTP Socket connections at conn3 local=[::]:3129 remote=[::] FD 11 flags=9
2024/12/23 23:22:59 kid1| storeLateRelease: released 0 objects
It didn't help putting the proxy as parameter, when I run it inside the docker,
Running with no proxy is fine but running it against Squid proxy,
Will have this errors,
Repeatedly and doesn't end.
On the /var/log/messages of the gateway,
I have no problem on other tasks like wget download or curl nist.gov.
If I used the lastest 11.1.1, there will be new errors and it will end,
Here are the env of my proxy,
My /etc/named.conf,
My squid,
My gateway have two networks (external-192.168.133.0/24 and internal-192.168.99.0/24). I'm running from the client of internal.
The squid log have no errors, so even if I turned off squid, still the same error, meaning the error is only on the bind/dns.
It didn't help putting the proxy as parameter, when I run it inside the docker,
Got this logs,
Please help me!
The text was updated successfully, but these errors were encountered: