Troubleshooting CLI issues

Q: CLI fails to execute A: Ensure to run “pre.sh” after CLI is extracted and rerun the command
Q: /tmp or /home does not have sufficient free space to run the CLI A: Before executing the CLI in a bash shell, export the environment variables “TMPDIR” and “HOME” to point to partitions where enough free space is available. The regular user that is running the CLI should have access to write to these directories.
Q: CLI crashes while running A: Collect the core if possible, or share a screenshot or output of the stack trace along with data specified in the section - “Data required for troubleshooting”
Q: SBOM data generated by the CLI is not available in SBOM360 portal A: Ensure to register the CLI using the device registration code before generating the SBOM. Verify the project input data given in “input.json” and that is a valid JSON.
Q: SBOM data generated by the CLI is not correct in SBOM360 portal A: Verify the project input data given in “input.json” and that is a valid JSON. Share the data specified in the section – “Data required for troubleshooting”

Assuming the CLI was executed inside the folder “/home/ubuntu/veecli”,

“/home/ubuntu/veecli/veelocal.log” – Log file created in the current folder where CLI was executed
“/home/ubuntu/veecli/output//-SPDXRef-DOCUMENT-vdna_.tar.gz – Output of the analysis
“/home/ubuntu/veecli/output//collectionsummary.json – Summary of the analysis
“/home/ubuntu/veecli/input.json” – Input JSON used for SBOM creation
Output file where the CLI execution stdout and stderr was redirected to.

Last updated 11 months ago