I just upgraded Ubuntu from 24.04 to 26.04. I have nextcloud running on “bare metal” (no docker) here. I’m using Collabora Online - Built-in CODE Server 26.4.402 on nextcloud.
After the upgrade, I’m unable to open .odt .ods… files: the browser shows “Document loading failed. Starting the built-in CODE server is taking longer than expected”
On coolwsd.log I can find:
wsd-18467-18467 2026-09-30 14:57:01.539053 [ coolwsd ] INF Total available memory: 0 KB (0 GB), System memory: 0 KB (0 GB), cgroup limit: 0 KB, cgroup soft-limit: 0 KB, configured memproportion: 25%, actual percentage of system total : 1e+02%, current usage: 66936 KB (1e+02% of limit)|home/collabora/jenkins/workspace/package_code_26.04_rpm/rpmbuild/BUILD/coolwsd-26.04.4.2/wsd/Admin.cpp:618 wsd-18467-18467 2026-09-30 14:57:01.539072 [ coolwsd ] ERR Low memory condition detected: only 0 MB of RAM available|home/collabora/jenkins/workspace/package_code_26.04_rpm/rpmbuild/BUILD/coolwsd-26.04.4.2/wsd/Admin.cpp:630
It seems that coolwsd only can see 0MB of RAM. My machine has 16GB of RAM, everything worked before upgrading to Ubuntu 26.04.
The “0 MB of RAM” line is a clue about where coolwsd is running, not a real memory problem. coolwsd reads MemTotal: from /proc/meminfo, and 0 means it could not open the file at all.
Ubuntu 26.04 ships a much more locked-down apache2.service than 24.04. It now sets ProcSubset=pid (hides everything in /proc except per-process directories), plus RestrictNamespaces=yes, MemoryDenyWriteExecute=yes, PrivateDevices=yes and ProtectSystem=full. The built-in CODE AppImage is started by PHP from inside Apache, so it inherits that whole sandbox. The memory message is the visible symptom; the other restrictions are very likely what breaks document loading.
The restart also clears Apache’s private /tmp, so the built-in server starts fresh. Once it works you can try re-enabling the settings one at a time to see which ones coolwsd really needs.
Longer term, running CODE as its own service (packages or Docker) avoids sharing the web server’s sandbox altogether.
If documents still fail afterwards, please post grep -E "ERR|WRN" coolwsd.log | head -50
I also applied the modifications to /etc/systemd/system/apache2.service.d/override.conf via systemctl edit apache2, uninstalled and reinstalled CODE server from nextcloud web gui, but .odt documents are not loading. Here is the log. The memory error disappeared, but another error is here now:
wsd-226125-226125 2026-10-01 08:47:49.163758 [ coolwsd ] WRN No cache path is set in cache_files.path. Disabling cache|home/collabora/jenkins/workspace/package_code_26 .04_rpm/rpmbuild/BUILD/coolwsd-26.04.4.2/wsd/COOLWSD.cpp:2151 wsd-226125-226125 2026-10-01 08:47:50.967569 [ coolwsd ] ERR Could not open proof RSA key, Poco exception: I/O error: EVPPKey::loadKey('/etc/coolwsd/proof_key') frk-226138-226138 2026-10-01 08:47:50.973243 [ coolforkit-ns ] ERR Security: Running without the ability to filter system calls is ill advised.|home/collabora/jenkins/ workspace/package_code_26.04_rpm/rpmbuild/BUILD/coolwsd-26.04.4.2/kit/ForKit.cpp:988
@giox069 Thanks. Good news first: the memory message is gone, so the Apache sandbox was behind that line. The remaining failure is something else.
The three lines you quoted are normal for the built-in server. The cache and proof-key messages appear on every built-in CODE install, and the seccomp warning is how the AppImage always runs. More telling is what is not there: no error at all when you try to open the document. That suggests the request never reaches coolwsd. Could you send:
The exact message the browser shows now. Is it still “taking longer than expected”, or something else?
All log lines, not only ERR/WRN, from the moment you open a document:
tail -60 $LOG
plus any richdocuments entries in nextcloud.log from the same minute.
The browser was frozen on “loading”… but now… it works. And I don’t know why. The loadKey ERR and Security ERR are still in the logs, but it works. Documents are loaded.
I don’t really know what unblocked it. Maybe something in the browser cache ? I’m testing now from another PC, not the one I tested last time. I also removed some old Ubuntu 24.04 packages with “apt autoremove” and then rebooted.
I can also confirm that the apache2 unit override cofiguration
is necessary for Ubuntu 26.04. Removing the override makes the “ERR Low memory condition detected: only 0 MB of RAM available” reappear.
It seems that the above apache2 unit override also fixed another nextcloud error:
[Tue Sep 29 20:21:48.453942 2026] [php:warn] [pid 297153:tid 297153] [client 192.168.56.85:43618] PHP Warning: preg_match(): Allocat ion of JIT memory failed, PCRE JIT will be disabled. This is likely caused by security restrictions. Either grant PHP permission to a llocate executable memory, or set pcre.jit=0 in /mnt/d1/shared/www/nextcloud/lib/base.php on line 1277
