You are not logged in.
Dear Forum,
Cannot get cron to work with newest free version 11.0.1. Although the jobs run fine out their own, and the syslog.log shows launches at the correct times, cron works, still nothing happens: no mail and no log entries. Would anybody know how to resolve this issue? This is just too curious...what is wrong here? Are we missing something? Thanks so much!
Dennis
Syslog shows crond doing its job:
cat /var/log/syslog.log
...
2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
...
2019-02-19T02:00:01Z crond[2098971]: crond: USER root pid 2826530 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/002"
...
2019-02-20T01:00:01Z crond[2841383]: crond: USER root pid 2846127 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
Running from command line works very well:
/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001
/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/002
Xsibackup logfile shows no entries:
cat /vmfs/volumes/gc0_ssd1/scripts/xsi-dir/var/logs/xsibackup.log
...
<nothing for those cron times only when running manually>
...
Main log directory /var/log also shows nothing:
[:/var/log] grep -i -I -r -n -s /001 *
syslog.log:2566:2019-02-18T01:00:01Z crond[2098971]: crond: USER root pid 2769648 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
syslog.log:3651:2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
syslog.log:4761:2019-02-20T01:00:01Z crond[2841383]: crond: USER root pid 2846127 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
[:/var/log] grep -i -I -r -n -s 2826075 *
syslog.log:3651:2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
@REF: https://33hops.com/xsibackup-cron-troubleshooting.html
The Troubleshooting Step 2 works: Question: could it be that this should be done after --update-cron?
[root@gc0:/var/log] for p in $(ps -c | grep -v grep | grep 'busybox crond' | awk '{print $1}'); \
> do kill -9 $p;done; \
> /usr/lib/vmware/busybox/bin/busybox crond; \
> ps -c | grep -v grep | grep 'busybox crond'
2840345 2840345 busybox /usr/lib/vmware/busybox/bin/busybox crond
The Troubleshooting Step 3 works:
[root@gc0:/var/spool/cron/crontabs] cat root
#min hour day mon dow command
*/1 * * * * echo "$(date)" >> /tmp/my-cron-test.txt
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
00 1 * * * localcli storage core device purge
# Added by XSIBackupmes/datastore1/xsi-dir/jobs/001"
# Added by XSIBackupmes/datastore1/xsi-dir/jobs/002"
*** ^NOTE: Bottom 2 entries are not logical! ***
[root@gc0:/var/spool/cron/crontabs] cat /tmp/my-cron-test.txt
Tue Feb 19 14:09:01 UTC 2019
Tue Feb 19 14:10:01 UTC 2019
Tue Feb 19 14:11:01 UTC 2019
Tue Feb 19 14:12:01 UTC 2019
Tue Feb 19 14:13:01 UTC 2019
Tue Feb 19 14:14:01 UTC 2019
Tue Feb 19 14:15:01 UTC 2019
However, in text editor, things are shown correctly:
#min hour day mon dow command
*/1 * * * * echo "$(date)" >> /tmp/my-cron-test.txt
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
00 1 * * * localcli storage core device purge
0 1 * * * "/vmfs/volumes/datastore1/xsi-dir/jobs/001"^M # Added by XSIBackup
0 2 * * * "/vmfs/volumes/datastore1/xsi-dir/jobs/002"^M # Added by XSIBackup
*** ^Question: What doe "^M" Stand for? ***
We would really appreciate help from anybody! Thanks so kindly!
Dennis
Offline
solved it myself. Got rid of the '^M' characters in conf/root-crontab. :-)
Offline