Logging & Troubleshooting

Log locations

Log	Path
Host	~/.omo/logs/omo.log
Host RPC	~/.omo/logs/rpc-host.log
Plugin	~/.omo/logs/<plugin>.log

Tail while reproducing an issue:

tail -f ~/.omo/logs/omo.log ~/.omo/logs/redis.log

Common issues

Cannot unlock vault / missing key

• Confirm ~/.omo/keys/omo.key exists and matches the database
• Restore from backup if the key was rotated or deleted
• omo secrets reset --yes creates a new empty database (destructive)

Plugin shows "Not Connected"

• Verify a KeePass entry exists for that plugin (omo secrets list <plugin>)
• Check URL / port / credentials with omo secrets get …
• Press Ctrl+T and select the intended target
• Read ~/.omo/logs/<plugin>.log

Package Manager sync fails

• Check network access to GitHub
• Inspect ~/.omo/index.yaml after a failed sync
• Retry ++S++ in Package Manager

Docker plugin errors

• Ensure the Docker daemon is running
• Confirm your user can access the socket (unix:///var/run/docker.sock)
• Test outside omo: docker ps

Kubernetes plugins

• Validate kubeconfig path and context attributes
• kubectl get ns with the same kubeconfig should work

Nested RPC / deadlock (plugin authors)

Plugins must not open nested RPC back to secrets during GetView. The host pushes config via Configure. See Plugin RPC API.

Still stuck?

• Open a GitHub Issue with OS, omo version, and redacted log snippets
• Do not paste live passwords or key file contents