You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
/tmp is filled completely by coolwsd.log
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Install Nextcloud-office
Use it for a while
Wait for strange things happening due to lack of /tmp (e. g. not being able to update apps with an "An error occured during the request. Unable to proceed. Couldn't update app." error)
/tmp/systemd-private-31e4fd1a5ed34ba9b565299e8e68e5fd-apache2.service-ZNykpg/tmp/coolwsd.JN32Vaplxe/ (replace the unique identifiers) is filling up with a giant coolwsd.log and the jails are filling with temporary *.upload files.
/tmp is about 2GB and gets filled by this within a week.
The worst are not the uploads/downloads left behind but the log file that is growing from notices that /tmp is filling up. That's a self-fulfilling prophecy.
Expected behavior
I expect coolwsd.log and I expect files below .../jails/... to be removed after uploads/downloads have been processed. If nothing else some slimmed-down logrotate utility limiting these logs that probably nobody is ever reading would be helpful.
Client details:
Any web client.
Server details
Operating system
Debian 11
Web server:
nginx
Database:
mariadb
PHP version:
7.4.33
Nextcloud version:
24.0.6
Version of the richdocuments app
6.3.2
Version of Collabora Online
22.5.802
The text was updated successfully, but these errors were encountered:
I am having the same issue with /tmp. Using build-in CODE server on Debian 10 with Appimage. Version of Collabora Online is 22.5.802, Nextcloud office 5.0.10, Nextcloud 23.0.12.
Since I installed office, /tmp is filling with files/folders that starts with php*, lu*, coolwsd*. Appimage folder has ~800 MB, and total is 3.9G just in one month and growing.
It seems that these temp folders are never removed - obviously this is not what one would expect. At least some instructions how to deal with all these folders would be very useful.
Describe the bug
/tmp is filled completely by coolwsd.log
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
/tmp/systemd-private-31e4fd1a5ed34ba9b565299e8e68e5fd-apache2.service-ZNykpg/tmp/coolwsd.JN32Vaplxe/
(replace the unique identifiers) is filling up with a giant coolwsd.log and the jails are filling with temporary *.upload files./tmp is about 2GB and gets filled by this within a week.
The worst are not the uploads/downloads left behind but the log file that is growing from notices that /tmp is filling up. That's a self-fulfilling prophecy.
Expected behavior
I expect coolwsd.log and I expect files below .../jails/... to be removed after uploads/downloads have been processed. If nothing else some slimmed-down logrotate utility limiting these logs that probably nobody is ever reading would be helpful.
Client details:
Any web client.
Server details
Operating system
Debian 11
Web server:
nginx
Database:
mariadb
PHP version:
7.4.33
Nextcloud version:
24.0.6
Version of the richdocuments app
6.3.2
Version of Collabora Online
22.5.802
The text was updated successfully, but these errors were encountered: