Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
My syslog time and the kernel's time seem to be in different timezones and cron is not picking up.
I have a droplet in the Bangalore region and I’m facing a problem where my crons are not being picked up if I specify a time.
This is what I’ve debugged so far:
sudo tail -f /var/log/syslog Apr 27 00:45:01 by2rides-app-2 cron: (*system*by2rides-auto-create) RELOAD (/etc/cron.d/by2rides-auto-create)
I created this file /etc/cron.d/by2rides-auto-create itself at exactly Apr 27 10:20 - so clearly the syslog is in a different timezone.
Additionally, I also checked this.
cat /etc/timezone Asia/Calcutta
And my cron.d was very specific:
21 10 * * 1-5 root curl --request GET http://localhost:8080/xyz
The cron is not being piked up. However, if I change it by removing concept of time altogether and keep it at a interval, it gets picked up. So clearly we have timezone issues !
*/5 * * * 1-5 root curl --request GET http://localhost:8080/xyz
Anyone else faced this issue ?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×