-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes not saved back to Nextcloud #931
Comments
Same here with NC 27.6.1 on Ubuntu 20.04.6 LTS with:
On other 28.0.1 instances I saw ONLYOFFICE 9.0.0 available which is not offered on my small instance. In my test I created a new spreadsheet, edited some cells and then download it. |
@lheckemann Status 3 is a response from the editor that means the file is corrupted. It's difficult to say what exactly happened based on the record you sent, since it's a response to a saving request. Could you post more records from the logs for the same file? @florian-obradovic The Community Document Server app is developed and maintained by Nextcloud. This is the repository for the ONLYOFFICE integration app. Please post the issue in the relevant repo: https://github.com/nextcloud/documentserver_community |
@SergeyKorneyev thanks for your response! There are no successful save requests; the documentserver log is filled with errors that look pretty much the same as the one above, and likewise but with status 7 when requesting a save explicitly via the menu. I just tried creating a new spreadsheet, opening it, writing some text into it, then saving it. These are the only logs that come out:
The only other thing I've found in the log is right at startup:
|
In that case, the errors would probably be in the Converter logs. If the issue is easily reproducible, I would also suggest enabling some additional diagnostics:
After that, reproduce the issue and take a look at the Converter logs. If you want us to analyze this further, you could also send us the contents of the "error" folder. |
I just noticed that x2t processes are constantly coredumping on SIGILL:
Is doctrenderer.so maybe built assuming CPU features that my machine doesn't have? cpuinfo:
|
I'm not seeing any files popping up in the location you mentioned even after making the config changes you suggested. |
The system records on x2t don't tell us much, I'm afraid, and it's strange that the error folder is empty. |
after Update to 28.0.3 ONLYOFFICE (internal) became the default App for documents (docx, xlsx, ...), although I had collabora configured
|
Sorry, turns out I was getting the config wrong. Here's an example error dir! The problem does occur with text documents as well as spreadsheets. |
I have the same error, including the core dump. It looks (besides the addresses) the same. I am Running nextcloud 28.0.4 and onlyoffice 8.0.1.31 (deb download). I am happy helping with debugging. |
I've self-compiled the libdocrenderer.so and got some functions names in addition to the function pointers.
|
Regarding types:
|
@lheckemann @MarcelCoding @SergeyKorneyev Has any further progress been made in triaging this issue? My current 'workaround' on my personal cloud is to open the document, download the document using the Onlyoffice interface and re-upload it to my Nextcloud in order to save the changes, but this is quite tedious. If more information is required in order to triage, please let me know. |
I have given up. I am just using the docker container again... |
Any workarounds for this issue? |
I've now deployed it using podman: |
If nextcloud is down, or the changes can otherwise not be saved back to nextcloud (e.g. because of [1]), the onlyoffice database contains _all the user data_ and should absolutely not be dropped on startup! [1]: ONLYOFFICE/onlyoffice-nextcloud#931
Hello everybody, i'm just encountering a weird bug that might be related to the one described here. When i test the sharing link (in private mode), OnlyOffice displays a previous unfinished version of my spreadsheet. I don't manage the server hosting OnlyOffice but i can ask for logs, just tell me. |
I'm also seeing this (also on NixOS). This might be the same issue as ONLYOFFICE/DocumentServer#2450 |
sorry to say - it's a drama that this is not solved and at the same time offered as a "production" tool without mentioning this issue. |
I've added a warning note to https://wiki.nixos.org/wiki/Nextcloud |
I did some more digging: x2t invokes some javascript code using v8. That (I think the invocation of
It looks like the coredump is just v8 aborting due to this error. So I guess the next step here is to rebuild |
OK, after deciphering it turns out that crash was a red herring: it was due to me not pointing at With that my built-from-source with-debugging x2t (NixOS/nixpkgs#338794) actually makes onlyoffice work fine! Somewhat unsatisfying that it doesn't explain the original problem, but this way of packaging has many advantages over using everything from the binary .deb, so this might be an improvement worth considering anyway. |
I'm running an onlyoffice document server in conjunction with the Nextcloud onlyoffice app. This mostly works fine, but the document server seems to be having some difficulty saving documents back to Nextcloud -- so when opened in onlyoffice, the current version of the document is shown, but downloading from nextcloud results in an outdated version of the document.
On save attempts, nextcloud logs:
And the docserver logs:
Why might this be happening?
The text was updated successfully, but these errors were encountered: