Troubleshooting Guide
Common issues and solutions when building, running, and deploying Pranor modules.
Issue 1: Compiler Mismatched Signatures
Symptom: go test ./... or pranor build fails with:
undefined: SomeFunction or mismatched argument types.
Resolution
- Verify the
go.workfile is configured at the workspace root to include all local subpackages. - Clean compiler build artifacts:
go clean -cache -testcache - Regenerate packages list:
serv packages --update
Issue 2: Service Registry (Pranor Mesh) Offline / Heartbeat Dropped
Symptom: Backend services fail to register, printing:
[ERROR] failed to connect to mesh registry on http://localhost:8089.
Resolution
- Verify that
Pranor Meshis running:serv status - Check firewall or Docker network bindings. The default mesh discovery port requires UDP
:9999to be open for multicast discovery. - If multicast fails in your hosting environment, bypass discovery and explicitly declare the registry target:
export PRANOR_MESH_ADDR="http://127.0.0.1:8089"