Hi folks, weāre using Nextcloud 12.0.3, latest Collabora plugin, latest Collabora release (tested both packages installed locally on Nextcloud server and via the official Docker image) hosted on Ubuntu 16.04 systems. This isnāt a consistently present error, but seems to be triggered once a document reaches a certain size.
Firstly, yes there is definitely plenty of storage on the server. I have tested with both and unlimited quota set, and a generous quota with plenty of spare room. A test document triggering this was created blank from within Nextcloud, only edited within Collabora environment. Saves were frequent and successful until finally after adding 3-4 images, the error popped up.
I found a similar-sounding report of something like this but it was apparently resolved by upgrading Nextcloud. Iām at most recent release on everything, and this has survived at least one update when we deployed 12.0.3.
Best information from the log is:
wsd-00025-00043 03:29:45.099255 [ docbroker_002 ] WRN Disk full while saving docKey [drive.adomain.com:443/apps/richdocuments/wopi/files/182693_oc91kt0hzyub] to URI [https://drive.adomain.com/apps/richdocuments/wopi/files/182693_oc91kt0hzyub?access_token=SCRUBBED&access_token_ttl=0&permission=edit]. Making all sessions on doc read-only and notifying clients.| wsd/DocumentBroker.cpp:667
Of course, the disk is not full. We can upload new files to the server and all Nextcloud functionality is working perfectly. Only Collabora is reporting any issue.
Any suggestions as to whether this is an issue at the Nextcloud or Collabora level and how to properly debug it gratefully received!
Didnāt check the container versionās disk allocation but the locally installed one was on the same disk as the main Nextcloud storage, which only about 20% full. My primary installation is the version installed via packages, I just dropped the docker version on the system as per the official Nextcloud docs to verify that the issue still happened there, and wasnāt just something Iād missed in my install.
It does kinda āfeelā like a temp storage space or a permissions issue on something, but not sure where it could be coming from. After doing this all by the book so far, I canāt see where Iād be having this issue and not everyone else bumping into it all the time. I donāt think Iāve done anything weird or unusual in my setup at all.
I have the same problem with a growing collabora container. After removing the collabora container, the disk has 30GB free space. After starting the collabora container 3.0.0.0, the disk will be filled in one day and the disk has no disk space free.
We start collabora with this parameters:
docker run -t -d -p 127.0.0.1:9980:9980 -e ādomain=cloud\.domain\.deā --restart always --cap-add MKNOD collabora/code
We ran version 2.1.5 for weeks without any problems.
We are seeing the same behavior - 11GB in /var/cache/loolwsd. Most of these files seem very old - is it safe to delete files older than say 7 days from this directory?