On 09/04/2020 12:24, Ed Greshko wrote:
On 2020-04-09 17:57, Terry Barnaby wrote:
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
Just wondering, if you look at the journal output for that date and time do you see it being started twice?
For example, I have 2 jobs that start at 19:00 each day and for each time they are started I'd see...
Apr 09 19:00:01 meimei.greshko.com CROND[76409]: (egreshko) CMD (/home/egreshko/bin/getpics-vis)
Apr 09 19:00:01 meimei.greshko.com CROND[76411]: (egreshko) CMD (/home/egreshko/bin/getpics-vis2)
Are you getting 2 starts of the same script recorded?
No, the cron log in /var/log/cron only shows one for the backup log below:
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
#/var/log/cron
Apr 8 22:01:01 beam CROND[804585]: (root) CMD (/src/bbackup/bbackup-test1)
Apr 8 22:01:01 beam CROND[804586]: (root) CMD (run-parts /etc/cron.hourly)
Apr 8 22:01:01 beam CROND[804583]: (root) CMDOUT (Starting Bbackup-test1)
Apr 8 22:01:01 beam run-parts[804586]: (/etc/cron.hourly) starting 0anacron
Apr 8 22:01:01 beam run-parts[804586]: (/etc/cron.hourly) finished 0anacron
Apr 8 23:01:01 beam CROND[805474]: (root) CMD (/src/bbackup/bbackup-test1)
Apr 8 23:01:01 beam CROND[805475]: (root) CMD (run-parts /etc/cron.hourly)
Apr 8 23:01:01 beam CROND[805476]: (root) CMD (/src/bbackup/bbackup-beam)
Apr 8 23:01:01 beam CROND[805471]: (root) CMDOUT (Starting Bbackup-test1)
Apr 8 23:01:01 beam run-parts[805475]: (/etc/cron.hourly) starting 0anacron
Apr 8 23:01:01 beam CROND[805473]: (root) CMDOUT (Waking up
70:85:c2:0f:68:07...)
Apr 8 23:01:01 beam run-parts[805475]: (/etc/cron.hourly) finished 0anacron
Apr 8 23:01:21 beam CROND[805473]: (root) CMDOUT (Starting Backup)
Apr 9 00:01:01 beam CROND[806518]: (root) CMD (run-parts /etc/cron.hourly)
Apr 9 00:01:01 beam CROND[806519]: (root) CMD (/src/bbackup/bbackup-test1)
Strange low PID for second bbackup-beam script run ...
Ahggh found it! There was a VM running on our network of an older
development Fedora platform based on an image of our old server and it
still had its backup system running as the cron table entry was still there!
Sorry for all the noise.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
