I just installed the archlinux aur packet for CODE. It works mostly as expected, but I am seeing some messages from coolwsd that probably should not happen.
This warning shows up frequently. I do wonder why this is. I installed and ran the server without jailing first but was tired of the warnings that come with this method. So I switched on the jailing and ended up with these failing chmods.
What can be wrong in my installation causing this?
Second:
coolwsd[11700]: wsd-11700-11731 2024-02-26 20:37:49.856498 +0100 [ websrv_poll ] ERR FileServerRequestHandler: File not found: Invalid URI request: [/browser/619c3e6/images/dark/vereign.png].| wsd/FileServer.cpp:748
I frequently see file not found errors. I learned that the number inside the path is a version hash that is in fact dropped and replaced by "distââ most of the time. Still it looks like something is missing here.
Third:
Feb 26 20:36:59 coolwsd[11700]: [0] 'lool'
Feb 26 20:36:59 coolwsd[11700]: [1] 'convert-to'
Feb 26 20:36:59 coolwsd[11700]: [2] 'png'
Feb 26 20:36:59 coolwsd[11700]: full URI: //lool/convert-to/png| wsd/COOLWSD.cpp:4432
Feb 26 20:37:27 coolwsd[11700]: wsd-11700-11731 2024-02-26 20:37:27.759810 +0100 [ websrv_poll ] ERR #18: Unknown resource: //lool/convert-to/png , host: HOST:9980, path: 3
I doubt there should be a path //lool/convert-to/png. I reads like something not initialised, but what?
Fourth:
coolwsd[899]: wsd-00899-00928 2024-02-26 02:32:55.020061 +0100 [ websrv_poll ] WRN Client - server version mismatch, disabling browser cache. Expected: 619c3e6; Actual URI path with version hash: /browser/824988663f/cool.html| wsd/FileServer.cpp:529
This one is really a bit of a problem. How can I make nextcloud and collabora install a matching version? I mean the nextcloud app store does not give you a lot possibilities for alternative versionsâŚ
Thanks you for reading. Hopefully someone can provide hints how to solve these.
Regards
In the meantime I read some threads about the jail warning and move this question to future versions. maybe it is already fixed there.
The file-not-found as all other logs show up on the collabora server in its journal. There is nothing to complain about shown in the app or the admin web pages. That looks pretty ok.
Maybe all of my logged problems would be gone if I installed an app and collabora with matching versions. How do I do that? Is there something like a combined doc where both is elaborated a bit?
Hm, some antispam bot ate my reply post âŚ
And there is no reference for me left to access the data it contained.
Sorry Mike, I answered your questions but it is all gone âŚ
(Dang Akismetâs anti-spam seems to initially gobble up posts when people âpost too quicklyâ. I suspect it happens when people copy/paste info in, so your whole post shows up in âless than a few secondsâ = MUST BE A BOT!)
Hmmm, that page leads me to a 404. I think this might be the link you meant?
thank you for freeing my answer
Sorry for posting the git link instead of the weblink from aur.
Generally we do not want any docker stuff. We really like to know what is going on, whereas docker aims at people mostly interested in ââpainless workingââ installation
I do believe there is a real problem with the version matching or conflict between nextcloud and collabora. Is there some list where one can find which versions match (or even work together)? Because there is no way of knowing regarding only the versions. Since yesterday we have richdocuments 8.2.5. But how does that match to coolwsd 23.05.9.1? How can we know that at all? Really, some table is needed, if not there currently.
Another issue I want to draw your attention to is the host aliasing. The xml config allows you to alias hostnames to a (means one) cloud instance. At least that is how I would understand alias. But we found out that this is not the case.
If you have cloud1.nc.com and cloud2.nc2.com aliased in the config and assume that both are true aliases in terms of web and identical user base. Then you will be at least astonished when two users in these clouds try to share a document with collabora and do not see each other in the top row and of course do not see each others edits.
The alias seems to work in terms of access, but it does not work in terms of collaboration, which seems strange, not?
It would be helpful if you could at least confirm this so we at least know that we made no other mistakes.
From what I understand, the versions of Nextcloud/richdocuments/Collabora can be interchangeable⌠because they each cover different âlayersâ.
For example:
Nextcloud
= A server where users can login / save+move files around.
Collabora Online
= The actual document creation/loading/editing.
richdocuments
= How Nextcloud integrates+communicates with Collabora.
For example:
Syncing usernames+cursor locations.
Sharing Nextcloudâs file permissions.
Some people can read-only. Some can fully edit. Some canât open at all.
Easily âShareâ URLs to your Nextcloud document.
So you can upgrade Nextcloud, or upgrade Collabora, and as long as they are still speaking the same API/language, they can still communicate with each other.
(Of course, newer versions will probably fix many bugs and be better than old! :P)
lol. Well yeah, youâd get a painless and working install.
[âŚ] When two users join to the same document but doesnât see each other edits or saved content is lost or overwritten by other users working on the same file.
That means the HTTP requests related to the same file are not directed to the same Collabora Online node.
Collabora/Nextcloud integration:
we are on Linux here, APIs are like dust in the wind (sometimes). So if there is a magic way that the integration works no matter which version and API, then I would like to read that in some documentation, probably at the very beginning
Host aliasing:
Yes I read the doc you are pointing to, it explains exactly what I would have expected. But unfortunately the inverse case of a single host and multiple aliases Is not mentioned in detail in the form that this does really work. Itâs only implicit in the way that 2 hosts with separate aliases work side by side, meaning not collaborating.
My config is exactly as the example says, only with one host.
I am not talking about a loadbalancing collabora at this point.
Just one simple server.