Community,Document, Mail Server Docker Synology NAS

Workspace
,
1

Hello,

Just installed the latest versions of Community, Document, and Mail Server on my Synology NAS. It seems like everything installs correctly, but I get the following error from community server

onlyoffice-community-server  | error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
onlyoffice-community-server  | Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
onlyoffice-community-server  | + sleep 1
onlyoffice-community-server  | + mysqladmin --defaults-extra-file=/etc/mysql/conf.d/client.cnf ping
onlyoffice-community-server  | mysqladmin: connect to server at 'localhost' failed
onlyoffice-community-server  | error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
onlyoffice-community-server  | Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
onlyoffice-community-server  | + sleep 1
onlyoffice-community-server  | + mysqladmin --defaults-extra-file=/etc/mysql/conf.d/client.cnf ping
onlyoffice-community-server  | mysqladmin: connect to server at 'localhost' failed
onlyoffice-community-server  | error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
onlyoffice-community-server  | Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
onlyoffice-community-server  | + sleep 1

I’ve tried change client.cnf, and mysqld.cnf to locathost with no change.
I have the port 3306 open in the firewall. I have all the containers in the same subnet.

Here is my docker compose

version: "3.3"
services:
  communityserver:
    networks:
      - onlyoffice
    stdin_open: true
    tty: true
    restart: always
    container_name: onlyoffice-community-server
    ports:
      - 8500:80
      - 5222:5222
      - 9443:443
    volumes:
      - /volume1/docker/onlyoffice/communityserver/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/communityserver/mysql:/var/lib/mysql
      - /volume1/docker/onlyoffice/communityserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/DocumentServerData
    environment:
      - DOCUMENT_SERVER_PORT_80_TCP_ADDR=onlyoffice-document-server
      - MAIL_SERVER_DB_HOST=onlyoffice-mail-server
    image: onlyoffice/communityserver
  documentserver:
    networks:
      - onlyoffice
    container_name: onlyoffice-document-server
    volumes:
      - /volume1/docker/onlyoffice/documentserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/Data
    environment:
      - JWT_ENABLED=true
      - JWT_SECRET=my secret
      - JWT_HEADER=Authorization
      - JWT_IN_BODY=true
    restart: always
    image: onlyoffice/documentserver
  onlyoffice-mail-server:
    networks:
      - onlyoffice
    privileged: true
    stdin_open: true
    tty: true
    restart: always
    container_name: onlyoffice-mail-server
    ports:
      - 25:25
      - 143:143
      - 587:587
    volumes:
      - /volume1/docker/onlyoffice/mailserver/data:/var/vmail
      - /volume1/docker/onlyoffice/mailserver/data/certs:/etc/pki/tls/mailserver
      - /volume1/docker/onlyoffice/mailserver/logs:/var/log
      - /volume1/docker/onlyoffice/mailserver/mysql:/var/lib/mysql
    hostname: hostname
    image: onlyoffice/mailserver
networks:
  onlyoffice:
    driver: bridge

Any help would be appreciated. Thanks.

PS: I also came across this as I was trying to reinstall

su: warning: cannot change directory to /nonexistent: Permission denied
2

Hello @Keith
The provided logs means an issue with MySQL. Meanwhile, in your compose file I don’t see the MySQL container. The MySQL is required for Workspace\Groups installation.
Please rewrite your compose file. You can use this one for the reference: Installed Onlyoffice using Docker-compose and it's loading indefinetely - #2 by Alexandre
Just change images tags for the latest one. You can check the latest tag versions here:
https://hub.docker.com/r/onlyoffice/documentserver/tags
https://hub.docker.com/r/onlyoffice/communityserver/tags
https://hub.docker.com/r/onlyoffice/controlpanel/tags
https://hub.docker.com/r/onlyoffice/mailserver/tags
For the MySQL container, please use mysql:8.0.29

If I misunderstood your request, please clarify it.

3

Still having trouble with Myql onlyoffice-mysql-server | 2024-07-26T19:58:57.224700Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it. This is after using your compose

onlyoffice-elasticsearch     | {"type": "server", "timestamp": "2024-07-26T20:36:20,982Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "docker-cluster", "node.name": "09070ab79110", "message": "uncaught exception in thread [main]", 
onlyoffice-elasticsearch     | "stacktrace": ["org.elasticsearch.bootstrap.StartupException: ElasticsearchException[failed to bind service]; nested: AccessDeniedException[/usr/share/elasticsearch/data/nodes];",
onlyoffice-elasticsearch     | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.16.3.jar:7.16.3]",
onlyoffice-elasticsearch     | "at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:157) ~[elasticsearch-7.16.3.jar:7.16.3]",
onlyoffice-elasticsearch     | "at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) ~[elasticsearch-7.16.3.jar:7.16.3]",
onlyoffice-elasticsearch     | "at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) ~[elasticsearch-cli-7.16.3.jar:7.16.3]",

onlyoffice-document-server  | [2024-07-26T21:53:04.771] [WARN] [localhost] [docId] [userId] nodeJS - [Error: ENOENT: no such file or directory, open '/var/www/onlyoffice/documentserver/../Data/license.lic'] {
onlyoffice-document-server  |   errno: -2,
onlyoffice-document-server  |   code: 'ENOENT',
onlyoffice-document-server  |   syscall: 'open',
onlyoffice-document-server  |   path: '/var/www/onlyoffice/documentser

onlyoffice-mysql-server      | mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/onlyoffice.cnf' is ignored.
onlyoffice-mysql-server      | 2024-07-26T22:16:59.262871Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
onlyoffice-mysql-server      | 2024-07-26T22:16:59.264412Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 80
onlyoffice-mysql-server      | 2024-07-26T22:16:59.266216Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
onlyoffice-mysql-server      | 2024-07-26T22:16:59.266221Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
onlyoffice-mysql-server      | 2024-07-26T22:16:59.266271Z 0 [ERROR] [MY-010119] [Server] Aborting
onlyoffice-mysql-server      | 2024-07-26T22:16:59.266689Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
onlyoffice-mysql-server      | 2024-07-26 22:17:45+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26 22:17:45+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
onlyoffice-mysql-server      | 2024-07-26 22:17:45+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26 22:17:45+00:00 [Note] [Entrypoint]: Initializing database files
onlyoffice-mysql-server      | mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/onlyoffice.cnf' is ignored.
onlyoffice-mysql-server      | 2024-07-26T22:17:45.769218Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
onlyoffice-mysql-server      | 2024-07-26T22:17:45.770631Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 80
onlyoffice-mysql-server      | 2024-07-26T22:17:45.772447Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
onlyoffice-mysql-server      | 2024-07-26T22:17:45.772452Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
onlyoffice-mysql-server      | 2024-07-26T22:17:45.772502Z 0 [ERROR] [MY-010119] [Server] Aborting
onlyoffice-mysql-server      | 2024-07-26T22:17:45.772932Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
onlyoffice-mysql-server exited with code 0
onlyoffice-mysql-server      | 2024-07-26 22:18:09+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26 22:18:09+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
onlyoffice-mysql-server      | 2024-07-26 22:18:09+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26 22:18:09+00:00 [Note] [Entrypoint]: Initializing database files
onlyoffice-mysql-server      | mysqld: [Warning] World-writable config file '/etc/mysql/conf.d/onlyoffice.cnf' is ignored.
onlyoffice-mysql-server      | 2024-07-26T22:18:09.893748Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
onlyoffice-mysql-server      | 2024-07-26T22:18:09.895376Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 80
onlyoffice-mysql-server      | 2024-07-26T22:18:09.897418Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
onlyoffice-mysql-server      | 2024-07-26T22:18:09.897424Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
onlyoffice-mysql-server      | 2024-07-26T22:18:09.897475Z 0 [ERROR] [MY-010119] [Server] Aborting
onlyoffice-mysql-server      | 2024-07-26T22:18:09.897940Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
onlyoffice-mysql-server exited with code 0
onlyoffice-mysql-server      | 2024-07-26 22:18:31+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26 22:18:31+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
onlyoffice-mysql-server      | 2024-07-26 22:18:31+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.1-1.el9 started.
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384375Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384380Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384427Z 0 [ERROR] [MY-010119] [Server] Aborting
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384427Z 0 [ERROR] [MY-010119] [Server] Aborting
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384879Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
onlyoffice-mysql-server      | 2024-07-26T22:18:32.384879Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
onlyoffice-mysql-server exited with code 1

For complete error details, refer to the log at /usr/share/elasticsearch/logs/docker-cluster.log

onlyoffice-elasticsearch     | Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
onlyoffice-elasticsearch     | output:
onlyoffice-elasticsearch     | [0.000s][error][logging] Error opening log file 'logs/gc.log': Permission denied
onlyoffice-elasticsearch     | [0.000s][error][logging] Initialization of output 'file=logs/gc.log' using options 'filecount=32,filesize=64m' failed.
onlyoffice-elasticsearch     | error:
onlyoffice-elasticsearch     | Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details.
onlyoffice-elasticsearch     | Error: Could not create the Java Virtual Machine.
onlyoffice-elasticsearch     | Error: A fatal exception has occurred. Program will exit.
4

@Alexandre

2024-02-19T12:31:54.029627Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) initializing of server in progress as process 13805
2024-02-19T12:31:54.047532Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:31:54.738857Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:31:57.593575Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2024-02-19T12:31:59.531671Z 6 [System] [MY-013172] [Server] Received SHUTDOWN from user boot. Shutting down mysqld (Version: 8.0.36-0ubuntu0.22.04.1).
2024-02-19T12:32:03.949383Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) starting as process 13850
2024-02-19T12:32:03.976650Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:32:04.182786Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:32:04.531648Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-19T12:32:04.531705Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-19T12:32:04.538589Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
2024-02-19T12:32:04.564283Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
2024-02-19T12:32:04.564519Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36-0ubuntu0.22.04.1'  socket: '/tmp/tmp.aJm4VqDbTZ/mysqld.sock'  port: 0  (Ubuntu).
2024-02-19T12:32:04.652645Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.36-0ubuntu0.22.04.1).
2024-02-19T12:32:06.104125Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36-0ubuntu0.22.04.1)  (Ubuntu).
2024-02-19T12:32:07.101771Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) starting as process 13920
2024-02-19T12:32:07.110111Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:32:07.334455Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:32:07.613305Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-19T12:32:07.613373Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-19T12:32:07.622290Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
2024-02-19T12:32:07.650792Z 7 [System] [MY-013172] [Server] Received SHUTDOWN from user boot. Shutting down mysqld (Version: 8.0.36-0ubuntu0.22.04.1).
2024-02-19T12:32:07.658083Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-02-19T12:32:09.185889Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36-0ubuntu0.22.04.1)  (Ubuntu).
2024-02-19T12:32:09.828622Z mysqld_safe Logging to '/var/log/mysql/error.log'.
2024-02-19T12:32:09.851972Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2024-02-19T12:32:10.192791Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) starting as process 14160
2024-02-19T12:32:10.201093Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:32:10.486941Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:32:10.822874Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-19T12:32:10.822934Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-19T12:32:10.858785Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-02-19T12:32:10.858986Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36-0ubuntu0.22.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu).
mbind: Operation not permitted
2024-02-19T12:32:13.491343Z 14 [System] [MY-013172] [Server] Received SHUTDOWN from user debian-sys-maint. Shutting down mysqld (Version: 8.0.36-0ubuntu0.22.04.1).
2024-02-19T12:32:14.219795Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36-0ubuntu0.22.04.1)  (Ubuntu).
2024-02-19T12:32:14.278861Z mysqld_safe mysqld from pid file /var/lib/mysql/95cf128f67ec.pid ended
2024-02-19T12:32:14.691168Z mysqld_safe Logging to '/var/log/mysql/error.log'.
2024-02-19T12:32:14.706483Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2024-02-19T12:32:15.035853Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) starting as process 14664
2024-02-19T12:32:15.041756Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-02-19T12:32:15.041768Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2024-02-19T12:32:15.051793Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:32:15.280156Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:32:15.542526Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-19T12:32:15.542589Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-19T12:32:15.586351Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-02-19T12:32:15.586484Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36-0ubuntu0.22.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu).
2024-02-19T12:33:09.395025Z 15 [System] [MY-013172] [Server] Received SHUTDOWN from user debian-sys-maint. Shutting down mysqld (Version: 8.0.36-0ubuntu0.22.04.1).
2024-02-19T12:33:10.051195Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.36-0ubuntu0.22.04.1)  (Ubuntu).
2024-02-19T12:33:10.151847Z mysqld_safe mysqld from pid file /var/lib/mysql/95cf128f67ec.pid ended
2024-02-19T12:33:10.801083Z mysqld_safe Logging to '/var/log/mysql/error.log'.
2024-02-19T12:33:10.828221Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2024-02-19T12:33:11.276001Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36-0ubuntu0.22.04.1) starting as process 17379
2024-02-19T12:33:11.278378Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-02-19T12:33:11.278394Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2024-02-19T12:33:11.289954Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-02-19T12:33:11.798262Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-02-19T12:33:12.192529Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-02-19T12:33:12.192593Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-02-19T12:33:12.284156Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-02-19T12:33:12.284444Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36-0ubuntu0.22.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu).
5 
[Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
onlyoffice-mysql-server      | 2024-07-29T04:02:33.065370Z 89 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
onlyoffice-mysql-server      | 2024-07-29T04:02:33.070286Z 90 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead
6 
ERROR 1251 (08004): Client does not support authentication protocol requested by server; consider upgrading MySQL client

onlyoffice-community-server  | [FAILED] Failed to start ONLYOFFICE MailWatchdog Service.
onlyoffice-community-server  | See 'systemctl status onlyofficeMailWatchdog.service' for details.
onlyoffice-community-server  | [FAILED] Failed to start ONLYOFFICE MailAggregator Service.
onlyoffice-community-server  | See 'systemctl status onlyofficeMailAggregator.service' for details.

The systemctl status

× onlyofficeMailWatchdog.service - ONLYOFFICE MailWatchdog Service
     Loaded: loaded (/lib/systemd/system/onlyofficeMailWatchdog.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Mon 2024-07-29 05:47:40 UTC; 7min ago
    Process: 7158 ExecStart=/usr/bin/dotnet /var/www/onlyoffice/Services/MailWatchdog/ASC.Mail.Watchdog.Service.dll --urls=http://0.0.0.0:5031 --pathToConf=/etc/onlyoffice/communityserver --pathToNlogConf=/etc/onlyoffice/communityserver --log:dir=/var/log/onlyoffice/mail --log:name=mail-watchdog --ENVIRONMENT=production (code=dumped, signal=ABRT)
   Main PID: 7158 (code=dumped, signal=ABRT)

Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailWatchdog.service: Scheduled restart job, restart counter is at 11.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: Stopped ONLYOFFICE MailWatchdog Service.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailWatchdog.service: Start request repeated too quickly.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailWatchdog.service: Failed with result 'core-dump'.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: Failed to start ONLYOFFICE MailWatchdog Service.
7 
onlyoffice-mail-server       | Starting OpenDKIM Milter: opendkim: /etc/opendkim.conf: dsn:mysql://mail_admin:Isadmin123@onlyoffice-mysql-server/onlyoffice_mailserver/table=dkim?keycol=domain_name?datacol=id: dkimf_db_open(): Client does not support authentication protocol requested by server; consider upgrading MySQL client
onlyoffice-mail-server       |                             [FAILED]
8

MailAggregator Failed

× onlyofficeMailAggregator.service - ONLYOFFICE MailAggregator Service
     Loaded: loaded (/lib/systemd/system/onlyofficeMailAggregator.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Mon 2024-07-29 05:47:40 UTC; 39min ago
    Process: 7183 ExecStart=/usr/bin/dotnet /var/www/onlyoffice/Services/MailAggregator/ASC.Mail.Aggregator.Service.dll --urls=http://0.0.0.0:5025 --pathToConf=/etc/onlyoffice/communityserver --pathToNlogConf=/etc/onlyoffice/communityserver --log:dir=/var/log/onlyoffice/mail --log:name=mail-aggregator --ENVIRONMENT=production (code=dumped, signal=ABRT)
   Main PID: 7183 (code=dumped, signal=ABRT)

Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailAggregator.service: Scheduled restart job, restart counter is at 11.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: Stopped ONLYOFFICE MailAggregator Service.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailAggregator.service: Start request repeated too quickly.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: onlyofficeMailAggregator.service: Failed with result 'core-dump'.
Jul 29 05:47:40 a60f755b2ab0 systemd[1]: Failed to start ONLYOFFICE MailAggregator Service.
9

Hello @Keith
Sorry for the late reply. Could you please share your new compose file? We will check it out.

10

I actually had some success. The reason why I say “some” is that even those I used the Docker-CommunityServer/docker-compose.workspace.yml at master · ONLYOFFICE/Docker-CommunityServer · GitHub and not the enterprise one, I figured there wouldn’t be any need for a lic file. However its asking for one. So here is my final compose:

version: "3"
services:
  onlyoffice-mysql-server:
    container_name: onlyoffice-mysql-server
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.2
    image: mysql:8.0.29
    environment:
      - MYSQL_ROOT_PASSWORD=
      - TZ=America/Chicago
      - UMASK=022
#      - UMASK_DIR=755
    stdin_open: true
    tty: true
    restart: always
    privileged: true
    expose:
      - "3306"
      - "33060"
    volumes:
      - /volume1/docker/onlyoffice/mysql/conf.d:/etc/mysql/conf.d
      - /volume1/docker/onlyoffice/mysql/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
      - /volume1/docker/onlyoffice/mysql/data:/var/lib/mysql

  onlyoffice-community-server:
    container_name: onlyoffice-community-server
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.3
    image: onlyoffice/communityserver:12.5.2.1848
    depends_on:
      - onlyoffice-mysql-server
      - onlyoffice-document-server
      - onlyoffice-mail-server
      - onlyoffice-elasticsearch
    environment:
      - ONLYOFFICE_CORE_MACHINEKEY=
      - TZ=America/Chicago
      - CONTROL_PANEL_PORT_80_TCP=80
      - CONTROL_PANEL_PORT_80_TCP_ADDR=onlyoffice-control-panel
      - DOCUMENT_SERVER_PORT_80_TCP_ADDR=onlyoffice-document-server
      - DOCUMENT_SERVER_JWT_ENABLED=true
      - DOCUMENT_SERVER_JWT_SECRET=
      - DOCUMENT_SERVER_JWT_HEADER=AuthorizationJwt
      - MYSQL_SERVER_ROOT_PASSWORD=
      - MYSQL_SERVER_DB_NAME=onlyoffice
      - MYSQL_SERVER_HOST=onlyoffice-mysql-server
      - MYSQL_SERVER_USER=onlyoffice_user
      - MYSQL_SERVER_PASS=onlyoffice_pass
      - MAIL_SERVER_API_PORT=8081
      - MAIL_SERVER_API_HOST=onlyoffice-mail-server
      - MAIL_SERVER_DB_HOST=onlyoffice-mysql-server
      - MAIL_SERVER_DB_PORT=3306
      - MAIL_SERVER_DB_NAME=onlyoffice_mailserver
      - MAIL_SERVER_DB_USER=mail_admin
      - MAIL_SERVER_DB_PASS=Isadmin123
      - ELASTICSEARCH_SERVER_HOST=onlyoffice-elasticsearch
      - ELASTICSEARCH_SERVER_HTTPPORT=9200
    ports:
      - 8500:80
      - 5222:5222
      - 9443:443
    expose:
      - "9865"
      - "9888" 
      - "9866" 
      - "9871" 
      - "9882" 
      - "5280"
    stdin_open: true
    tty: true
    restart: always
    privileged: true
    #    cgroup: host
    volumes:
      - /volume1/docker/onlyoffice/communityserver/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/communityserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/communityserver/letsencrypt:/etc/letsencrypt
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/DocumentServerData
      - /sys/fs/cgroup:/sys/fs/cgroup:rw
      - /volume1/docker/onlyoffice/communityserver/certs:/var/www/onlyoffice/Data/certs

  onlyoffice-document-server:
    container_name: onlyoffice-document-server
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.4
    image: onlyoffice/documentserver-ee:latest
    stdin_open: true
    tty: true
    restart: always
    environment:
      - JWT_ENABLED=true
      - JWT_SECRET=TGCrx6eUsG2Ww45RLwpRLFKvDiYbeDjL
      - JWT_HEADER=AuthorizationJwt
      - TZ=America/Chicago
    expose:
      - "80"
      - "443"
    volumes:
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/documentserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/documentserver/fonts:/usr/share/fonts/truetype/custom
      - /volume1/docker/onlyoffice/documentserver/forgotten:/var/lib/onlyoffice/documentserver/App_Data/cache/files/forgotten

  onlyoffice-mail-server:
    container_name: onlyoffice-mail-server
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.5
        ipv6_address: 2600:1700:b730::5
    image: onlyoffice/mailserver:1.6.75
    depends_on:
      - onlyoffice-mysql-server
    hostname: houserofmanns.com
    environment:
      - MYSQL_SERVER=onlyoffice-mysql-server
      - MYSQL_SERVER_PORT=3306
      - MYSQL_ROOT_USER=mail_admin
      - MYSQL_ROOT_PASSWD=Isadmin123
      - MYSQL_SERVER_DB_NAME=onlyoffice_mailserver
      - TZ=America/Chicago
    restart: always
    privileged: true
    ports:
      - 25:25
      - 143:143
      - 587:587
    stdin_open: true
    tty: true
    expose:
      - "8081"
      - "3306"
    volumes:
      - /volume1/docker/onlyoffice/mailserver/data:/var/vmail
      - /volume1/docker/onlyoffice/mailserver/certs:/etc/pki/tls/mailserver
      - /volume1/docker/onlyoffice/mailserver/log:/var/log

  onlyoffice-control-panel:
    container_name: onlyoffice-control-panel
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.6
    depends_on:
      - onlyoffice-document-server
      - onlyoffice-mail-server
      - onlyoffice-community-server
    image: onlyoffice/controlpanel:latest
    environment:
      - ONLYOFFICE_CORE_MACHINEKEY=
    expose:
      - "80"
      - "443"
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /volume1/docker/onlyoffice/controlpanel/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/controlpanel/log:/var/log/onlyoffice
    stdin_open: true
    tty: true

  onlyoffice-elasticsearch:
    # https://hub.docker.com/r/onlyoffice/elasticsearch/tags 
    image: onlyoffice/elasticsearch:7.16.3
    container_name: onlyoffice-elasticsearch
    networks:
      onlyoffice:
        ipv4_address: 192.168.48.7
    restart: always
    environment:
      - discovery.type=single-node
      - bootstrap.memory_lock=true
      - ES_JAVA_OPTS=-Xms1g -Xmx1g -Dlog4j2.formatMsgNoLookups=true
      - indices.fielddata.cache.size=30%
      - indices.memory.index_buffer_size=30%
      - ingest.geoip.downloader.enabled=false
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65535
        hard: 65535
    volumes:
      - /volume1/docker/onlyoffice/elasticsearch/data:/usr/share/elasticsearch/data
    expose:
      - "9200"
      - "9300"
networks:
  onlyoffice:
    driver: bridge
    driver_opts:
      com.docker.network.enable_ipv6: "true"
    ipam:
      driver: default
      config:
      - subnet: 192.168.48.0/24
        gateway: 192.168.48.1
      - subnet:  
        gateway:
11

Hello @Keith,
Sorry for the late reply.
you are using Enterprise Edition of Document server in your compose file:
image: onlyoffice/documentserver-ee:latest
This is the reason why the portal asks for a license. You should use this repository if you want to use open-source version of Workspace: https://hub.docker.com/r/onlyoffice/documentserver/tags
As for your compose file, I found these issues:

  • MYSQL password is not specified
  • networks.onlyoffice.ipam.config.1.subnet must be specified (the last section in your compose file)

Could you please run a test? Please use this sample: Docker-CommunityServer/docker-compose.workspace.yml at release/12.7.0 · ONLYOFFICE/Docker-CommunityServer · GitHub
Just uncomment line 57 and do not forget to specify hostname for mailserver:Docker-CommunityServer/docker-compose.workspace.yml at release/12.7.0 · ONLYOFFICE/Docker-CommunityServer · GitHub

However, there’s another hint on this case. You mentioned, that you’re trying to deploy it on Synology NAS. Please bear in mind that we didn’t test such installation and we always recommend using separate clean server for Workspace installation.

1 Like
12

Thanks in advance. I switched on the enterprise version of DS for the CE version and now workspace ce is running on the synology nas. It is however running slow, not sure why this is, but it is running. Thanks in advance and I’ve shared my docker-compose on your github page it you would like to see it.

13

Hello @Keith
We are glad that you managed the situation.
Have you made a pull request? If so, we will review it.
As for the slowing performance, please bear in mind that we didn’t test the installation on the Synology NAS. However, these guides might help you to check if the situation is related to hardware requirements:

14

I’m not good with github yet so I have no clue on how to do a pull request. But I will look through documentation and see what I can adjust for better performance. Thank you so much.

15

So I thought I had everything working, but there is an issue.

So everything installs as it should, however when it comes to the mail server, it only connects successfully when you click verify to the mail server container ip. The mx record is unable to be setup because of this.

16

For bug reports, provide the steps to reproduce and if possible a minimal demo of the problem: Unable to connect to mail server from outside of the container

Community Server/Control Panel version: latest
Type of installation of Workspace (docker, deb/rpm, exe, please point us to the installation guide that you used as well): Docker Workspace (Mail Server
OS: Synology NAS
Browser version: Thorium

So I was able to install Workspace CE on Synology NAS. I know you guys haven’t ran test on it with Workspace. However I’m sure you can still help me out.

So I got everything install, (it takes at least an hour or more just go through its first boot process) Anyway, I go to the mail server connection and it immediately shows the ip of the container. You try and switch that to the host ip, it fails. This is an issue if everything for the most part is suppose to run through the host ip address. It stop me from connecting to my mx records. The domain setting always have a dns setting because its looking for the container ip instead of the host Ip.

Here is my compose

services:
  onlyoffice-mysql-server:
    container_name: onlyoffice-mysql-server
    image: mysql:8.0.29
    environment:
      - MYSQL_ROOT_PASSWORD=pass
      - TZ=America/Chicago
      - UMASK=022
    stdin_open: true
    tty: true
    restart: always
    privileged: true
    network:
      - onlyoffice
    expose:
      - "3306"
      - "33060"
    volumes:
      - /volume1/docker/onlyoffice/mysql/conf.d:/etc/mysql/conf.d
      - /volume1/docker/onlyoffice/mysql/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
      - /volume1/docker/onlyoffice/mysql/data:/var/lib/mysql

  onlyoffice-community-server:
    container_name: onlyoffice-community-server
    image: onlyoffice/communityserver:latest
    depends_on:
      - onlyoffice-mysql-server
      - onlyoffice-document-server
      - onlyoffice-mail-server
      - onlyoffice-elasticsearch
    environment:
      - ONLYOFFICE_CORE_MACHINEKEY= openssl 32
      - TZ=America/Chicago
      - CONTROL_PANEL_PORT_80_TCP=80
      - CONTROL_PANEL_PORT_80_TCP_ADDR=onlyoffice-control-panel
      - DOCUMENT_SERVER_PORT_80_TCP_ADDR=onlyoffice-document-server
      - DOCUMENT_SERVER_JWT_ENABLED=true
      - DOCUMENT_SERVER_JWT_SECRET=openssl 32
      - DOCUMENT_SERVER_JWT_HEADER=AuthorizationJwt
      - MYSQL_SERVER_ROOT_PASSWORD=pass
      - MYSQL_SERVER_DB_NAME=onlyoffice
      - MYSQL_SERVER_HOST=onlyoffice-mysql-server
      - MYSQL_SERVER_USER=onlyoffice_user
      - MYSQL_SERVER_PASS=onlyoffice_pass
      - MAIL_SERVER_API_PORT=8081
      - MAIL_SERVER_API_HOST=onlyoffice-mail-server
      - MAIL_SERVER_DB_HOST=onlyoffice-mysql-server
      - MAIL_SERVER_DB_PORT=3306
      - MAIL_SERVER_DB_NAME=onlyoffice_mailserver
      - MAIL_SERVER_DB_USER=mail_admin
      - MAIL_SERVER_DB_PASS=Isadmin123
      - ELASTICSEARCH_SERVER_HOST=onlyoffice-elasticsearch
      - ELASTICSEARCH_SERVER_HTTPPORT=9200
    network:
      - onlyoffice
    ports:
      - 8500:80
      - 5222:5222
      - 9443:443
    stdin_open: true
    tty: true
    restart: always
    privileged: true
    cpuset: "0-10"  # Binds the service to cores 0, 1, 2, and 3
    cpu_shares: 3072  # Relative CPU weight for containers
    volumes:
      - /volume1/docker/onlyoffice/communityserver/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/communityserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/communityserver/letsencrypt:/etc/letsencrypt
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/DocumentServerData
      - /sys/fs/cgroup:/sys/fs/cgroup
      - /volume1/docker/onlyoffice/communityserver/certs:/var/www/onlyoffice/Data/certs

  onlyoffice-document-server:
    container_name: onlyoffice-document-server
    image: onlyoffice/documentserver:latest
    stdin_open: true
    tty: true
    restart: always
    environment:
      - JWT_ENABLED=true
      - JWT_SECRET=openssl 32
      - JWT_HEADER=AuthorizationJwt
      - TZ=America/Chicago
    network:
      - onlyoffice
    expose:
      - "80"
      - "443"
    volumes:
      - /volume1/docker/onlyoffice/documentserver/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/documentserver/logs:/var/log/onlyoffice
      - /volume1/docker/onlyoffice/documentserver/fonts:/usr/share/fonts/truetype/custom
      - /volume1/docker/onlyoffice/documentserver/forgotten:/var/lib/onlyoffice/documentserver/App_Data/cache/files/forgotten

  onlyoffice-mail-server:
    container_name: onlyoffice-mail-server
    image: onlyoffice/mailserver:latest
    depends_on:
      - onlyoffice-mysql-server
    hostname: mail.domain.com
    environment:
      - MYSQL_SERVER=onlyoffice-mysql-server
      - MYSQL_SERVER_PORT=3306
      - MYSQL_ROOT_USER=mail_admin
      - MYSQL_ROOT_PASSWD=Isadmin123
      - MYSQL_SERVER_DB_NAME=onlyoffice_mailserver
      - TZ=America/Chicago
    restart: always
    privileged: true
    network:
      - onlyoffice
    ports: ['25:25','143:143','587:587','8081:8081']
#    stdin_open: true
#    tty: true
    expose:
      - "8081"
    volumes:
      - /volume1/docker/onlyoffice/mailserver/data:/var/vmail
      - /volume1/docker/onlyoffice/mailserver/certs:/etc/pki/tls/mailserver
      - /volume1/docker/onlyoffice/mailserver/log:/var/log

  onlyoffice-control-panel:
    container_name: onlyoffice-control-panel
    depends_on:
      - onlyoffice-document-server
      - onlyoffice-mail-server
      - onlyoffice-community-server
    image: onlyoffice/controlpanel:latest
    environment:
      - ONLYOFFICE_CORE_MACHINEKEY=openssl 32
    network:
      - onlyoffice
    expose:
      - "80"
      - "443"
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /volume1/docker/onlyoffice/controlpanel/data:/var/www/onlyoffice/Data
      - /volume1/docker/onlyoffice/controlpanel/log:/var/log/onlyoffice
    stdin_open: true
    tty: true

  onlyoffice-elasticsearch: 
    image: onlyoffice/elasticsearch:7.16.3
    container_name: onlyoffice-elasticsearch
    restart: always
    environment:
      - discovery.type=single-node
      - bootstrap.memory_lock=true
      - ES_JAVA_OPTS=-Xms1g -Xmx1g -Dlog4j2.formatMsgNoLookups=true
      - indices.fielddata.cache.size=30%
      - indices.memory.index_buffer_size=30%
      - ingest.geoip.downloader.enabled=false
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65535
        hard: 65535
    volumes:
      - /volume1/docker/onlyoffice/elasticsearch/data:/usr/share/elasticsearch/data
    network:
      - onlyoffice
    expose:
      - "9200"
      - "9300"
network:
  onlyoffice:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 192.168.48.0/16
          gateway: 192.168.48.1

I would share logs, but there is nothing that shows an error or anything else. Thanks in advance for your help

17

Hello @Keith
Could you please show us the entire scenario, step-by-step? Also, please go to Mail server and restart Mail container (docker restart *ID_of_container* ), after that go to portal settings and re-connect Mail server one more time. Please show us the result.

18

So I restarted the mail server as requested and got the same error. As far as step by step, not im not sure what your asking for. I run my docker-compose, everything starts, I go to settings/mail server and it shows a docker container ip address. It wont let me connect to any other ip address. I even tried change the 8081 from expose to port in the compose and it wont connect. However the error message changes to Error: Could not get the hostname.

19

Hello @Keith
I have merged your second topic since it describes the same request.
In the provided compose file I don’t see this parameter: Docker-CommunityServer/docker-compose.workspace.yml at release/12.7.0 · ONLYOFFICE/Docker-CommunityServer · GitHub
Also please make sure that you specified the hostname for the mailserver correctly:
hostname: mail.domain.com

20

Hey thanks for the response. I did set the hostname correctly. I saw that parameter, but didn’t think it was valid since its commented out. So I’m assuming I need to remove # then?