On an ESXi server you can't access the crontab via crontab -e, but you can edit the config file and kill & restart the crond.
What it took to get this running:
Login to ESXi as root and execute these steps
Kill crond
[root@esxi1:~]/bin/kill $(cat /var/run/crond.pid)
Edit crontab
[root@esxi1:~] vi /var/spool/cron/crontabs/root
#min hour day mon dow command
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /sbin/hostd-probe ++group=host/vim/vmvisor/hostd-probe
00 1 * * * localcli storage core device purge
#min hour day mon dow command
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /sbin/hostd-probe ++group=host/vim/vmvisor/hostd-probe
00 1 * * * localcli storage core device purge
# My added lines
0 13 30 8 * /sbin/vmware-autostart.sh stop
15 13 30 8 * /sbin/shutdown.sh && /sbin/poweroff
0 13 30 8 * /sbin/vmware-autostart.sh stop
15 13 30 8 * /sbin/shutdown.sh && /sbin/poweroff
Start crond
[root@esxi1:~]/usr/lib/vmware/busybox/bin/busybox crond
Above added lines in the crontab will result in the guests to be shutdown on 30th of August at 13:30 UTC time. The last line will shutdown the ESXi host 15 min later. So, check your system time via date.
[root@esxi1:~] date
Thu Aug 30 16:38:36 UTC 2017
Thu Aug 30 16:38:36 UTC 2017
The gracefull guest shutdown will only work if the guests are configured for autostart in ESXi. The original crontab will be restored automatically with the next system boot.
If you want your changes to be permanent you could archieve this by editing
/etc/rc.local.d/local.sh to readd your changes at every system startup.
/etc/rc.local.d/local.sh to readd your changes at every system startup.
Example:
#!/bin/sh
#Kill crond
/bin/kill $(cat /var/run/crond.pid)
#Your added lines
/bin/echo "0 13 30 8 * /sbin/vmware-autostart.sh stop" >> /var/spool/cron/crontabs/root
/bin/echo "15 13 30 8 * /sbin/shutdown.sh && /sbin/poweroff" >> /var/spool/cron/crontabs/root
#Start crond
/usr/lib/vmware/busybox/bin/busybox crond
exit 0
#Kill crond
/bin/kill $(cat /var/run/crond.pid)
#Your added lines
/bin/echo "0 13 30 8 * /sbin/vmware-autostart.sh stop" >> /var/spool/cron/crontabs/root
/bin/echo "15 13 30 8 * /sbin/shutdown.sh && /sbin/poweroff" >> /var/spool/cron/crontabs/root
#Start crond
/usr/lib/vmware/busybox/bin/busybox crond
exit 0
Keep in mind that all these changes are not officially supported by VMware. Use at your own risk.
2 comments:
Unified Communications Providers ProjectsComm is a team of technology consultants. Our engineers and solutions architects are accredited to the highest standards to provide best-in-class professional service and support. Our bespoke services are designed to meet your organization’s needs. We bundle our collaboration services together to provides your business with great ROI (Return of investment) along with a fit-to-purpose solution for seamless communication infrastructure. At Projects Comm, we provide bespoke Cisco & Microsoft telephony solutions for every type of business. From Pharmaceuticals and advertising companies, to manufacturers and Universities – we have over 20 years of experience in the communications technology sector, well-versed in both traditional and new ways of communicating.
Thanks for sharing this informative blog. Empower your team with Telerain's Unified Communications software. Streamline workflows, enhance productivity, and stay connected from anywhere. Visit us today!
Post a Comment