Lineaje Learning Center
  • About Lineaje
  • Lineaje Product Offering
  • Getting started
    • Create an account
      • Configure Azure AD for sso
      • Configure Okta for sso
    • Onboarding workflow
  • SBOM360, OSM
    • Generate an SBOM
      • Source Code Management (SCM) As Source
        • Public Code Repositories
        • Private Code Repositories
          • Configure GitHub credentials
          • Configure Bitbucket credentials
          • Configure Gitlab credentials
          • Configure Git credentials
          • Configure Azure Repo
        • Frequently Asked Questions
      • Container Image As Source
        • Public Container Image
        • Private Container Image
          • Configure AWS Elastic Container Registry
          • Configure Google Container Registry
          • Configure Docker Hub
          • Configure Generic OCI Registry
          • Configure Azure Container Registry
        • Frequently Asked Questions
      • Existing SBOM As Source
        • EO 14028 checks
      • Manifest file As Source
      • Android Package Kit (APK)
      • Using Lineaje CLI
    • Explore Your SBOM
      • Info
      • Attestation
      • IRL
      • Dependencies
      • Provenance
      • Vulnerabilities
      • Mitigations
      • Security Posture
      • Code Quality
      • Suppliers & Licenses
      • Findings
    • Manage Your SBOM
    • Dashboard
    • Search
    • Policies and Gates
    • Organization and User Management
      • Organization example
    • Lineaje AI
    • AI Plan and AI Remediate
      • JIRA Integration
  • SBOM360 Hub
    • My Products
    • My SBOMS
    • Find & Review SBOMs
    • Manage Your Repository
    • Request and Share SBOMS
    • Settings
    • User Roles
  • Lineaje CLI
    • System Configuration
    • Toolset Configuration
    • CLI Installation
    • CLI Usage
    • Troubleshooting CLI issues
    • Support matrix
  • Integration with CICD pipeline
    • Pre-Requisites
    • Generate Project from source code
      • Project creation using Lineaje cloud
  • Abbreviations and Descriptions
  • Release Notes
    • Unified Scanner for AWS
Powered by GitBook
On this page
  • Troubleshooting
  • Data required for troubleshooting
  1. Lineaje CLI

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.

PreviousCLI UsageNextSupport matrix

Last updated 1 year ago