Crontab Issue. Last job execution ran 4 hours ago. Something seems wrong

ℹ️ Support
,
21

Hello!

I had the same issue. It could be a not enabled cache called APCu.
To enable this cache do this (from Nextcloud docs):
APCu is disabled by default on CLI which could cause issues with nextcloud’s cron jobs. Please make sure you set the apc.enable_cli to 1 on your php.ini config file or append --define apc.enable_cli=1 to the cron job call.

Or manually:
nano /etc/php/x.x/cli/php.ini
(x.x is your php Version e.g. 7.4 or 8.1)
write the next line into this file:
apc.enable_cli=1

Hint:
Enabling apc in /etc/php/x.x/apache2/php.ini doesn’t work!

Reboot and test.
Hope I could help you.

22

I will give that a try and let you know.

23

The warning still persists. I really have no idea how to fix this. This is extremely frustrating.

24

Why not use the webcron feature instead? Just run it as a curl crontab

25

That’s that other one I keep hearing about. Seems like a lot of people are having problems with it. This is the official image:

https://hub.docker.com/_/nextcloud

26

Not sure how to use curl in CRON so I will have to research that. I did switch to WEBCRON in the UI, but later when I refreshed the page, the CRON (recommended) option was selected automatically. But I still see the warning…Last job execution ran 4 hours ago. Something seems wrong.

27

Have you installed php-apcu or are you using a different cache? If not, install it and test it with the settings I told you.

28

Good morning…Last night I noticed there was a nextcloud update so I updated the docker container. And hocus pocus Fu**kin’ magic my CRON now works. I didn’t do anything other than apply the update. I find these sorts of issues that magically go away very frustrating. Thank you very much to you guys for trying to help me fix this issue. I will close this issue later today.