SOLO-5083

SoloLogsDirectoryNotWritableSoloError

Description

Thrown when solo cannot write to its log directory or to one of the log files inside it; the message names the offending path and the underlying failure is wrapped in cause. solo opens solo.ndjson and solo.log under its logs directory before running any command, so an unwritable path there stops every invocation — including solo --version, which otherwise touches nothing. The usual cause is a directory or log file left behind by an installation that ran as a different user, for example an earlier sudo npm install -g @hiero-ledger/solo, which leaves the files owned by root.

Troubleshooting Steps

1. Check who owns the path: ls -la ~/.solo ~/.solo/logs
2. Take ownership if it belongs to another user: sudo chown -R “$(id -u):$(id -g)” ~/.solo
3. Or delete the directory and let solo recreate it: rm -rf ~/.solo
4. Reinstall without sudo so no root-owned files are left behind: npm install -g @hiero-ledger/solo
5. Or point solo at a writable location instead: export SOLO_HOME=