From 96b98337a8861854d424796f5727d0edc0b673fe Mon Sep 17 00:00:00 2001 From: Alexander Vnuchkov Date: Thu, 12 Apr 2018 15:06:23 +0300 Subject: [PATCH] Added info about correct server restart --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index b421d55..3d01edf 100644 --- a/README.md +++ b/README.md @@ -13,6 +13,7 @@ * [Installing ONLYOFFICE Document Server integrated with Community and Mail Servers](#installing-onlyoffice-document-server-integrated-with-community-and-mail-servers) * [Issues](#issues) - [Docker Issues](#docker-issues) + - [Document Server usage Issues](#document-server-usage-issues) * [Project Information](#project-information) * [User Feedback and Support](#user-feedback-and-support) @@ -281,6 +282,16 @@ As a relatively new project Docker is being worked on and actively developed by The known Docker issue with ONLYOFFICE Document Server with rpm-based distributives is that sometimes the processes fail to start inside Docker container. Fedora and RHEL/CentOS users should try disabling selinux with setenforce 0. If it fixes the issue then you can either stick with SELinux disabled which is not recommended by RedHat, or switch to using Ubuntu. +### Document Server usage issues + +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 documentserver-prepare4shutdown.sh +``` + +Please note, that both executing the script and disconnecting users may take a long time (up to 5 minutes). + ## Project Information Official website: [http://www.onlyoffice.org](http://onlyoffice.org "http://www.onlyoffice.org")