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

Configuration property "bottleneck.getChanges" is not defined #2082

Closed
1 task done
sabrinamile opened this issue Feb 1, 2023 · 5 comments
Closed
1 task done

Configuration property "bottleneck.getChanges" is not defined #2082

sabrinamile opened this issue Feb 1, 2023 · 5 comments
Labels
invalid Issues that are invalid

Comments

@sabrinamile
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

Linux (DEB package)

Version information

Documentserver 7.3.0-184~stretch

Expected Behavior

Docservice should be running after upgrade onlyoffice-documentserver-ee:amd64 7.2.2-56 -> 7.3.0-184~stretch

Actual Behavior

Documentserver/Docservice is not starting after an upgrade: onlyoffice-documentserver-ee:amd64 7.2.2-56 -> 7.3.0-184~stretch

Error in Logfiles:
supervisorctl status:
ds:converter RUNNING pid 8360, uptime 0:21:18
ds:docservice FATAL Exited too quickly (process log may have details)
ds:example RUNNING pid 8348, uptime 0:21:18
ds:metrics RUNNING pid 8347, uptime 0:21:18

In /var/log/onlyoffice/documentserver/docservice/err.log we found this error:
Error: Configuration property "bottleneck.getChanges" is not defined
at Config.get (/snapshot/server/build/server/DocService/node_modules/config/lib/config.js:203:11)
at Object. (/snapshot/server/build/server/DocService/sources/baseConnector.js)
at Module._compile (pkg/prelude/bootstrap.js:1930:22)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at Module.require (pkg/prelude/bootstrap.js:1855:31)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (/snapshot/server/build/server/DocService/sources/DocsCoServer.js)

Reproduction Steps

upgrade onlyoffice-documentserver-ee:amd64 7.2.2-56 -> 7.3.0-184~stretch

Additional information

No response

@Akrobs
Copy link

Akrobs commented Feb 1, 2023

Same problem on rpm package.

@sabrinamile
Copy link
Author

There was a conflict between the old and the new config-file. The unattended installation at night was not fully finished. Trying the update once again solved the issue for us.

@nahoj
Copy link

nahoj commented May 26, 2023

I had the same error upgrading from 7.1.0~ynh1 to 7.3.3~ynh1 on YunoHost, resulting in high CPU load as in #1472 which probably crashed my server afterwards (though no definitive evidence).

I fixed in a way inspired by #1472, namely:

cd /etc/onlyoffice/documentserver
cp default.json.dpkg-dist default.json
supervisorctl restart all

Update: found cause in YNH upgrade log:

2023-05-26 15:07:50,346: WARNING - Configuration file '/etc/onlyoffice/documentserver/default.json'
2023-05-26 15:07:50,347: WARNING -  ==> Modified (by you or by a script) since installation.
2023-05-26 15:07:50,348: WARNING -  ==> Package distributor has shipped an updated version.
2023-05-26 15:07:50,349: WARNING -  ==> Keeping old config file as default.

(though I'm not sure what the aforementioned changes were or came from).

@igwyd
Copy link
Member

igwyd commented Aug 31, 2023

Hello @sabrinamile, you're right, /etc/onlyoffice/documentserver/default.json should be updated, all custom changes must be made to /etc/onlyoffice/documentserver/local.json.

@Rita-Bubnova Rita-Bubnova added the invalid Issues that are invalid label Aug 31, 2023
@Rita-Bubnova
Copy link
Member

I close this issue. Feel free to comment or reopen it if you got further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Issues that are invalid
Projects
None yet
Development

No branches or pull requests

5 participants