You are not logged in.
Pages: 1
Same situation here, we have a VMware ESXi 6.7 server where the cron jobs are executed twice:
2020-10-02T00:05:01Z crond[2099813]: crond: USER root pid 2471658 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2020-10-02T00:05:01Z crond[2099813]: crond: USER root pid 2471659 cmd /etc/cim/lenovo/refresh.sh
2020-10-02T00:05:01Z crond[2099813]: crond: USER root pid 2471660 cmd /scratch/XSI/XSIBackup-Free/jobs/001 > /dev/null 2>&1
2020-10-02T00:05:01Z crond[2099698]: crond: USER root pid 2471664 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2020-10-02T00:05:01Z crond[2099698]: crond: USER root pid 2471665 cmd /etc/cim/lenovo/refresh.sh
2020-10-02T00:05:01Z crond[2099698]: crond: USER root pid 2471666 cmd /scratch/XSI/XSIBackup-Free/jobs/001 > /dev/null 2>&1
It's a Lenovo server and another instance of cron is executed as /bin/crond from /etc/init.d/179.lenovo-cronjob or /etc/cim/lenovo/register_ipp_schema:
# ps -c | grep cron
2099698 2099698 crond /bin/crond
2629914 2629914 busybox /usr/lib/vmware/busybox/bin/busybox crond
# ls -l /bin/crond
lrwxrwxrwx 1 root root 35 Oct 3 2018 /bin/crond -> /usr/lib/vmware/busybox/bin/busybox
On server restart, the call to cron-init in /etc.rc.local.d/local.sh is needed to set up the contents of cron, but is also starts the busybox crond instance. Even if you kill the busybox crond process, xsibackup --update-cron will restart it.
Lenovo's mechanism to start/restart cron is
CRONID=$(sed '1q' /var/run/crond.pid)
kill -9 "${CRONID}"
/bin/crond
but server seems to be reacting also to echo root >/var/spool/cron/crontabs/cron.update as a signal for crontab changes. Perhaps one of those could be used instead?
Pages: 1