Nick Howitt wrote:
Ok so you went for sh and not bash but that is a personal choice. The issue is a known issue with cron/crontab and presumably appears somewhere in its documentation (but is not in "man crontab"). The internet has references like https://stackoverflow.com/questions/2388087/how-to-get-cron-to-call-in-the-correct-paths.
Anyway, it is working now.
I found that article also and is helpful. My solution was adding the full path in the script. Only then it was working. Hopefully someone will run into this solution in the future when running into the same.