MuninnDB

Troubleshooting

Common Issues

⚠️ Windows: DLL or ORT initialization error on first start

The bundled local embedder uses ONNX Runtime, which requires the Visual C++ Redistributable on Windows. Most machines already have it. If you see an error about onnxruntime.dll or "ORT environment init", install the Visual C++ 2019+ Redistributable (x64) from https://aka.ms/vs/17/release/vc_redist.x64.exe and restart muninn. You can also set MUNINN_LOCAL_EMBED=0 if you use another embedder (e.g. Ollama).

⚠️ Port already in use

Another process is using port 8474/8475/8476/8477/8750. Stop the other process or use --mbp-addr, --rest-addr, --mcp-addr flags to configure different ports.

lsof -i :8474   # Find what's using the port
⚠️ ACTIVATE returns 0 results

This happens when no engrams are above the MinScore threshold. Lower the threshold, or check that engrams are in ACTIVE state.

curl http://localhost:8475/api/stats   # Check engram counts by state
⚠️ Decay worker not running

This is expected. In MuninnDB, temporal priority is computed at query time using the ACT-R formula — no background decay worker is required. If you've opted in to the legacy Decay Worker plugin, enable it via workers.decay.enabled = true and check the dashboard at :8476.

⚠️ MCP tools not appearing in Claude

Run "muninn init" to automatically configure claude_desktop_config.json and restart Claude Desktop. Verify muninn is in your PATH with "muninn status".

muninn status   # Check which services are running
⚠️ High memory usage

The L1 cache defaults to 10,000 entries. Also ensure Pebble compaction is running — check disk usage in the web dashboard at :8476.

curl http://localhost:8475/api/health   # Check system health

Getting Help

← Previous Next →