Troubleshoot
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
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:
Ensure your WSL version is greater than 2. Check with:
wsl --status
If the version is lower than 2, update it with:
wsl --set-default-version 2
Launch Ubuntu environment within WSL and gain root access:
sudo su -
Edit the WSL configuration file:
sudo nano /etc/wsl.conf
Add the following lines:
[boot] systemd=true
Save and exit (Ctrl+O and Ctrl+X), then proceed with the install.
Issue:
TrustEdge agent cannot connect to Device Trust Manager.
Solution:
Verify that the device can reach the required DigiCert URLs:
one.digicert.com*.one.digicert.com
Ensure that outbound connections on TCP ports 8883 and 1883 are not blocked by your network firewall.
Issue:
TrustEdge agent fails to start due to configuration file errors.
Solution:
Check the syntax and structure of your
trustedge.jsonandbootstrap_config.jsonfiles.Validate JSON files to ensure they are correctly formatted.
Verify file paths and credentials specified in the configuration files.
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.
Check service status
Verify the status of the TrustEdge agent service:
sudo systemctl is-active trustedge
View logs
Important
The file trustedge.log is only created when TrustEdge is running in service mode.
Access TrustEdge logs for detailed error messages:
tail /var/log/trustedge.log
Test connectivity
Test network connectivity to required endpoints:
ping one.digicert.com curl -I https://one.digicert.com