So I’ve recently upgraded my docker image of nextcloud. And I have a cloudflare worker running for the webcron, but it isn’t working, and activating it manually does nothing too.
The logs sadly don’t return anything usefull.
I hope you can help, and I’ll try to provide more information if needed.
(And yes, I have tryed another post here, but that didn’t work, but I can’t find the link rn)
other posts related to docker and cron might be useful
I don’t have detailed answers for all the questions. just see a working solution from my setup:
additional cron container has same settings as app container (image, ENV, volumes, DB connection)
the only difference is the entrypoint, this is entrypoint: /cron.sh
this results in cron.php running with access to files and DB so it can perform background tasks of the instance
I’m running my nextclud instance via docker (compose file adopted from
here). There is already a container running /cron.sh, which starts a busybox with cron, which starts cron.php every 5 minutes.
Now my question is: how to do i add additional tasks? (i.e. ./occ fulltextsearch:index)
I do not want to rebuild the nextcloud image just for adding a cron task. And i do not want to use the host for managing tasks in the container (host systemd oder host cron)
any way to manage this?
I’m aware of these, but I’d like to use a webcron, since cpu usage spikes with running a local as well as a docker cron
Maybe the above mentioned issue is related to:
Nextcloud version: 23.0.3
Operating system and version: Ubuntu 20.04.4 LTS
Apache or nginx version: Apache, unknown version (web hoster)
PHP version: 8.0.16
Yesterday I upgraded my Nextcloud installation from 22.x to 23.0.3. Since then (it never occured before) I get this error message in the admin panel under Administration - General settings (please note: I use the German version and I translated messages and menus, which means it may be called differently):
“Some jobs have not been exec…
Ah, that’s the one I was looking for :D. Might try changing the log level later, but afaik there’s no real solution once again, and using ajax doesn’t really help either.