> > I think it is working at the moment. But it stops every now and then. As > > you would see below, mbsync.service also ends with an error. There is no > > such error when I run mbsync -V daily myself. > > > the error is certainly stochastic, so it's more likely to occur when you > auto-poll often than during a few manual runs.
I am afraid I don't understand what you mean by the error being stochastic. But it seems to never happen when I run mbsync manually and almost always be the case when it is run through systemd. > the fact that the failure is silent is obviously an mbsync bug. i recommend > that you use a build from git master - it has more reliable error reporting. > it also has additional exit codes to let you know whether running the > post-exec action makes sense. I have built isync from git master: mbsync -v gives me: isync 1.5.0 But I still see the same message in systemd logs. mbsync.service: Failed with result 'exit-code'. Failed to start Mbsync synchronization service What should I do for more verbose error reporting? > > Is this error makes systemd stop running it repeatedly? > > > i guess? systemd has protection mechanisms against error floods. you can > configure the exact behavior. Can you kindly point to how? Is there a way of telling systemd to just silently ignore these errors? Thanks very much. V. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
