Open eroussy opened 1 year ago
Hi, @eroussy, thank you for raising these issues. We are reworking the code to eliminate the pid problem and will include changes to improve field validation. We're planning to release these fixes in our next update, which is currently under development.
For the pid issue - this workaround can be applied when the sbom_process.pid error appears:
1. cd /var/www/sbomscripts/
2. rm sbom_process.pid
3. Resubmit the upload
For the field validation issue there are a few workarounds:
1. cd /var/www/DaggerBoard
2. Edit /var/www/DaggerBoard/daggerboard/models.py and adjust the max_length for the desired field
3. (if using venv) source /venv/bin/activate
4. python manage.py makemigrations
5. python manage.py migrate
6. systemctl restart apache2
Daggerboard installation method : docker
Description
I uploaded the SPDX-DAGGERBOARD-1-0-SBOM-20-5-2022-23-40.spdx provided in this repository on daggerboard. The SBOM is correctly analyzed, but after that, no other sbom will be analyzed. New uploaded files stay in the "started" state and are never analyzed.
Exact steps to reproduce :
Analysis
Here is the content of the
sbom.log
in the docker container :I tried to reset the container and removing dagger-vol volume. I then uploaded SPDX-DAGGERBOARD-1-0-SBOM-20-5-2022-23-40.spdx again and launched the analysis manually :
It seems that the line 452 of SPDX-DAGGERBOARD-1-0-SBOM-20-5-2022-23-40.spdx contains a too long package supplier : "Organization: Andy Robinson, Robin Becker, the ReportLab team and the community".
Then, because sbom_process.py has failed, it does not remove the file /var/www/sbomscripts/sbom_process.pid. And this file blocks every other SBOM analysis.