> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/sca360-secure-deployment-for-restricted-environments/troubleshooting-cli-issues.md).

# Troubleshooting CLI issues

### Troubleshooting

1. Q: CLI fails to execute A: Ensure to run “pre.sh” after CLI is extracted and rerun the command
2. 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.
3. 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”
4. 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.
5. 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” 

### Data required for troubleshooting 

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

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/sca360-secure-deployment-for-restricted-environments/troubleshooting-cli-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.