Update CVE cronscript sometimes fails to retrieve CVE database
Bug #135623 reported by
Diogo Matsubara
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Undecided
|
Tom Haddon | ||
Bug Description
Every once in a while the cronscript scheduled to update our CVE entries fails to retrieve the CVE database.
The error looks like:
06:26:50 ERROR Unable to connect for CVE database
http://
This seems like a transient network failure, which causes our script monitoring system to report those errors to the internal mailing list .
SteveA suggested the following approach:
- schedule the script to run twice a day
or
- check that the script has run successfully once every two days
Revision history for this message
| Tom Haddon (mthaddon) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → mthaddon |
| status: | New → Fix Released |
To post a comment you must log in.
I've changed forster to check for this every 2 days.