Symptoms

You have Acronis Cyber Backup installed in Linux. Scheduled backups do not start. Cyber Protection console doesn't show an error.

In scheduler log (/usr/lib/Acronis/Schedule/), you see this error:

2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): Task:CanRunNow:Can not run task on: 3:1 13:50 Wday=5
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): Task:ExecuteFromWrapper:Fake run.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): Task:NotifySession:Start, code=15014, save=0.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): Task:NotifySession:End, code=15014.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): User:ExecuteFromWrapper:tsk.ExecuteFromWrapper ret=15014, exitCode=-1
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(1): User:ExecuteFromWrapper:Exit, ret=0
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Intf:ExecuteFromWrapper:ret=0
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Postpone:PostponeRunWaitThreadFunc:Started
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Intf:crontab_intf:Already inited.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Intf:GetWaitId:Start.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Postpone:PostponeRunWaitThreadFunc:Wait changes 4
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Intf:crontab_intf:Already inited.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Intf:WaitChangesEx:Start wait on /var/lib/Acronis/Scheduler/waitdata/waitcmn/4_0_9177.wait.
2019-03-01T13:50:01+0000 schedwrapper-bin(9177)(0): Postpone:~PostponeRunWaitShutdowner:Stop wait changes 4

Cause

Timezone of crontabs differs from device time zone.

Solution

Adjust crontabs time zone to device time zone.

1. Find out device timezone
   # timedatectl
   In the Time Zone line of the output, you can get the correct timezone value.
2. Set this value in the crontabs:
   TZ=<value from step 1>
3. On CentOS, restart crond service:
   sudo systemctl restart crond.service