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
Hi all, great project and I'm trying to make it more resilient for my team by caching the NVD data instead of downloading it each time it runs.
With the intent to kick-start mirroring to into my container, I ran this, some time ago...
% docker exec -u mirror vulnz /mirror.sh
the most I'm getting back is:
NVD API request failures are occurring; retrying request for the 7th time
I don't see any data landing in /usr/local/apache2/htdocs. From the looks of it, that's the intended location.
is this due to current issues with the NVD site?
The text was updated successfully, but these errors were encountered:
You simply have to wait a few hours and - if remote servers aren't overloaded, as they usually are - it'll work. I did it last night.
I suppose the partial downloaded data gets written to a temporary directory and only when the data is complete it gets written to the output directory.
that was going to be my next question... could the persistence of those downloaded records in htdocs be shared out to a docker volume... that's the next feature on the way? Awesome if so @jeremylong
Hi all, great project and I'm trying to make it more resilient for my team by caching the NVD data instead of downloading it each time it runs.
With the intent to kick-start mirroring to into my container, I ran this, some time ago...
% docker exec -u mirror vulnz /mirror.sh
the most I'm getting back is:
NVD API request failures are occurring; retrying request for the 7th time
I don't see any data landing in /usr/local/apache2/htdocs. From the looks of it, that's the intended location.
is this due to current issues with the NVD site?
The text was updated successfully, but these errors were encountered: