-
Notifications
You must be signed in to change notification settings - Fork 19
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
Onlyoffice fails after upgrade, config file kept back [Solved] #108
Comments
ping @nahoj in case you want to add precisions... |
encountered this issue during upgrade between the 2 most recent ynh package versions on 25.10.23. default.json had missing config options for |
I had the same problem from 7.3 to 7.5, only this time the new config file was nowhere to be found 😮 I had to fetch it from upstream and paste it in @ericgaspar Are you sure of your testing ? I'm still very grateful for the work you put in (i'm no packager myself...), but if you need help or 2nd looks when testing, feel free to ping me. On second thought, the same upgrade went well on another server, so it must be a "snowflake"-effect (one of a kind server, or 2 of a kind with @czen ...). If you need logs, just tell me 😺 |
Same issue with the latest update (8.1.1~ynh1), using the .dpkg-dist worked fine, thanks for the tips! |
Describe the bug
Doc-service fails after a successful upgrade. The supervisord service keeps running, but doc edition is disabled. Only webpages are visible on the onlyoffice domain, not the editor.
In Nextcloud, the app settings gives a 503 error for the document-service url.
Context
Steps to reproduce
Upgrade the app via CLI, then try to edit a doc drom Nextcloud.
Expected behavior
App should work the same as before.
Logs
upgrade : https://paste.yunohost.org/raw/enolizibag
Error from DS-docservice ( in
/var/log/onlyoffice/documentserver/docservice/err.log
) :✔️ Solution
As pointed in this issue, it turns out that yunohost does not apply the last config file, because the default one has been modified (I don' remember doing it, maybe it's ynh fault ?).
So I went in the CLI, and replaced the default.json with the default.json.dpkg-dist that had been kept back
A simple
service ds-docservice restart
made it work afterwards.So I guess a warning message would be needed when upgrading. (or if it's there I missed it, so make it more visible, stopping the process maybe)
I'll leave you to fix this, dear maintainers 😉
The text was updated successfully, but these errors were encountered: