[GH-ISSUE #97] Information about how to restart safely #53

Closed
opened 2026-02-26 09:35:44 +03:00 by kerem · 4 comments
Owner

Originally created by @y0va on GitHub (Apr 11, 2018).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/97

There should be some notes about how to restart / update the docker container safely, so that all loaded documents are saved. I lost some data because of assuming that it goes fine by normal restart procedure.

Originally created by @y0va on GitHub (Apr 11, 2018). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/97 There should be some notes about how to restart / update the docker container safely, so that all loaded documents are saved. I lost some data because of assuming that it goes fine by normal restart procedure.
kerem 2026-02-26 09:35:44 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@aaronouthier commented on GitHub (May 26, 2018):

An obscure article I came across recently, mentions how to do a safe shutdown by forcefully disconnecting all users.

Article can be found here: https://helpcenter.onlyoffice.com/server/docker/document/troubleshooting.aspx

Edit: Corrected article reference to point to Docker section, instead of Linux section of Help Center.

<!-- gh-comment-id:392229355 --> @aaronouthier commented on GitHub (May 26, 2018): An obscure article I came across recently, mentions how to do a safe shutdown by forcefully disconnecting all users. Article can be found here: [https://helpcenter.onlyoffice.com/server/docker/document/troubleshooting.aspx](url) Edit: Corrected article reference to point to Docker section, instead of Linux section of Help Center.
Author
Owner

@aaronouthier commented on GitHub (May 26, 2018):

Run this command from your docker HOST's command prompt.
sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh

Obviously, substitute the actual docker container name or id for your system into the appropriate place above.

Edit: Corrected the command to type.

<!-- gh-comment-id:392229658 --> @aaronouthier commented on GitHub (May 26, 2018): Run this command from your docker HOST's command prompt. `sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh` Obviously, substitute the actual docker container name or id for your system into the appropriate place above. Edit: Corrected the command to type.
Author
Owner

@drebs commented on GitHub (Oct 20, 2018):

The link above is correct but doesn't match the actual URL that opens when you click it. This is the correct place for that documentation: https://helpcenter.onlyoffice.com/server/docker/document/troubleshooting.aspx

I copy the relevant content below in case the link ever gets outdated:

Document Server usage issues

Q: Data loss has occured when stopping Document Server. How to prevent data loss?

A: Due to the operational characteristic, Document Server saves a document only after the document has been closed by all the users who edited it. To avoid data loss, you must forcefully disconnect the Document Server users when you need to stop Document Server in cases of the application update, server reboot etc. To do that, execute the following script on the server where Document Server is installed:

sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh
  • Executing the script may take a long time (up to 5 minutes).
  • Disconnecting users may take a long time (up to 5 minutes).
<!-- gh-comment-id:431570847 --> @drebs commented on GitHub (Oct 20, 2018): The link above is correct but doesn't match the actual URL that opens when you click it. This is the correct place for that documentation: https://helpcenter.onlyoffice.com/server/docker/document/troubleshooting.aspx I copy the relevant content below in case the link ever gets outdated: ## Document Server usage issues **Q:** Data loss has occured when stopping Document Server. How to prevent data loss? **A:** Due to the operational characteristic, Document Server saves a document only after the document has been closed by all the users who edited it. To avoid data loss, you must forcefully disconnect the Document Server users when you need to stop Document Server in cases of the application update, server reboot etc. To do that, execute the following script on the server where Document Server is installed: ``` sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh ``` * Executing the script may take a long time (up to 5 minutes). * Disconnecting users may take a long time (up to 5 minutes).
Author
Owner

@ShockwaveNN commented on GitHub (Apr 22, 2019):

I think I'll close this issue since this is more a question (and it's resolved) than an issue

<!-- gh-comment-id:485454844 --> @ShockwaveNN commented on GitHub (Apr 22, 2019): I think I'll close this issue since this is more a question (and it's resolved) than an issue
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#53
No description provided.