sorry , I don`s know how to describe the problem .
let`s see the picture.
I add a cron job to create snapshot in one of my node at 20:00 everyday (No.2 in picture)
and I can confirm that date in node is the correct time (no.2/No.3 in picture)
but in tasks , dunno why , that cron job delayed 8 hours to start at 04:00
and there`s another backup job at that time already , so some of the snapshot will failed due to vm locked.
I config the host timezone to Asia/Taipei using dpkg-reconfigure tz-data long time ago and never change that ever. so why is that crontab time different than task time ?
if I change the host time to UTC , instead of UTC+8 or Asia/Taipei , is that correct way ? and should every nodes in my cluster use the same timezone setting eg UTC , not Asia/Taipei ?
let`s see the picture.
I add a cron job to create snapshot in one of my node at 20:00 everyday (No.2 in picture)
and I can confirm that date in node is the correct time (no.2/No.3 in picture)
but in tasks , dunno why , that cron job delayed 8 hours to start at 04:00
and there`s another backup job at that time already , so some of the snapshot will failed due to vm locked.
I config the host timezone to Asia/Taipei using dpkg-reconfigure tz-data long time ago and never change that ever. so why is that crontab time different than task time ?
if I change the host time to UTC , instead of UTC+8 or Asia/Taipei , is that correct way ? and should every nodes in my cluster use the same timezone setting eg UTC , not Asia/Taipei ?