Troubleshooting
Troubleshooting
Section titled “Troubleshooting”Common issues and how to resolve them.
Connection Issues
Section titled “Connection Issues”Connection Refused
Section titled “Connection Refused”Symptom: ECONNREFUSED when connecting to MindFry.
Solutions:
- Verify server is running:
docker psor check process - Check port binding:
netstat -an | grep 9527 - Verify firewall rules allow port 9527
Connection Timeout
Section titled “Connection Timeout”Symptom: SDK hangs on connect().
Solutions:
- Increase timeout:
new MindFry({ timeout: 10000 }) - Check network path to server
- Verify no firewall blocking
Memory Issues
Section titled “Memory Issues”Lineage Not Found
Section titled “Lineage Not Found”Symptom: NotFound error for existing key.
Causes:
- Key never created
- Lineage decayed to DORMANT
- Below consciousness threshold
Solutions:
- Use Executive Override:
brain.lineage.get(key, 0x07) - Check mood:
brain.system.stats()and adjust if needed - Stimulate to raise energy:
brain.lineage.stimulate({ key, delta: 0.5 })
Repressed Status
Section titled “Repressed Status”Symptom: Repressed error on GET.
Cause: Memory energy below consciousness threshold.
Solutions:
- Lower threshold:
brain.system.setMood(0.8)(euphoric) - Bypass:
brain.lineage.get(key, 0x02)(INCLUDE_REPRESSED)
SDK Issues
Section titled “SDK Issues”RangeError on Response
Section titled “RangeError on Response”Symptom: RangeError: Invalid array length in SDK.
Cause: Protocol version mismatch.
Solution: Update SDK to latest version:
npm update @mindfry/clientFrame Parsing Error
Section titled “Frame Parsing Error”Symptom: Garbled responses or deserialization failures.
Cause: Incomplete frame handling.
Solution: Ensure using SDK v0.4.0+ with proper FrameDecoder.
Persistence Issues
Section titled “Persistence Issues”Resurrection Failed
Section titled “Resurrection Failed”Symptom: Data not restored after restart.
Solutions:
- Check
/datavolume is mounted - Verify sled files exist:
ls /data/akashic/ - Check logs for corruption errors
Snapshot Not Found
Section titled “Snapshot Not Found”Symptom: SYS.RESTORE fails with unknown snapshot.
Solutions:
- List available:
ls /data/snapshots/ - Use exact name from
SYS.SNAPSHOT
Performance Issues
Section titled “Performance Issues”High Memory Usage
Section titled “High Memory Usage”Cause: Approaching max_lineages limit.
Solutions:
- Increase
MINDFRY_MAX_LINEAGES - Force decay by lowering
MINDFRY_DECAY_LAMBDA - Prune low-energy lineages
Slow Propagation
Section titled “Slow Propagation”Cause: Dense bond graph causing deep cascades.
Solutions:
- Increase damping via
PHYSICS.TUNE - Use
NO_PROPAGATEflag for bulk operations