Troubleshooting PathWise itself

When the tool that troubleshoots is the thing acting up. Start here to find the cause fast.

The usual suspects

• A network check fails on a healthy network. This is often the missing host permission for ping. See System requirements.
• The model does not answer. Check your model choice and, if you use a frontier model, your key. See the reasoning engine.
• The engine will not start. Check Docker, the mounted data paths, and the license. See Installation.
• Records reset after a restart. Your data volumes are probably not mounted. See Installation.

Where the logs are

PathWise does not write a separate log file, and this build has no adjustable log level. Docker captures its output. Read it with docker compose logs pathwise, or follow it live with docker compose logs -f pathwise.

What the log messages mean

A healthy boot prints PathWise engine listening on http://<host>:<port>. A first boot on an empty database also prints First run: no users yet. Set up access via POST /api/setup.

• A block starting with probe tools:. One or more probe programs are missing from the environment. The lines name each missing tool.
• A block starting with ping capability:. The host is blocking the ping socket. Apply the sysctl under System requirements.
• A line starting with Data directory is not writable:. The data mount is missing or read-only. Fix the volume mount from Installation.
• A line starting with No reasoning-engine API key configured yet. No hosted-model key is saved. The rest of that line directs you to Settings, under Model.

Getting help

If you are still stuck, see Support and what is covered.