Troubleshoot

  2 minute read  

When using TrustEdge, you may encounter various issues that can affect its operation. This section provides guidance on diagnosing and resolving common problems to ensure smooth functionality.

Common issues and solutions

Installation errors

Issue:

When installing on Windows using WSL, installation fails with the error message: “System has not been booted with systemd as init system (PID 1). Can’t operate. Failed to connect to bus: Host is down.”

Solution:

  1. Ensure your WSL version is greater than 2. Check with:
    wsl --status
  2. If the version is lower than 2, update it with:
    wsl --set-default-version 2
  3. Launch Ubuntu environment within WSL and gain root access:
    sudo su -
  4. Edit the WSL configuration file:
    sudo nano /etc/wsl.conf
    Add the following lines:
    [boot]
systemd=true
  5. Save and exit (Ctrl+O and Ctrl+X), then proceed with the install.

Connectivity problems

See Network requirements.

Configuration errors

Issue:

TrustEdge agent fails to start due to configuration file errors.

Solution:

  1. Check the syntax and structure of your trustedge.json and bootstrap_config.json files.
  2. Validate JSON files to ensure they are correctly formatted.
  3. Verify file paths and credentials specified in the configuration files.

Certificate issues

Issue:

Problems with certificate generation or CSR submission.

Solution:

Ensure that the keys and certificates are correctly specified in the command line or configuration files.

Troubleshooting commands

Check service status

Verify the status of the TrustEdge agent service:

sudo systemctl is-active trustedge

View logs

To view TrustEdge logs when running as a service:

sudo journalctl -f -u trustedge.service

Test connectivity

Test network connectivity to required endpoints:

ping one.digicert.com
curl -I https://one.digicert.com