Try the fastest and simplest way to install ONLYOFFICE

co-editing doesn't work

Questions/problems on Docker

co-editing doesn't work

Postby gaord » Wed Sep 21, 2016 11:36 am


I had setup testing system on docker-compose without volumes configuration and it work just fine. Then when I setup one production system as in yams file below with volumes configuration, it ends up with error to stop co-editing online at all. It sayes can't start editing the file when multiple users are on the same files for a while. I have to restart community server to get back to normal. However, after another while, the error will pop up again to stop co-editing at all.

Community server version is The docker images were pulled couple weeks ago from official site.

I attached error from browser. and also some log from web.files as below:
Could you give some insight on what's wrong with it?
Many thanks,
2016-09-21 11:19:56,085 DEBUG [Threadpool worker] ASC.Files - DocService command Info fileId '197' docKey 'LUpdhK47uvXF16v9fKw_' callbackUrl '' users '' status ''
2016-09-21 11:19:56,093 ERROR [Threadpool worker] ASC.Files - DocService command error
System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP) <0x40d08970 + 0x001cb> in <filename unknown>:0
at System.Net.WebConnection.Connect (System.Net.HttpWebRequest request) <0x40d07a40 + 0x005cf> in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) <0x40d06f00 + 0x001ab> in <filename unknown>:0
at System.Net.HttpWebRequest.GetResponse () <0x40cf0dc0 + 0x0005a> in <filename unknown>:0
at ASC.Web.Core.Files.DocumentService.CommandRequest (System.String documentTrackerUrl, CommandMethod method, System.String documentRevisionId, System.String callbackUrl, System.String users, System.String status) <0x412eaab0 + 0x0046f> in <filename unknown>:0
at ASC.Web.Files.Services.DocumentService.DocumentServiceConnector.Command (CommandMethod method, System.String docKeyForTrack, System.Object fileId, System.String callbackUrl, System.String users, System.String status) <0x412ea6b0 + 0x001cb> in <filename unknown>:0
2016-09-21 11:19:56,100 ERROR [Threadpool worker] ASC.Files - System.Exception: 无法开始编辑该文件
at ASC.Web.Files.Services.WCFService.FileStorageServiceController.StartEdit (System.String fileId, System.String docKeyForTrack, Boolean asNew, Boolean editingAlone, System.String doc) <0x412ea230 + 0x00197> in <filename unknown>:0

Here is docker-compose.yaml:
image: onlyoffice/communityserver:v1
entrypoint: dumb-init bash --rcfile /app/onlyoffice/ -i
- documentserver:document_server
- mailserver:mail_server
- "80:80"
- /data/onlyoffice/CommunityServer/data:/var/www/onlyoffice/Data
- /data/onlyoffice/CommunityServer/mysql:/var/lib/mysql
- /data/onlyoffice/CommunityServer/logs:/var/log/onlyoffice
# - /data/onlyoffice/DocumentServer/data:/var/www/onlyoffice/DocumentServerData
stdin_open: true
tty: true
image: onlyoffice/documentserver
stdin_open: true
- "81:80"
- /data/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data
- /data/onlyoffice/DocumentServer/logs:/var/log/onlyoffice
tty: true
image: onlyoffice/mailserver
privileged: true
- "25:25"
- "143:143"
- "587:587"
- /data/onlyoffice/MailServer/data:/var/vmail
- /data/onlyoffice/MailServer/data/certs:/etc/pki/tls/mailserver
- /data/onlyoffice/MailServer/logs:/var/log
- /data/onlyoffice/MailServer/mysql:/var/lib/mysql
stdin_open: true
tty: true
2016-09-21 下午7.20.41.png
2016-09-21 下午7.20.41.png (111.75 KiB) Viewed 1599 times
Posts: 4
Joined: Sat Sep 03, 2016 12:51 pm

Re: co-editing doesn't work

Postby gaord » Mon Sep 26, 2016 2:58 am

Hi there,
It looks like running docking version in VMWare will have the issues somehow. I set up two servers in VMWare and end up with the same issue. While setting up one in bare-metal, it works without the problem. All setups are with the same docker-compose.yml file and data files in volumes. It will be a bug for scenario of docker version on VMWare, won't it?

Thanks anyway for your time,
Posts: 4
Joined: Sat Sep 03, 2016 12:51 pm

Re: co-editing doesn't work

Postby Alex » Wed Sep 28, 2016 10:13 am

The same ports have been mounted in both cases?
If you link the containers you do not have to use port mapping for the DocumentServer
Follow the link to find an example of docker compose.
Posts: 52
Joined: Sat Nov 07, 2015 3:19 pm

Return to Docker Version

Who is online

Users browsing this forum: No registered users and 3 guests