Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVD Mirror Notifications Not Working Correctly #1429

Closed
officerNordberg opened this issue Mar 2, 2022 · 2 comments
Closed

NVD Mirror Notifications Not Working Correctly #1429

officerNordberg opened this issue Mar 2, 2022 · 2 comments
Labels
defect Something isn't working
Milestone

Comments

@officerNordberg
Copy link
Contributor

officerNordberg commented Mar 2, 2022

Current Behavior:

Informational System Notifications being sent even if the level is set to WARNING. For 2 weeks I received


Level: INFORMATIONAL
Scope: SYSTEM
Group: DATASOURCE_MIRRORING


Mirroring of the National Vulnerability Database completed successfully

Also No System Notification was sent when mirroring failed the last 2 days.

Steps to Reproduce:

Setup system notifications with WARNING scope. I tried both Slack and Email destinations.

Expected Behavior:

On the days when mirroring completes successfully I expect no notification.
I expect a notification when things do go wrong.

Environment:

  • Dependency-Track Version: 4.3.3
  • Distribution: Docker
  • BOM Format & Version: N/A
  • Database Server: PostgreSQL
  • Browser:

Additional Details:

The reason there is no error message is the NVD Mirroring task just hung on the download and ended up corrupting the gzip which impacted other processes that utilize the mirror, this should have a timeout
2022-02-28 19:14:36,298 [] INFO [org.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-2010.json.gz 2022-02-28 19:14:36,441 [] INFO [org.dependencytrack.tasks.NistMirrorTask] Downloading...

@nscuro nscuro added defect Something isn't working and removed in triage labels Jun 22, 2022
@nscuro nscuro added this to the 4.6 milestone Jun 22, 2022
@nscuro
Copy link
Member

nscuro commented Jun 22, 2022

Addressed with #1742

@github-actions
Copy link
Contributor

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
defect Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants