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
gc: ERROR (abnormal termination)
docservice: ERROR (abnormal termination)
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;
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.