Troubleshooting#

This page goes through some common issues and their solutions when using OctaiPipe.

Devices not Spinning Up#

Problem

After registering a device and running the docker compose, it does not appear as “Available” in the portal interface.

Solution

Make sure to check the following:

  1. Ensure that Docker is installed and running on the device.

  2. Verify that the device is properly registered in the portal.

  3. Check any error messages in the terminal where you ran the docker compose command. For example, if there are issues pulling images, it might be due to your network setup.

  4. If there is a container named something like octaipipe-manager-{device-id}, make sure to check its logs using docker logs <container-id>.

SuperNode Invalid Timestamp#

Problem

When inspecting SuperNode logs (running in SuperNode container on the device), they mention an “Invalid timestamp” error. For example:

12025-09-23 17:18:10.229 | ERROR :     <_InactiveRpcError of RPC that terminated with:
22025-09-23 17:18:10.229 |   status = StatusCode.UNAUTHENTICATED
32025-09-23 17:18:10.229 |   details = "Invalid timestamp"
42025-09-23 17:18:10.229 |   debug_error_string = "UNKNOWN:Error received from peer
52025-09-23 17:18:10.229 |   {created_time:"2025-09-23T16:18:10.228634257+00:00", grpc_status:16, grpc_message:"Invalid timestamp"}"
62025-09-23 17:18:10.229 | >
72025-09-23 17:18:10.427 | INFO :      Disconnect and shut down

Solution

This means your local device time is out of sync with the actual time. To resolve this issue, you can synchronize your device’s clock with a time server or manually adjust the time settings. Exactly how this is done depends on your operating system and exact setup. For Linux systems, you can use the timedatectl command to check the time, and enable automatic time synchronization with:

1sudo timedatectl set-ntp true

This will enable NTP-based time synchronization using the system’s default service (such as systemd-timesyncd). Alternatively, you can install and use chrony for more advanced time synchronization options.

Docker Permission Denied on Windows (WSL)#

Problem

When running OctaiPipe edge clients on a Windows machine through Docker Desktop, the following error occurs:

1dial unix /var/run/docker.sock: connect: permission denied

Solution

This issue occurs when Docker permissions are not properly configured inside WSL. To resolve the problem:

  1. Ensure all users and groups in WSL are correctly set up (for example, app user and Docker group with ID 49999). The docker.sock file should be owned by root:docker.

  2. Do not run the Docker Compose file for the edge client (docker-compose.yml) from PowerShell. Instead, run it from within WSL, where the user setup has been completed.

  3. Try restarting the edge client container with:

    1docker restart {container-id}