Collabora Online - Built-in CODE Server crashes my server

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 29.0.11
  • Operating system and version (e.g., Ubuntu 24.04):
    • RedHat Linux EL 9
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.62
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • F5 BigIP LTM VE
  • PHP version (e.g, 8.3):
    • 8.1.30
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • After upgrading to last version f Collabora Online app and to Nextcloud 29.0.11
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Unknown
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

Hi there, during upgrading to Nextcloud 29.0.11 (from 29.0.5), Collabora Online app was upgraded too. After these upgrades, the editing of the documents started having troubles. Sometimes the editing crashes and you need to close and re-open the document, sometimes it is not possible to open the document and in some other cases the server linux crashes. Before crashing, I noticed that the coolwsd process gets bigger and bigger in CPU and memory usage

Steps to replicate it (hint: details matter!):

  1. open and edit a document

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

nothing shown in the log files

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

N/a

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

N/a

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

{
    "system": {
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "REMOVED SENSITIVE VALUE",
            "REMOVED SENSITIVE VALUE"
        ],
        "trusted_proxies": "***REMOVED SENSITIVE VALUE***",
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "29.0.11.1",
        "overwrite.cli.url": "REMOVED SENSITIVE VALUE",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "maintenance": false,
        "overwriteprotocol": "https",
        "memcache.local": "\\OC\\Memcache\\Redis",
        "filelocking.enabled": true,
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 6379,
            "timeout": 0
        },
        "default_language": "it",
        "default_locale": "it_IT",
        "mail_smtpmode": "smtp",
        "mail_sendmailmode": "smtp",
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "587",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpauth": 1,
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "loglevel": 2,
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory",
        "updater.secret": "***REMOVED SENSITIVE VALUE***",
        "theme": "",
        "upgrade.disable-web": true,
        "twofactor_enforced": "true",
        "twofactor_enforced_groups": [],
        "twofactor_enforced_excluded_groups": [],
        "skeletondirectory": "",
        "app_install_overwrite": [
            "groupfolders"
        ]
    }
}

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

Are you sure, that /var/log/apache is empty? I do not believe it.
How many RAM is available on the system?

Hello,
first of all thank you for your interest in my problem.
I have 16gn of RAM on my server.
As per what mentioned in the installation instructions concerning Collabora online, the logs should be under /tmp directory in a folder called “coolwsd*”, but I do not have that directory. In my /var/log/httpd/… the error log files do not mention anything relating the problem I have and the access log file only shows this

Time Taken: 0 208267 192.168.254.10 - “” [12/Feb/2025:17:00:34 +0100] “GET /index.php/apps/richdocuments/wopi/files/36627_ocw2k1u9dxgg?access_token=***_token_ttl=0&permission=edit%2Fws%3FWOPISrc%3Dhttps%3A%2F%2Fnc.comune.re.it%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F36627_ocw2k1u9dxgg&compat= HTTP/1.1” 200 950 “-” “COOLWSD HTTP Agent 24.04.11.2” “-” “oc_sessionPassphrase=3A7VT7zUdiGICVMKn9KcT3aPcRwpBx3R8%2FZLf5XUrJApks5h9bUsR93uEnVBWk; path=/; secure; HttpOnly; SameSite=Lax, __Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax, __Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict, ocw2k1u9dxgg=0i5op0tmji3jkkn0unco3orme2; path=/; secure; HttpOnly; SameSite=Lax” “COOLWSD HTTP Agent 24.04.11.2” “172.16.0.52”

BTW, I did some other tests and I found that the problem is after the saving of a file. I am experiencing this behaviour with XLS and ODT files. When I open a file for editing, after my activity, if I save the file and I do not close it, the collwsd process starts growing in memory and CPU very fast. In a while it reaches more than 80% of RAM and more than 50% of CPU and, when this occurrs, I cannot edit my file, the only option I have is to close it.

I had almost the exact same issue. See this:

Unfortunately without any luck figuring it out. I gave up and will move to a dedicated Collabora host, as soon as I find the time.

Very sad. The difference between you and me is that my NC server version is 29.0.11 and yours is 30.0.3 and the way the error occurs. I had to downgrade the collabora online version to the previous, now the editing still fails (or the document are not open), but at least mem and CPU consuption of coolwsd process do not crash my linux server. If I upgrade to latest collabora online version, coolwsd process grows in mem and CPU and crashes my linux server.
Thank you for sharing with me your experience. I do not know what to do as turning to a beta version of NC is not possible as I am in production.

1 Like