Open tograss opened 8 months ago
Same problem for me, up my CPU to 100%. When I try to execute cron.php with the same owner, it finishes normally
https://github.com/nextcloud/server/pull/45804 will provide a bit more clarity. We will start to see which specific jobs are taking ages to complete.
⚠️ This issue respects the following points: ⚠️
Bug description
Since the update to 28 the cron jobs get stuck once a day. I've seen https://github.com/nextcloud/server/issues/42793 and https://github.com/nextcloud/server/issues/43184 but I'm unsure if its the same problem. Feel free to close or link if its the same.
In my case the cronjobs getting not OOM killed instead they keep stuck till so many processes are spanned the system gets slow. When I do a strace I get
lstat("/srv/www/XXX/data/8ED118F1-XXX", 0x7fffc8330550) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
forever. When I create the missing folder the cronjobs end. However next time they got stuck with a different folder.Steps to reproduce
Expected behavior
Cronjobs should end
Installation method
None
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response