Mirror.sh script fails but container has exitcode 0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- devops, infrastructure
Research direction
Start by locating and reading mirror.sh, then run it in the container with a Java failure such as the reported OutOfMemoryError. Check how command failures are handled and verify that mirror problems produce a nonzero container exit status, while successful mirrors still exit with status 0.
Written by the indexing model from the issue text.
Description
I also have the vulnz error now on my local NVD mirror:
Jun 24 15:05:56 v220240133360251736 vulnz[265688]: Caused by: java.lang.OutOfMemoryError: Java heap space
Since the NVD update on 17.06:
https://www.nist.gov/itl/nvd#news-updates
I understand that you have nothing to do with it, but it took me one week to notice the error because the mirror.sh script running inside the Podman container did not report the error back to the container, and it exited with status code 0 (success).
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d44d2b0dd744 ghcr.io/jeremylong/open-vulnerability-data-mirror:latest /mirror.sh 37 minutes ago Exited (0) 36 minutes ago vulnz
Would it be possible to report all mirror.sh problems, including Java errors, back to the container so that I can react to the container exit code?
Or do you have another suggestion for how to handle errors from mirror.sh running inside the container?
- Dominant language
- Java
- Stars
- 176
- Forks
- 53
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jeremylong/open-vulnerability-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
jeremylong/open-vulnerability-cli#432 · 6 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
jeremylong/open-vulnerability-cli#414 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
jeremylong/open-vulnerability-cli#405 · 2 comments · 2 reactions ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in jeremylong/open-vulnerability-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100