Bad behavior if log file path is invalid

[zyedidia]

When setting up my preferences I accidentally used an invalid path for the path field of the runLog. When I ran jobber reload, this gave the error: Call to Jobber failed: unexpected EOF, and subsequent calls to jobber (jobber reload, jobber list, etc...) all failed with dial unix /var/jobber/1000/cmd.sock: connect: connection refused.

Fixing the path solved the issue, but I had to reinstall jobber first.

Verison: 1.4.4
OS: Ubuntu

[AntoinePrv]

I'm having a similar issue on MacOS

[NicoWeio]

Temporarily renaming (/fixing) the culprit .jobber file and running sudo systemctl restart jobber was sufficient for me – no need to reinstall.

[paxperscientiam]

@AntoinePrv i'm also seeing this error on macos (Big Sur)