Troubleshooting#
Start-Up#
Symptom |
Resolution |
|---|---|
|
Install the Intel GPU driver and confirm |
|
Run |
|
Add your user to the |
|
The model is loading and warming up on the GPU. Follow progress with |
|
Check |
Settings changes have no effect |
Edit |
Image pull fails |
Check registry access and proxy settings, or build locally with |
Build fails with |
A proxy node intercepts GitHub downloads. See Builds Behind a Proxy. |
Store Services#
Symptom |
Resolution |
|---|---|
A service shows as unavailable in Connected apps |
Confirm the service is running and its URL is reachable from the agent container. Use |
A remote service is unreachable behind a proxy |
Add the service host to |
An HTTPS service fails after it restarted |
The service may have generated a new certificate. Run |
Changes to |
Run |
A remote service stops answering after it restarted |
The agent keeps its MCP session. Run |
A remote service is reachable again but still shows as unavailable |
After repeated failures the agent parks the connection and retries every five minutes. Run |
No events arrive from a remote service |
On the service host, check its event URL points to |
Events from one host fail with a clock-skew or “evidence expired” error |
That host’s clock is behind the agent’s. Enable NTP on every host ( |
Chat and Decisions#
Symptom |
Resolution |
|---|---|
A store question is declined as out of scope |
Rephrase it using store terms such as menu, queue, order, table, or kitchen. Confirm the related service is connected. |
The answer says data is unavailable |
The service that owns the data is not reachable. Check Connected apps. |
An answer takes longer than usual |
Long conversations are occasionally summarised to fit the model’s context. Select New chat to start fresh. |
Chat stops answering and New chat hangs |
A very large answer can exhaust the model’s context. Run |
An event shows Failed |
Check |
Approve returns an error |
The proposal expired after five minutes or was already decided. |
The weather event does nothing |
Use a valid condition ( |
Learning#
Symptom |
Resolution |
|---|---|
Learn now does not appear |
The UI needs 20 responses for the service and 5 for one event type. |
|
Collect more varied responses. A rule needs at least two taught records and must not be rejected as often as taught. |
A learned rule refers to fields or item IDs your services don’t have |
It was learned from data for different services. Delete |
Learned skills are not in the repository’s |
They are in the |
Collect Diagnostics#
make status
make logs
docker compose logs ovms --tail=200
curl -s http://localhost:8600/status?force=1