Open JOpsDev opened 1 month ago
This could potentially be a bug/issue with Collabora, will look into it a bit and give an update here.
I took a deeper look, and I am pretty sure this would specifically be related to how the built-in CODE server manages it
Especially after reading your analysis in the other thread, it makes me think this is the case.
Can you provide any input here? @timar @eszkadev
Describe the bug When using CODE the coolwsd process seems to exit after some time and the coolwsd and appimage_extracted directories are not removed.
To Reproduce Steps to reproduce the behavior:
Expected behavior /tmp/snap-private-tmp/snap.nextcloud/tmp should not be filling up with left over coolwsd and appimage_extracted directories.
Server details
Operating system:
Name Version Rev Tracking Publisher Notes nextcloud 29.0.7snap1+git2.a85bd4b 44403 latest/candidate nextcloud✓ -
snap 2.63+20.04ubuntu0.1 snapd 2.63+20.04ubuntu0.1 series 16 ubuntu 20.04 kernel 5.4.0-196-generic
Nextcloud version: nextcloud 29.0.7snap1
Version of the richdocuments app Nextcloud Office Version 8.4.7
Version of Collabora Online Collabora Online - Built-in CODE Server Version 24.4.802
Configuration of the richdocuments app
/tmp/snap-private-tmp/snap.nextcloud/tmp/coolwsd.vE1VGjlRM9/coolwsd.log ends with:
I have been sent here from https://github.com/nextcloud-snap/nextcloud-snap/issues/2921 .
When I kill the coolwsd process e.g. with "killall coolwsd" the coolwsd and appimage_extracted directories are removed. If I just let it time out with the above log messages the tmp directories stay around forever.