richdocuments icon indicating copy to clipboard operation
richdocuments copied to clipboard

RichDocuments built-in CODE causes significant slowdown/timeout issues

Open eganonoa opened this issue 3 years ago • 51 comments

Over the last couple of weeks Snap and Docker versions of Nextcloud have updated to version 2.0.2 (snap on Friday). After the upgrade the connection to Nextcloud, particularly via the web-interface, slows to a crawl and/or times out. It appears to be caused by richdocuments/collabora.

What is strange about this is that you cannot see easily identify the problem: basic analytics show no major increase in load on the CPU, Ram or I/O, the logs don't immediately show anything out of the ordinary. If you open top/htop on the server, however, and observe for a while you can see big, temporary spikes where available CPU's are maxed out by richdocuments/the Appimage related to Collabora and the Code server. When you go to the admin settings under collabora you can see an error that says that it cannot establish a connection to the in-built CODE server.

The performance problem can be fixed by disabling both the collabora and code server apps: either in the web interface if you can get there through the performance issues, or in the server terminal (sudo snap run nextcloud.occ app:disable richdocuments ; sudo snap run nextcloud.occ app:disable richdocumentscore). After doing that normal service is resumed entirely across the Nextcloud server.

This indicates that the failure to establish a connection to the inbuilt CODE server is the underlying problem and that there is something that happens when upgrading from Nextcloud v. 2.0.1 to 2.0.2 that causes it to break. Strangely, however, this is an issue that only appears to be present in Nextcloud Snap (where slowdown occurs) and Docker (where timeouts occur) and doesn't appear to have been reported by users of the regular Nextcloud: see threads on Nextcloud Community Forum (https://help.nextcloud.com/t/nextcloud-20-0-2snap2-interface-incredibly-slow/100304), Nextcloud Snap Github (https://github.com/nextcloud/nextcloud-snap/issues/1569), and Nextcloud Reddit (https://www.reddit.com/r/NextCloud/comments/k7b1of/extremely_slow_interface_nextcloud_snap/).

eganonoa avatar Dec 07 '20 13:12 eganonoa

Hello,

my Nextcloud instance is experiencing the same issue after version upgrade, although in my case it is enough to disable the Collabora Online - Built-in CODE Server app to solve the performance problem.

Environment: Ubuntu 18.04.5 LTS snap 20.0.2snap2

Thank you for your time and effort in looking into this matter. Should you need additional information please let me know.

calbav avatar Dec 07 '20 13:12 calbav

Confirmed, this makes the snap unusable. Nothing interesting in the logs during usage that doesn't relate to collabora. When trying to open a document I see this though. Not sure if it's helpful:

{"reqId":"FX5iHBU58fJlpkNjGQsY","level":3,"time":"2020-12-07T17:38:50+00:00","remoteAddr":"127.0.0.1","user":"admin","app":"richdocuments","method":"GET","url":"/index.php/apps/richdocuments/index?fileId=11&requesttoken=AEyf86%2BIbFplFbZnaNJpmAjUL4WrtY98go6EYe6v%2BNM%3D%3ANDjKqtXyKw8dW9QFX7gBt2nlH%2FTYhd447v7HL6jXteE%3D","message":{"Exception":"Exception","Message":"Could not find urlsrc in WOPI","Code":0,"Trace":[{"file":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/TokenManager.php","line":210,"function":"getUrlSrc","class":"OCA\\Richdocuments\\WOPI\\Parser","type":"->","args":["application/vnd.openxmlformats-officedocument.wordprocessingml.document"]},{"file":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/Controller/DocumentController.php","line":256,"function":"getToken","class":"OCA\\Richdocuments\\TokenManager","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":169,"function":"index","class":"OCA\\Richdocuments\\Controller\\DocumentController","type":"->","args":["*** sensitive parameter replaced ***",null]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":100,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/App.php","line":152,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/Route/Router.php","line":308,"function":"main","class":"OC\\AppFramework\\App","type":"::","args":["OCA\\Richdocuments\\Controller\\DocumentController","index",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"action":null,"_route":"richdocuments.document.index"}]},{"file":"/snap/nextcloud/24828/htdocs/lib/base.php","line":1008,"function":"match","class":"OC\\Route\\Router","type":"->","args":["/apps/richdocuments/index"]},{"file":"/snap/nextcloud/24828/htdocs/index.php","line":37,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/WOPI/Parser.php","Line":54,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0","version":"20.0.2.2"}

Note that I've been trying to open that document for about 5 minutes now, it just keeps spinning.

kyrofa avatar Dec 07 '20 17:12 kyrofa

Got a lot of these in my PHP error log:

[07-Dec-2020 17:38:41 UTC] PHP Warning:  file_get_contents(http://localhost:9982/hosting/capabilities): failed to open stream: HTTP request failed! in /var/snap/nextcloud/24828/nextcloud/extra-apps/richdocumentscode/proxy.php on line 208
[07-Dec-2020 17:38:43 UTC] PHP Warning:  file_get_contents(http://localhost:9982/hosting/capabilities): failed to open stream: HTTP request failed! in /var/snap/nextcloud/24828/nextcloud/extra-apps/richdocumentscode/proxy.php on line 208
[07-Dec-2020 17:38:45 UTC] PHP Warning:  file_get_contents(http://localhost:9982/hosting/capabilities): failed to open stream: HTTP request failed! in /var/snap/nextcloud/24828/nextcloud/extra-apps/richdocumentscode/proxy.php on line 208
[07-Dec-2020 17:38:47 UTC] PHP Warning:  file_get_contents(http://localhost:9982/hosting/capabilities): failed to open stream: Connection timed out in /var/snap/nextcloud/24828/nextcloud/extra-apps/richdocumentscode/proxy.php on line 208

And this type of thing in PHP-FPM error log:

[07-Dec-2020 09:40:44] WARNING: [pool www] child 17933 said into stderr: "File exists and file size matches, skipping"
[07-Dec-2020 09:40:44] WARNING: [pool www] child 17933 said into stderr: "Logging at warning level to file: /tmp/loolwsd.wQQ51O50TX/loolwsd.log"
[07-Dec-2020 09:40:44] WARNING: [pool www] child 15589 said into stderr: "Logging at warning level to file: /tmp/loolwsd.4qc5ViOkqZ/loolwsd.log"
[07-Dec-2020 09:40:44] WARNING: [pool www] child 17933 said into stderr: "Failed to listen on Server port(s) (9982-9982). Exiting."
[07-Dec-2020 09:40:45] WARNING: [pool www] child 15589 said into stderr: "Failed to listen on Server port(s) (9982-9982). Exiting."
[07-Dec-2020 09:40:48] WARNING: [pool www] child 17933 said into stderr: "/tmp/appimage_extracted_9bc52a5da15b4853d238ef00019d6a4d/opt/collaboraoffice6.4/share/autotext/es/standard.bau: ftw error: No such file or directory"
[07-Dec-2020 09:40:48] WARNING: [pool www] child 17933 said into stderr: "Failed to clean up cache directory"

kyrofa avatar Dec 07 '20 17:12 kyrofa

cc @timar @eszkadev Seems caused or related to richdocumentscode. Any idea?

juliushaertl avatar Dec 07 '20 18:12 juliushaertl

I found something on the nextcloud forum:

hpilkington gave the tip:

Confirmed sudo snap run nextcloud.occ app:disable richdocuments && sudo snap run nextcloud.occ app:disable richdocumentscore resolved my issues.

After having done that, the web interface turns fast again. I hope there will be a fix soon for collabora...

cedartop avatar Dec 07 '20 23:12 cedartop

Confirmed, this makes the snap unusable. Nothing interesting in the logs during usage that doesn't relate to collabora. When trying to open a document I see this though. Not sure if it's helpful:

{"reqId":"FX5iHBU58fJlpkNjGQsY","level":3,"time":"2020-12-07T17:38:50+00:00","remoteAddr":"127.0.0.1","user":"admin","app":"richdocuments","method":"GET","url":"/index.php/apps/richdocuments/index?fileId=11&requesttoken=AEyf86%2BIbFplFbZnaNJpmAjUL4WrtY98go6EYe6v%2BNM%3D%3ANDjKqtXyKw8dW9QFX7gBt2nlH%2FTYhd447v7HL6jXteE%3D","message":{"Exception":"Exception","Message":"Could not find urlsrc in WOPI","Code":0,"Trace":[{"file":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/TokenManager.php","line":210,"function":"getUrlSrc","class":"OCA\\Richdocuments\\WOPI\\Parser","type":"->","args":["application/vnd.openxmlformats-officedocument.wordprocessingml.document"]},{"file":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/Controller/DocumentController.php","line":256,"function":"getToken","class":"OCA\\Richdocuments\\TokenManager","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":169,"function":"index","class":"OCA\\Richdocuments\\Controller\\DocumentController","type":"->","args":["*** sensitive parameter replaced ***",null]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":100,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/AppFramework/App.php","line":152,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/snap/nextcloud/24828/htdocs/lib/private/Route/Router.php","line":308,"function":"main","class":"OC\\AppFramework\\App","type":"::","args":["OCA\\Richdocuments\\Controller\\DocumentController","index",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"action":null,"_route":"richdocuments.document.index"}]},{"file":"/snap/nextcloud/24828/htdocs/lib/base.php","line":1008,"function":"match","class":"OC\\Route\\Router","type":"->","args":["/apps/richdocuments/index"]},{"file":"/snap/nextcloud/24828/htdocs/index.php","line":37,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"/var/snap/nextcloud/24828/nextcloud/extra-apps/richdocuments/lib/WOPI/Parser.php","Line":54,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0","version":"20.0.2.2"}

Note that I've been trying to open that document for about 5 minutes now, it just keeps spinning.

@juliushaertl I noticed similar issue probably introduced by: https://github.com/nextcloud/richdocuments/commit/6b3d3f1 Request for "/index.php/apps/richdocuments/index" hangs in DocumentController.php because we need discovery while getting token and after mentioned patch there is no local cache which may be used so we are trying to connect to richdocumentscode which may be not started yet. But it should be fixed now in my last commits by increasing timeout when it is starting.

eszkadev avatar Dec 08 '20 08:12 eszkadev

Looked into the snap case with @timar. The findings so far (spoiler: the interesting part is at the end): /var/snap/nextcloud/24828/log/php-fpm_errors.log has relevant content.

[08-Dec-2020 19:56:50] NOTICE: fpm is running, pid 3042
[08-Dec-2020 19:56:50] NOTICE: ready to handle connections

So far so good.

[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "sh: 1: pidof: Permission denied"
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "sh: 1: disown: not found"

These aren't ideal, and might be worth investigating some other time (service may fail to kill the old version, and start the new one after an update), but isn't relevant now.

[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "dlopen(): error loading libfuse.so.2"
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "AppImages require FUSE to run. "
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "You might still be able to extract the contents of this AppImage "
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "if you run it with the --appimage-extract option. "
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "See https://github.com/AppImage/AppImageKit/wiki/FUSE "
[08-Dec-2020 22:08:46] WARNING: [pool www] child 20232 said into stderr: "for more information"

This is expected, there's no libfuse2 in snap, content of the AppImage is extracted to /tmp/snap.nextcloud/tmp/.

[08-Dec-2020 22:08:51] WARNING: [pool www] child 20232 said into stderr: "Logging at warning level to file: /tmp/loolwsd.2y1F0DbTKo/loolwsd.log"

loolwsd has started.

[08-Dec-2020 22:08:51] WARNING: [pool www] child 20232 said into stderr: "Error: loolforkit incorrect user-name: root - aborting"
[08-Dec-2020 22:08:51] WARNING: [pool www] child 20232 said into stderr: "Security: --disable-lool-user-checking failed, loolforkit has some capabilities set."

^ This indicates the problem. Another indicator: http://<snap host>/extra-apps/richdocumentscode/proxy.php?status stays at {"status":"starting"} instead of OK.

Only happens with version 6.4.202, while the previous 6.4.14 version is okay. https://github.com/CollaboraOnline/online/commit/264008618fd45c41e8b518d30cd56ba49dccf9e2 altered a check so !hasCorrectUID("loolforkit") is always called, and emits the first error message, and added another check that causes the app to exit with error after the second error message. I don't know if that's all there is to this problem, but looks like a good starting point. @kendy, @Ashod, what are your thoughts on that?

thebearon avatar Dec 08 '20 23:12 thebearon

@thebearon: I'd suggest removing the capabilities from the binaries when packaging this, that should make it working again.

kendy avatar Dec 09 '20 10:12 kendy

@juliushaertl: So we have investigated this more, and actually the problem is that the AppImage is run as root - who of course by definition has all the capabilities, so we refuse to start... Is it really necessary to run us as root?

kendy avatar Dec 09 '20 13:12 kendy

@juliushaertl: So we have investigated this more, and actually the problem is that the AppImage is run as root - who of course by definition has all the capabilities, so we refuse to start... Is it really necessary to run us as root?

Actually, probably @kyrofa can answer this question.

timar avatar Dec 09 '20 14:12 timar

The loolwsd command should be ran as the same user that the webserver is using since richdocuments code is just calling PHP exec(), so I assume that this is rather snap specific.

juliushaertl avatar Dec 09 '20 14:12 juliushaertl

Is it really necessary to run us as root?

Yes, as we've discussed before, daemons in snaps run as root, although note that root in snaps is still confined so there are no special capabilities granted.

kyrofa avatar Dec 09 '20 16:12 kyrofa

@juliushaertl: So we have investigated this more, and actually the problem is that the AppImage is run as root - who of course by definition has all the capabilities, so we refuse to start... Is it really necessary to run us as root?

Important to note that this issue isn't limited to snap, but has been reported by Docker image users also (though perhaps only those that installed everything as root?). Also note that one user on the Community Forum has said that upgrading to the edge release fixes the issue: https://help.nextcloud.com/t/nextcloud-20-0-2snap2-interface-incredibly-slow/100304/27. It's just one user, of course.

eganonoa avatar Dec 09 '20 17:12 eganonoa

@juliushaertl: So we have investigated this more, and actually the problem is that the AppImage is run as root - who of course by definition has all the capabilities, so we refuse to start... Is it really necessary to run us as root?

Important to note that this issue isn't limited to snap, but has been reported by Docker image users also (though perhaps only those that installed everything as root?). Also note that one user on the Community Forum has said that upgrading to the edge release fixes the issue: https://help.nextcloud.com/t/nextcloud-20-0-2snap2-interface-incredibly-slow/100304/27. It's just one user, of course.

I use Nextcloud, latest version & fresh install, in Docker with the latest image, which corresponds to the latest stable release. I can't use richdocuments & richdocumentscode because of how slow and how sluggish my instance become when these apps are installed.

LouisVallat avatar Dec 10 '20 08:12 LouisVallat

This also happens if nextcloud is installed on bare metal. It's not dependent on docker or snap.

I have a collabora container on another VM, but nextcloud hasn't connected to it yet.

Unfortunately in my case with nextcloud 20.04 the entire install errors out with richdocuments enabled so I can't configure it. With 20.02 I could at least load into the app after 45-60 seconds and once configured the issue went away.

That's not possible on 20.04.

SimplyCorbett avatar Dec 17 '20 14:12 SimplyCorbett

I really hope a fix for this is forthcoming soon. I definitely is a big showstopper for me.

aaylnx avatar Dec 22 '20 17:12 aaylnx

richdocumentcode 6.4.203 has been released. It fixes the issue, i.e. now we let loolforkit run as root.

timar avatar Dec 22 '20 23:12 timar

richdocumentcode 6.4.203 has been released. It fixes the issue, i.e. now we let loolforkit run as root.

I'm afraid I cannot confirm the fix. I upgraded to 6.4.203 and re-enabled the CODE server and Collabora Online and it has, unfortunately, knocked out my Nextcloud server (latest snap version) again. Disabling them brings performance right back.

eganonoa avatar Dec 23 '20 00:12 eganonoa

I can confirm, it still not working, logs:

xx.xx.xx.xx - - [23/Dec/2020:07:37:57 +0000] "GET /custom_apps/richdocumentscode/proxy.php?req=/hosting/capabilities HTTP/1.1" 200 628 "-" "Nextcloud Server Crawler" dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information

Logging at warning level to file: /tmp/loolwsd.k6vtOuTaTH/loolwsd.log Error: loolforkit incorrect user-name, other than 'lool' - aborting Security: --disable-lool-user-checking failed, loolforkit has some capabilities set.

nextcloud 20.0.4 (docker) Collabora Online 3.7.11 Collabora Online - Built-in CODE Server 6.4.203

szjozsef avatar Dec 23 '20 07:12 szjozsef

The fix seems to work on snap.

Although everything appears to be working a new notification appears (maybe unrelated?):

"Invalid private key for encryption app. Please update your private key password in your personal settings to recover access to your encrypted files."

Also many new errors are logged, mainly:

[encryption] Warning: OC\ServerNotAvailableException: Legacy cipher is no longer supported! at <>

  1. /snap/nextcloud/24940/htdocs/apps/encryption/lib/Crypto/Crypt.php line 405 OCA\Encryption\Crypto\Crypt->getLegacyCipher()
  2. /snap/nextcloud/24940/htdocs/apps/encryption/lib/KeyManager.php line 404 OCA\Encryption\Crypto\Crypt->decryptPrivateKey("*** sensitive parameters replaced ***")
  3. /snap/nextcloud/24940/htdocs/apps/encryption/lib/Hooks/UserHooks.php line 183 OCA\Encryption\KeyManager->init("*** sensitive parameter replaced ", " sensitive parameter replaced ***")
  4. /snap/nextcloud/24940/htdocs/lib/private/legacy/OC_Hook.php line 110 OCA\Encryption\Hooks\UserHooks->login("*** sensitive parameters replaced ***")
  5. /snap/nextcloud/24940/htdocs/lib/private/Server.php line 581 OC_Hook::emit("OC_User", "post_login", "*** sensitive parameter replaced ***")
  6. <> OC\Server->OC{closure}("*** sensitive parameters replaced ***")
  7. /snap/nextcloud/24940/htdocs/lib/private/Hooks/EmitterTrait.php line 101 call_user_func_array(Closure {}, ["*** sensitive ... "])
  8. /snap/nextcloud/24940/htdocs/lib/private/Hooks/PublicEmitter.php line 40 OC\Hooks\BasicEmitter->emit("\OC\User", "postRememberedLogin", ["*** sensitive ... "])
  9. /snap/nextcloud/24940/htdocs/lib/private/User/Session.php line 903 OC\Hooks\PublicEmitter->emit("\OC\User", "postRememberedLogin", ["*** sensitive ... "])
  10. /snap/nextcloud/24940/htdocs/lib/base.php line 1058 OC\User\Session->loginWithCookie("*** sensitive parameters replaced ***")
  11. /snap/nextcloud/24940/htdocs/lib/base.php line 997 OC::handleLogin(OC\AppFramework\Http\Request {})
  12. /snap/nextcloud/24940/htdocs/index.php line 37 OC::handleRequest()

calbav avatar Dec 23 '20 09:12 calbav

I tested this update this morning, using Docker, and it still acts the same : installing richdocuments & richdocumentscode result is veeerry slow instance, and it goes back to normal after uninstalling these apps.

LouisVallat avatar Dec 23 '20 10:12 LouisVallat

The fix seems to work on snap.

Although everything appears to be working a new notification appears (maybe unrelated?):

"Invalid private key for encryption app. Please update your private key password in your personal settings to recover access to your encrypted files."

Also many new errors are logged, mainly:

[encryption] Warning: OC\ServerNotAvailableException: Legacy cipher is no longer supported! at <>

  1. /snap/nextcloud/24940/htdocs/apps/encryption/lib/Crypto/Crypt.php line 405 OCA\Encryption\Crypto\Crypt->getLegacyCipher()
  2. /snap/nextcloud/24940/htdocs/apps/encryption/lib/KeyManager.php line 404 OCA\Encryption\Crypto\Crypt->decryptPrivateKey("*** sensitive parameters replaced ***")
  3. /snap/nextcloud/24940/htdocs/apps/encryption/lib/Hooks/UserHooks.php line 183 OCA\Encryption\KeyManager->init("*** sensitive parameter replaced ", " sensitive parameter replaced ***")
  4. /snap/nextcloud/24940/htdocs/lib/private/legacy/OC_Hook.php line 110 OCA\Encryption\Hooks\UserHooks->login("*** sensitive parameters replaced ***")
  5. /snap/nextcloud/24940/htdocs/lib/private/Server.php line 581 OC_Hook::emit("OC_User", "post_login", "*** sensitive parameter replaced ***")
  6. <> OC\Server->OC{closure}("*** sensitive parameters replaced ***")
  7. /snap/nextcloud/24940/htdocs/lib/private/Hooks/EmitterTrait.php line 101 call_user_func_array(Closure {}, ["*** sensitive ... "])
  8. /snap/nextcloud/24940/htdocs/lib/private/Hooks/PublicEmitter.php line 40 OC\Hooks\BasicEmitter->emit("\OC\User", "postRememberedLogin", ["*** sensitive ... "])
  9. /snap/nextcloud/24940/htdocs/lib/private/User/Session.php line 903 OC\Hooks\PublicEmitter->emit("\OC\User", "postRememberedLogin", ["*** sensitive ... "])
  10. /snap/nextcloud/24940/htdocs/lib/base.php line 1058 OC\User\Session->loginWithCookie("*** sensitive parameters replaced ***")
  11. /snap/nextcloud/24940/htdocs/lib/base.php line 997 OC::handleLogin(OC\AppFramework\Http\Request {})
  12. /snap/nextcloud/24940/htdocs/index.php line 37 OC::handleRequest()

Can I ask, which version of snap are you on. I'm on the latest stable version and re-enabling the CODE server and Collabora Online after updating the app had no positive impact at all, but just brought back the same problem.

eganonoa avatar Dec 23 '20 14:12 eganonoa

Can I ask, which version of snap are you on. I'm on the latest stable version and re-enabling the CODE server and Collabora Online after updating the app had no positive impact at all, but just brought back the same problem.

Hi, sure. Here is the output from snap list:

Name Version Rev Tracking Publisher Notes nextcloud 20.0.3snap1 24940 latest/stable nextcloud* -

calbav avatar Dec 23 '20 14:12 calbav

Can you test on 20.0.4 instead of 20.0.3 @calbav

SimplyCorbett avatar Dec 23 '20 16:12 SimplyCorbett

@SimplyCorbett gladly, can you tell me how?

Would that be:

$ sudo snap refresh nextcloud --channel=<what channel? latest/beta?>

calbav avatar Dec 23 '20 17:12 calbav

@calbav sudo snap refresh --beta nextcloud will get you on 20.0.4. It will be released to stable shortly.

kyrofa avatar Dec 23 '20 23:12 kyrofa

I can confirm, it still not working, logs:

xx.xx.xx.xx - - [23/Dec/2020:07:37:57 +0000] "GET /custom_apps/richdocumentscode/proxy.php?req=/hosting/capabilities HTTP/1.1" 200 628 "-" "Nextcloud Server Crawler" dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information

Logging at warning level to file: /tmp/loolwsd.k6vtOuTaTH/loolwsd.log Error: loolforkit incorrect user-name, other than 'lool' - aborting Security: --disable-lool-user-checking failed, loolforkit has some capabilities set.

nextcloud 20.0.4 (docker) Collabora Online 3.7.11 Collabora Online - Built-in CODE Server 6.4.203

Just the same as all three! Gets fixed as soon as I disable Collabora Online 3.7.11.

avimanyu786 avatar Dec 24 '20 07:12 avimanyu786

Thanks @kyrofa,

I tested 20.0.4snap1 (25275 latest/beta) and the problem persists. Again it is enough to disable the Collabora Online - Built-in CODE Server app to regain performance.

Unfortunately upon reverting to 20.0.3snap1 (24940 latest/stable) the issue revived. This time it wasn't enough to disable the Collabora Online - Built-in CODE Server app to regain the performance, I also had to disable the Collabora Online app (as for everyone else using snap in the thread) to regain the performance.

calbav avatar Dec 24 '20 08:12 calbav

I tested NC 20.0.4 snap stable today and there is no progress. Collabora Online 3.7.11 - installed Collabora Online - Built-in CODE Server 6.4.203 installed Still must be disabled to have fast access to server files. If Collabora Online is enabled - still a problem persists.

vawaver avatar Dec 25 '20 13:12 vawaver

I have the same problem on a Gentoo installation: apache + php-fpm + postgres, Nextcloud 20.0.4. Nextcloud was installed via ebuild so the source lives in the server's main /var/www. Therefore, this problem is not limited to snap or docker installations.

I have to disable the built-in CODE server, otherwise Nextcloud is unbearably slow. This doesn't affect any other apps in the server (php or not), and there's no unusual CPU load, memory consumption, or disk activity. It's just that all Nextcloud pages take forever to load. I don't know when it started - I used to work with it without problems some time ago, but now I've had this problem for at least a month.

sliwowitz avatar Dec 25 '20 15:12 sliwowitz