Document server ERROR

[debopam]

We are working with the document server for last few weeks; however all of a sudden it stopped and when we are trying to restart it shows the following error.

Error: Configuration property "services.CoAuthoring.expire.pemStdTTL"
is not defined
at Config.get
(/var/www/onlyoffice/documentserver/server/Common/node_modules/config/lib/c
onfig.js:180:11)
at Object.<anonymous>
(/var/www/onlyoffice/documentserver/server/Common/sources/utils.js:35:30)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous>
(/var/www/onlyoffice/documentserver/server/Common/sources/license.js:16:15)

Searched in the forums for possible solutions but not able to identify the exact problem.

Please help!

[Maxim]

Hello debopam!
1 Please specify what installation of Onlyoffice do you use? Community or Enterprise Edition, maybe Integration?
2 There is a problem connected with config file. You should check is there such file or not

/etc/onlyoffice/documentserver/default.json

3 if there is no such file or it's damaged you can just reinstall Onlyoffce if you use Onlyoffice for Docker.

[jtinsley]

Hi,

I'm Debopam's sysadmin.
1. Using Community, just the documentserver component.
2. File exists, and appears to be valid, not corrupted
3. We're not using docker, using the debian packaged version installed on Debian Jessie.

[Maxim]

Hello jtinsley!
Is there any chance to get ssh access to test your server?

[jtinsley]

Sorry, it's inside a private LAN that we can't give access to. I can run any commands you'd like, or gather any information you'd like for you?

[Maxim]

Hello jtinsley!
Clarify please how do you reboot server? Maybe you do not use supervisor for rebooting?

[jtinsley]

Hi,

The server's a standard debian Jessie, we've installed DocumentServer from the repository? Only the document server, it's being interfaced with via custom UIs using the SDK. 'Restarting' the server is literally only possible from supervisord, using the supervisorctl tool.

root@office:~# supervisorctl status
onlyoffice-documentserver:converter FATAL Exited too quickly (process log may have details)
onlyoffice-documentserver:docservice FATAL Exited too quickly (process log may have details)
onlyoffice-documentserver:gc FATAL Exited too quickly (process log may have details)
onlyoffice-documentserver:metrics RUNNING pid 21517, uptime 2 days, 4:23:05
onlyoffice-documentserver:spellchecker RUNNING pid 28963, uptime 3 days, 3:15:22

root@oss-live-office:~# supervisorctl restart all
FAILED: attempted to kill converter with sig SIGTERM but it wasn't running
metrics: stopped
spellchecker: stopped
gc: stopped
docservice: stopped
metrics: started
spellchecker: started
gc: ERROR (abnormal termination)
docservice: ERROR (abnormal termination)
converter: started

Error message is from log in /var/log/onlyoffice/documentserver/docservice/out.log



Is "pemStdTTL" a new variable? I can see at some point document server has been updated, so there's two default.json config files;
/etc/onlyoffice/documentserver/default.json
/etc/onlyoffice/documentserver/default.json.dpkg-dist

Should we overwrite the existing default.json with .dpkg-dist? Will that wipe any changes anyone's made to config? Debian would only refuse to overwrite the config if it thinks we've edited the config at some point.

[Maxim]

Hello jtinsley!

Is "pemStdTTL" a new variable? I can see at some point document server has been updated, so there's two default.json config files;
/etc/onlyoffice/documentserver/default.json
/etc/onlyoffice/documentserver/default.json.dpkg-dist

As i understand you updated the server with parametr "keep your existing package". The new config is default.json.dpkg-dist but old config default.json is still working. It's not correct!

Should we overwrite the existing default.json with .dpkg-dist?

Yes

Will that wipe any changes anyone's made to config?

I suppose yes