Nextcloud 19.03 Community Document Server not save

[FindschNET1]

the Community Document Server Version 0.1.7 with ONLYOFFICE 6.0.0
dont save files and shows after reopen the onw User is working togehter with itself

[ferdiga]

Hi, this is a high priority issue.
https://nextcloud.com/onlyoffice/
suggest a production ready solution.
Data loss is a no go (I just lost almost a days work)

perhaps the following description helps
I opened a xlsx in on window and the same xlsx in another window on the same computer.
changes in one window have been reflected correctly in the other window.
So I was convinced that data was written to the server.
I even clicked "file save" several times, because I wanted to be on the safe side.
Nevertheless it wasn't.
After closing all windows and reopening the file all work was lost.
I also noted that the modification date was not changed.

I disabled ONLYOFFICE for now and enabled Collabora (which is much slower, lacks the freeze rows and columns feature, making sheets hard to use , supposedly solved in CODE 6.0 and the font resolution is not so good.). But at least no data loss.

All in all a very sub optimal solution.

[ferdiga]

see here
#100

[FindschNET1]

THX for your input.
you're right all in all a very sub optimal solution.
i think it must be work... in need a solution!

[mhier]

As stated in #100, it works fine when not using the document server app but instead run the document server in a Docker container. The effort do to this is not very big.

Still, being able to use Onlyoffice with just a few clicks in Nextcloud (at least on small-scale installations) is quite neat. It has worked perfectly for me until the last update. If I remember correctly (cannot check any more, as I have switched now to the Docker version), the document server version provided by this app moved to version 6.0.0. This is strange, as the latest version is only 5.6.5. Maybe this is the actual root cause for the problem? It looks I have mixed up the document server version with the integration app version... Sorry for the confusion!

[ferdiga]

I didn't have much time, so I installed the docker document server and its running on port 8006,
I am lost what to do next.

• probably uninstall the nextcloud document server to be able to specify the new docker version ?
  I do not get the 3 options in onlyoffice app, I can remember it is the option 2 ?
• how make the docker server available to next cloud?
  sorry for the stupid questions

[ferdiga]

can I drop these table to get a fresh install ?

MariaDB [owncloud]> show tables like "%documentserver%";
+---------------------------------------+
| Tables_in_owncloud (%documentserver%) |
+---------------------------------------+
| oc_documentserver_changes             |
| oc_documentserver_ipc                 |
| oc_documentserver_locks               |
| oc_documentserver_sess                |
+---------------------------------------+
4 rows in set (0.001 sec)

[mhier]

I didn't have much time, so I installed the docker document server and its running on port 8006,
I am lost what to do next.

* probably uninstall the nextcloud document server to be able to specify the new docker version ?
  I do not get the 3 options in onlyoffice app,  I can remember it is the option 2  ?

You can even keep the document server app in Nextcloud, it would simply be unused.

* how make the docker server available to next cloud?

In Nextcloud administrator settings, there is a ONLYOFFICE section. You have to put the document server address and the secret key (which you probably specified when launching the Docker container) in there.

As far as I understand, the document server needs to be reachable both by the Nextcloud instance as well as by the user's Browser. Hence if your Nextcloud instance is reachable from the internet, the document server should be reachable as well. It is also strongly recommended to use (only!) https for this, otherwise your documents are probably shipped in plain text through the internet. This is usually realised with a reverse proxy in Apache resp. nginx or whatever web server you are using.

Since this is not a support forum, maybe you should try to find the remaining information somewhere else (it's easily found in the big search engines...)

[ibnpetr]

As far as I understand, the document server needs to be reachable both by the Nextcloud instance as well as by the user's Browser. Hence if your Nextcloud instance is reachable from the internet, the document server should be reachable as well.

one more thing:
Nextcloud also should be reachable by the document server (As soon as you close your editing session, ONLYOFFICE server will inform your NC instance that there is a new version of the document available in the document server's cache and it (NC) should download it)

[mhl66]

Does not save. Period. Ridiculous.

[ferdiga]

Please can anyone advice how to purge the only-office installation
probably some old data prohibit the correct functioning.
I see tables associated with the community server and I think there was a section in ONLY Office to connect to an external onlyoffice (docker) service, which does nit show up any more.

[Fiodin]

I now switched to a Docker Instance of OnlyOffice. It really works fine and I wrote a little How-To without a reverse proxy because it was easier for me and it is as secure as it is with it: #100 (comment)

[mhl66]

NOTHING at all happened in the current versions (OnlyOffice 6.0.2 and Community Document Server 0.1.8).
This is really a show stopper for Nextcloud as a would-be office solution. Any comments at all???

[pongraczi]

• NC 19.0.4
• PHP 7.4
• Community Document Server 1.8
• Onlyoffice 6.0.2

Use case:

• Shared excel sheet between users
• Only web clients involved to accessing the file
• Onlyoffice setting in NC:
  • Keep intermediate versions when editing (checked, aka force write)
• Onlyoffice editor settings under Advanced config:
  • Automatic save enabled (checked)
  • Cooperative editing set to quick
  • Always save to the server (otherwise save on close)
  • Force save to the server supposed to work with these settings
• Cronjobs
  • NC cronjob at */5 (cron.php)
  • occ document_flush */2
  • occ email:send */2
• Saving/closing seems write out the file when one user edits and click on Save (timestamp seems fine, email notification sent almost immediately)

Steps to reproduce and observations

• User1 opened, edited, saved, closed (by clicking on this
  
• User1 reopened the file, added new record (several fields) save, leave
• User2 logs in from other location/browser, so, two NC session opened
• User2 opens the file in the browser: some fields are missing from the latest edition made by User1
• User2 saves, leaves
• User1 opens the file, it is definitely missing, same
  
• User1 added records , saves, leaves
• User2 opens the file, records exists as expected, added new record, save, leave (Observation: the number of users on the top right shows 2, even definitely only User2 edited the document)
• There are no running Onlyoffice in browser, all settings supposed to force write to server, timestamp and notification mentioned this, so, it should be no locks or sessions in the database (oc_documentserver_locks and oc_documentserver_sess)
• I found 2 existing sessions in the database and several locks
  
  
• User1 opens, modifies, saves, leaves
• User2 opened, modified, keep onlyoffice open
• The database shows 3 existing sessions, even there only one active (running) Onlyoffice in browser
  

My conclusion

Big Fat Warning
* I do not know and I did not check how the session and lock mechanism are working in document server.
* Cronjob flushes every 2 minutes the documentserver.

Quick Facts
* There were several locks and *ghost* sessions inside the database, while there was no active (running) Onlyoffice instances. I saw it for several minutes after all onlyoffice instances are closed.
* Every saves and leaves from Onlyoffice supposed to trigger force save to server and as I saw, it definitely happened (maybe one time, when there were several locks and three sessions, there was a small delay, I am not sure, maybe 1 minute).

• I suppose the correct behaviour should be that, when a user closes/leaves the Onlyoffice app, sessions should be wiped out immediately without delay.
• Locks are also interesting, I guess there should be no lock after saving, so, seeing several locks after everybody closed onlyoffice for several minutes should be an indicator of misbehaving.
• My bet the problem is lying around this lock and session anomaly.

My request

Please share my report (this one) anywhere where you think it can help developers/others to fix this issue or give more data/test results to be able to narrow down the issue.

Let's fix this F rated issue. Thank you.

Edited

• User2 is a Guest user, but the same problem exists in other use cases.
• When User2 tried to restore an earlier version before the big test started, I got an exception into nextcloud.log (as I remember, maybe there is no connection to the base problem, just for the record)

{"reqId":"UG8jc5BXsonrcWgjEYNq","level":3,"time":"2020-10-16T21:50:00+02:00","remoteAddr":"XX.104.XX.27","user":"[email protected]","app":"onlyoffice","method":"MOVE","url":"/remote.php/dav/versions/[email protected]/versions/12630/1602876244","message":{"Exception":"OCP\\Files\\NotFoundException","Message":"Important_document.xlsx not found while trying to get owner",

[pongraczi]

Today I just installed a standalone document server into an LXC container and set up with Nextcloud.
I am testing right now and I have to tell, now it seems working as expected.
I enter a lot of texts with User1 and User2 and there is no data loss, so far so good.
Still testing, but much more promising than the bundled community document server.

[ferdiga]

I have installed Onlyoffice docker 6.0.0.105 and this seems to "work" so far. Changes are written to the Nextcloud storage and synced to the client.

I followed the guidance for "Force Saving" here:
https://api.onlyoffice.com/editors/save

{
    "services": {
        "CoAuthoring": {
            "autoAssembly": {
                "enable": true,
                "interval": "2m",
                "step": "1m" 
            }
        }
    }
}

Pls let me know your thoughts

[Fiodin]

You dont need the "Force Savong" with the Docker-Image. With it it is saved automatically.

[mhl66]

Summary: Docker works, this here (Community Document Server) DOES NOT. Anyone there?

[gcommit]

got the same problem and tried almost every solution out there.

ONLYOFFICE Document Server is not equal to Community Docusment Server used for ONLYOFFICE by Nextcloud ...

[github-actions]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 60 days. Thank you for your contribution!

Retaking repo management include inheritance of old, not treated, and probablty obsolete issues, this is why it was decided to mark issues as stale.

[github-actions]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.