isync service (i.e. mbsync) stops functioning but produces no logs for debugging #4446
Unanswered
cacology
asked this question in
Everyday usage
Replies: 1 comment 1 reply
-
I have a similar problem. Just started using MacOS this week. Attempting tobootstrap the service with launchctl fails with the same error |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew config
Output of
brew doctor
Description of issue
Calling
brew services start isync
as a non-admin user happily does what is expected: starts a instance of isync (i.e. mbsync) according to my files. However, after about 24 hours, it seems to stop working. I'd like to fix it so it doesn't periodically stall.I've tried to debug it a bit, but cannot get it to produce log files. Can anyone advise?
What I've tried
Restarting it when it stalls works fine, so I wanted to look at the log files. As it is, it sends out and error to
/dev/null
so I wrote my own plist, i.e.homebrew.mxcl.isync-log.plist:
Then I loaded this with
brew services start isync --file=homebrew.mxcl.isync-log.plist
. It didn't seem to be running. I tried/bin/launchctl bootstrap gui/503 /Users/james/Library/LaunchAgents/homebrew.mxcl.isync.plist
which complained:Bootstrap failed: 5: Input/output error.
How can I get a useful log file for this running as a non-admin user? Or, even better, any ideas why isync might be choking over night?
Beta Was this translation helpful? Give feedback.
All reactions