2019-12-23, 15:31:18
Let me add what is currently our theory of what happened.
As it looks like the vimalinWorker process got hung on sending an email, either due to a slow email server or due to a time out.
This should have resulted in writing out a nice error to the log and leave it at that.
Instead the vimalinWorker process got hung which caused the impression of nothing happening once scheduling a job.
Here this meant ending up with a lot of scheduled backup jobs.
With currently no recourse to let it run or uninstall - with clear settings option - and install again.
Neither options are ideal, so I will look into that.
If you suspect that the worker process hangs and it isn't doing anything, then it is safe to kill from Activity Monitor, it should restart and your backups will then be processed.
Of course the vimalinWorker process should not hang on such a scenario, so I will also try to reproduce this and see if it can be fixed to work as expected.
--
Wil
As it looks like the vimalinWorker process got hung on sending an email, either due to a slow email server or due to a time out.
This should have resulted in writing out a nice error to the log and leave it at that.
Instead the vimalinWorker process got hung which caused the impression of nothing happening once scheduling a job.
Here this meant ending up with a lot of scheduled backup jobs.
With currently no recourse to let it run or uninstall - with clear settings option - and install again.
Neither options are ideal, so I will look into that.
If you suspect that the worker process hangs and it isn't doing anything, then it is safe to kill from Activity Monitor, it should restart and your backups will then be processed.
Of course the vimalinWorker process should not hang on such a scenario, so I will also try to reproduce this and see if it can be fixed to work as expected.
--
Wil