[onlyoffice] if `local.conf` is empty, the charm can't solve the situation by itself #17

Open
opened 3 years ago by vlab · 1 comments
vlab commented 3 years ago
Owner

We got a server that had an empty local.conf in /etc/onlyoffice/documentserver/local.conf. This will make it unable to launch.

The compose up will finish, but the logs of the onlyoffice docker will end about waiting for amqp. This is due to the fact that the default url from rabbitmq is in the local.conf.

This issue is to remember to have a check for this situation (empty local.json), and know what to do automatically if this happens.

What needs to be done is to copy the default local.json (either from another server, or from the documentserver-default dir.
The other quick way to solve this is to remove dir /srv/datastore/config/onlyoffice. Everything should be rebuilt with grace upon next compose up.

We got a server that had an empty `local.conf` in `/etc/onlyoffice/documentserver/local.conf`. This will make it unable to launch. The `compose up` will finish, but the logs of the `onlyoffice` docker will end about waiting for `amqp`. This is due to the fact that the default url from rabbitmq is in the `local.conf`. This issue is to remember to have a check for this situation (empty `local.json`), and know what to do automatically if this happens. What needs to be done is to copy the default `local.json` (either from another server, or from the `documentserver-default` dir. The other quick way to solve this is to remove dir `/srv/datastore/config/onlyoffice`. Everything should be rebuilt with grace upon next `compose up`.
vlab changed title from [onlyoffice] if `local.js` is empty, the charm can't solve the situation by itself to [onlyoffice] if `local.conf` is empty, the charm can't solve the situation by itself 3 years ago
vlab commented 1 year ago
Poster
Owner

To be noted, we had the issue of a log in /etc/onlyoffice/documentserver/log4js/production.json that was also knocked out (emptied).

This made de inner docservice process unable to start, and thus would make the connection with nextcloud to wait and timeout.

To be noted, we had the issue of a log in `/etc/onlyoffice/documentserver/log4js/production.json` that was also knocked out (emptied). This made de inner `docservice` process unable to start, and thus would make the connection with nextcloud to wait and timeout.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.