Closed Githopp192 closed 1 month ago
Logs of https://github.com/nextcloud/server/pull/45804 and https://github.com/nextcloud/server/pull/42391 would be helpful to identify the job and its arguments.
cron job did end now, run time ~ 7 - 8 hours
memory & cpu consumption did normalize for that moment - no increase in ==> /tmp/php-fpm
not sure if the new maintenance feature could be the culprit - did change the value now from:
'maintenance_window_start' => 2,
to :
'maintenance_window_start' => 100, (disabling it).
Do you need any other logs, when yes - which ones ?
Do you need any other logs, when yes - which ones ?
The messages of of https://github.com/nextcloud/server/pull/45804 and https://github.com/nextcloud/server/pull/42391.
Do you need any other logs, when yes - which ones ?
The messages of of #45804 and #42391.
you mean the nextcloud.log ?
you mean the nextcloud.log ?
Yes. The same one we ask for in our bug reporting template. :)
you mean the nextcloud.log ?
Yes. The same one we ask for in our bug reporting template. :)
Yes, i'd love to do that, but as there is no possibility (afik), to attach this as "non public" .. I would say refrain from putting this log with very sensitive user information (IP...and more) to public
We only need a sample of the long running job entries. We don't need IPs or any identifying information. And we certainly don't want the entire log file.
Without the log entry I'm not sure what you expect us to do. :-)
You can also look at it yourself though: it should indicate what job and what app.
Yes, Josh - can understand :-)
I'll see, what i can do - related to filter out the log ...
on the other hand .. is not only an issue, which affects my server - this issue could become a critical one for the enterprise ==>
https://github.com/CollaboraOnline/richdocumentscode/issues/187#issuecomment-2276750318
it seems to be a cron - collabora side effect
it seems to be a cron - collabora side effect
Do you have a log line to back this theory?
it seems to be a cron - collabora side effect
Do you have a log line to back this theory?
no - i haven't - but since i disabled the maintenance specifc run ('maintenance_window_start' => 100, (disabling it), the issue did not re-occur !?
(issue = long running cron & increasing /tmp/php stuff)
you could check the comment of @cableTh0rn in ==>
https://github.com/CollaboraOnline/richdocumentscode/issues/187
"I run a check script to log the time tmp files gets bigger. It is just the maintenance_window time, 100GB in just one hour"
may be the cron maintenance window ('maintenance_window_start') has an influence on the behavior of collabora ?
In this case it would be worth not to close the case, but to investigate it, because there are obviously some people with the same issue ? :-)
I'm happy to reopen once we have some logs that clearly indicate where the problem lies. Right now we have symptoms and speculation. We don't know why or where the memory grows.
⚠️ This issue respects the following points: ⚠️
Bug description
cron job is running 6h 20 minutes (now, CET Time 10:22 / am)
1528 4-18:40:27 /usr/sbin/crond -n 2176627 06:20:58 /bin/sh -c /bin/php -f /var/www/html/nextcloud/cron.php &> /dev/null 2176628 06:20:58 /bin/php -f /var/www/html/nextcloud/cron.php
may be this has to do with the config.php parameter:
'maintenance_window_start' => 2,
Steps to reproduce
Expected behavior
cron job should not take tool long to do the maintenance cron job should not increase memory & cpu footprint continously, that the server gets in trouble
Installation method
Community Web installer on a VPS or web space
Nextcloud Server version
29
Operating system
RHEL/CentOS
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
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
Nextcloud Logs
No response
Additional info
together with the observation of cron, it also shows, among other things, that the php-fpm process uses a lot of space in /tmp/
du -hs /tmp/systemd-private-4c513a85a5cb462b92e805310c385d9e-php-fpm.service-jkmBSp/tmp/coolwsd.0u42WDiYQI/jails/* 5.1G /tmp/systemd-private-4c513a85a5cb462b92e805310c385d9e-php-fpm.service-jkmBSp/tmp/coolwsd.0u42WDiYQI/jails/1976183-9bea7ef2
space used coming from Nextcloud Office (collabora/coolwsd). Space consumption is growing steadily up to 50..60..70G in /tmp
May be the "cron behave" has something to do with this ? (side effect) ?
https://github.com/nextcloud/richdocuments/issues/2676 https://github.com/CollaboraOnline/richdocumentscode/issues/176