Hi
After upgrade, cron jobs started to fail.
Example of an error:
sh: 19: cd: can’t cd to /tmp/tmp.9KfcXxjpja Execution directory inaccessible.
I don’t a alow execution from tmpfs, as I consider it unsafe. (noexec for /tmp in fstab)
Is this the problem? (Everything was OK up to 1.5.0)
BR,
Neven
I have no Idea.
How can I find that?
I know only what the number of the cronjobs that failed (114, 115, 116, 117 and 118) from the error log, and that they are jobs from admin user:
spooled jobs fro this user are:
*/2 * * * * sudo /usr/local/hestia/bin/v-update-sys-queue restart
15 02 * * * sudo /usr/local/hestia/bin/v-update-sys-queue disk
10 00 * * * sudo /usr/local/hestia/bin/v-update-sys-queue traffic
30 03 * * * sudo /usr/local/hestia/bin/v-update-sys-queue webstats
*/5 * * * * sudo /usr/local/hestia/bin/v-update-sys-queue backup
10 03 * * * sudo /usr/local/hestia/bin/v-backup-users
20 00 * * * sudo /usr/local/hestia/bin/v-update-user-stats
*/5 * * * * sudo /usr/local/hestia/bin/v-update-sys-rrd
43 5 * * * sudo /usr/local/hestia/bin/v-update-letsencrypt-ssl
*/5 * * * * sudo /usr/local/hestia/bin/v-update-sys-queue letsencrypt
12 5 * * * sudo /usr/local/hestia/bin/v-update-sys-hestia-all
01 00 * * * sudo /usr/local/hestia/bin/v-update-sys-queue daily
*/5 * * * * sudo /usr/local/hestia/bin/v-update-sys-queue dns-cluster
N.
Could be this:
(from hesitia error log)
2021-11-27 03:30:01 v-update-web-domain-stat ‘admin’ ‘domain1.com’ [Error 3]
2021-11-27 03:30:05 v-update-web-domain-stat ‘admin’ ‘domain2.com’ [Error 3]
2021-11-27 03:30:12 v-update-web-domain-stat ‘admin’ ‘domain3.com’ [Error 3]
2021-11-27 03:30:12 v-update-web-domain-stat ‘admin’ ‘domain4.com’ [Error 3]
2021-11-27 03:30:12 v-update-web-domain-stat ‘admin’ ‘domain5.com’ [Error 3]
N.
Just confirming that I had this very same issue. I haven’t been able to track down what caused it yet though.
Had some time today, so I executed all spooled jobs manually.
0 errors.
Can you perhaps update the script that creates this entry:
sh: 19: cd: can’t cd to /tmp/tmp.9KfcXxjpja Execution directory inaccessible.
with the name of the script that is being executed?
N.
That’s what the problem was, we didn’t know what script was generating it. It took me awhile to trace the issue back to it’s source, but we haven’t figured out a fix for it just yet.
It’s related to letsencrypt ssl renewal and it’s harmless. Just annoying. We’ll fix it soon.