pyCANdo
Download

A project runtime will not start

Find configuration, Python environment, dependency, and CAN-channel errors behind a failed project start.

  • The Start action fails or the project immediately stops.
  • The project runtime status reports an error.

Diagnose the project start

Read the runtime status first, then follow the first error into the service journal or project logs.

  1. Read the project status

    Use the project identifier—not its filesystem path—and copy the first reported error.

    runp status -p <project>

  2. Inspect runtime and application logs

    The service journal shows startup failures. The `pyrbs` logs show Python-side and core runtime errors.

    journalctl -u "runp@$(systemd-escape '<project>').service" -n 100 --no-pager
    tail -n 100 /var/log/pcd/pyrbs/<project>.log
    tail -n 100 /var/log/pcd/pyrbs_core/<project>.log

  3. Check the required project files

    Confirm that `config/config.toml` and `rbs/main.py` exist. If you selected a profile, confirm that its file exists under `config/profiles/` and contains valid TOML, JSON, or YAML.

  4. Repair the project environment if needed

    If the log reports a missing `run_rbs` executable or Python dependency, rebuild the project environment and then start it again.

    runp venv <project>
    runp start <project>
Service health

A service is reported as “Not healthy”

Use the diagnosis details, service status, and recent logs to find out why a pyCANdo component is unavailable.

CAN bus

A CAN interface or channel is unavailable

Check whether the configured CAN channel exists, is up, and matches the connected hardware.