On 08/04/2020 23:11, Cameron Simpson wrote:
On 08Apr2020 14:54, Terry Barnaby terry1@beam.ltd.uk wrote:
Note this has happened a few times this year, (approx 1 in 64 x) so not related to DST changes anyway. Might be due to chrony clock resyncs I suppose but I think something stranger is going on here or something silly and obvious in what I am doing.
I will have a more detailed look at the system and my backup shell script and create a simple test cron job to see if it shows the same thing ...
How about sticking:
echo "`date` [`date -u`]: start $0 $*" >>some_log_file
at the start. Makes sure the job is actually starting at the cron time. Might tell you more about the system time situation.
Cheers, Cameron Simpson cs@cskk.id.au _______________________________________________
The script already has date/time and the log shows (The Wed 8th entries entry having the PID):
Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt /data/backup at Tue 7 Apr 23:01:01 BST 2020 Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt /data/backup at Tue 7 Apr 23:01:01 BST 2020 Backup aborted as locked by another backup Bbackup completed status: 0 at Wed 8 Apr 00:58:57 BST 2020 Bbackup 805476 / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt /data/backup at Wed 8 Apr 23:01:01 BST 2020 Bbackup 27200 / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt /data/backup at Wed 8 Apr 23:01:01 BST 2020 Backup aborted as locked by another backup Bbackup completed status: 0 at Thu 9 Apr 01:29:24 BST 2020
I will change it to show down to the us.
Terry