Skip to content
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

After the callback function is invoked, the returned JSON has a status of 3 and there is no corresponding URL. #2728

Open
1 task done
qq997540362 opened this issue May 11, 2024 · 4 comments
Labels
fixed-release Issues that fixed on next release, waiting to be released

Comments

@qq997540362
Copy link

This issue is unique.

  • I have used the search tool and did not find an issue describing my bug.

Operating System of DocumentServer

Docker

Version information

20.10.17 and 20.10.14

Expected Behavior

Yesterday while troubleshooting the logs, I found that OnlyOffice discovered that whenever I opened and edited a .doc or .docx file and saved it, the callback function always received a status of 3. I checked the out.log file located under \var\www\onlyoffice\log\onlyoffice\documentserver\converter
out_stdout
I also checked the logs in other paths \var\www\log\onlyoffice\documentserver\metrics, which provided the following information:
2024051101
I encountered such an error in the logs under the path \var\www\log\onlyoffice\documentserver\docservice
2024051102

How can I resolve this issue?

Actual Behavior

After I discovered this issue yesterday, I tried to replicate it in my test environment but without success. Both my production and test environments are using the same CentOS 7, with Docker versions 20.10.14 for production and 20.10.17 for testing. The OnlyOffice Document Server used in both environments is onlyoffice/documentserver:7.0.

Reproduction Steps

No response

Additional information

No response

@igwyd
Copy link
Member

igwyd commented May 14, 2024

Hello @qq997540362, this error is related to the conversion of the old format doc inside docimentserver, we already fix it at ONLYOFFICE/core@04480bb, and will be released in the next major release.

@Rita-Bubnova Rita-Bubnova added the fixed-release Issues that fixed on next release, waiting to be released label May 14, 2024
@qq997540362
Copy link
Author

Thank you for your response! Has this bug been fixed in version 8.0 so far, or do we need to wait until version 8.5 for the fix?

@igwyd
Copy link
Member

igwyd commented May 14, 2024

Number will probably be 8.1.

@qq997540362
Copy link
Author

Thank you for your answer and hope you have a smooth day at work today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-release Issues that fixed on next release, waiting to be released
Projects
None yet
Development

No branches or pull requests

3 participants