Running the Docker version of the 'only office/documentserver' container on the Rocky linux system timed out and reported an error

Do you want to: Suggest a feature / Report a bug / Ask a how-to question
For feature suggestions, describe the result you would like to achieve in detail.
For bug reports, provide the steps to reproduce and if possible a minimal demo of the problem.
Document Server version:onlyoffice/documentserver latest 01da3778d001 (docker)
Type of installation of the Document Server (docker, deb/rpm, exe, please point us to the installation guide that you used as well):
OS:Rocky linux system
Browser version:google Browser NEW
Additional information:
Any relevant details about the situation. If you’ve modified configuration files or are using a proxy server that might affect the situation, please mention it. You can also attach images and videofile to the post (or to place them to external storage)

I am functioning normally in CentOS 7, and the CPU, memory, storage, and other configurations of CentOS 7 and Rocky9 are basically the same

rocky onlyoffice docker logs
[root@localhost ~]# docker logs -f ab7f

  • Starting PostgreSQL 14 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_{log, _err}
    [fail]
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672
    Waiting for connection to the localhost host on port 5672

centos7 onlyoffice docker logs

  • Starting PostgreSQL 14 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server [ OK ]
  • Reloading nginx configuration nginx [ OK ]
    Starting supervisor: supervisord.
    cron: unrecognized service
  • Starting nginx nginx [ OK ]
    Generating AllFonts.js, please wait…Done
    Generating presentation themes, please wait… * Starting PostgreSQL 14 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server [ OK ]
  • Reloading nginx configuration nginx [ OK ]
    Starting supervisor: supervisord.
    cron: unrecognized service
  • Starting nginx nginx [ OK ]
    Generating AllFonts.js, please wait…Done
    Generating presentation themes, please wait…Done
    Generating js caches, please wait…Done
    ds:docservice: stopped
    ds:docservice: started
    ds:converter: stopped
    ds:converter: started
  • Starting PostgreSQL 14 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server [ OK ]
  • Reloading nginx configuration nginx [ OK ]
    Starting supervisor: supervisord.
    cron: unrecognized service
  • Starting nginx nginx [ OK ]
    Generating AllFonts.js, please wait…Done
    Generating presentation themes, please wait… * Starting PostgreSQL 14 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server [ OK ]
  • Reloading

Hello @sam123

This might be indicating that port 5672 is either occupied or closed. Please double check if all necessary for Document Server ports are opened, the list you can find here:

Additionally, please share contents of RabbitMQ log mentioned here:

Hello Constantine:
To be precise, it is Rocky9 (subsequent versions are not important)
Normal use of CentOS Docker installation source.
In a sense, all ports within the container should be enabled by default.

I have found that computers with slightly better performance require a long wait time (more than 10 minutes) when running the only office container on Rocky9, while on systems such as Rocky8, it is very fast.

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
Preparing for shutdown, it can take a lot of time, please wait...
==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2024-07-28T01:37:11.125] [WARN] [localhost] [docId] [userId] nodeJS - start shutdown:%b true
[2024-07-28T01:37:11.126] [WARN] [localhost] [docId] [userId] nodeJS - active connections: 0
[2024-07-28T01:37:11.126] [WARN] [localhost] [docId] [userId] nodeJS - end shutdown
 * Starting PostgreSQL 14 database server                                                                                                                                              [ OK ]
 * Starting RabbitMQ Messaging Server rabbitmq-server                                                                                                                                  [ OK ]
 * Reloading nginx configuration nginx                                                                                                                                                 [ OK ]
Starting supervisor: supervisord.
cron: unrecognized service
 * Starting nginx nginx                                                                                                                                                                [ OK ]
Generating AllFonts.js, please wait...Done
Generating presentation themes, please wait...Done
Generating js caches, please wait...Done
ds:docservice: stopped
ds:docservice: started
ds:converter: stopped
ds:converter: started
 * Reloading nginx configuration nginx                                                                                                                                                 [ OK ]

==> /var/log/onlyoffice/documentserver/converter/err.log <==

==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2024-07-28T01:31:16.292] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:31:49.023] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:31:49.034] [WARN] [localhost] [docId] [userId] nodeJS - worker 821 started.
[2024-07-28T01:31:49.036] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:44:52.759] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:44:52.769] [WARN] [localhost] [docId] [userId] nodeJS - worker 700 started.
[2024-07-28T01:44:52.772] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:45:23.774] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers
[2024-07-28T01:45:23.785] [WARN] [localhost] [docId] [userId] nodeJS - worker 811 started.
[2024-07-28T01:45:23.787] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workers

==> /var/log/onlyoffice/documentserver/docservice/err.log <==

==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2024-07-28T01:31:47.366] [WARN] [localhost] [docId] [userId] nodeJS - Express server listening on port 8000 in production-linux mode. Version: 7.3.3. Build: 49
[2024-07-28T01:37:11.125] [WARN] [localhost] [docId] [userId] nodeJS - start shutdown:%b true
[2024-07-28T01:37:11.126] [WARN] [localhost] [docId] [userId] nodeJS - active connections: 0
[2024-07-28T01:37:11.126] [WARN] [localhost] [docId] [userId] nodeJS - end shutdown
[2024-07-28T01:44:53.260] [WARN] [localhost] [docId] [userId] nodeJS - Express server starting...
[2024-07-28T01:44:53.264] [WARN] [localhost] [docId] [userId] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/do                                                                                                                                             cs/latest/api/fs.html#fs_availability
[2024-07-28T01:44:53.441] [WARN] [localhost] [docId] [userId] nodeJS - Express server listening on port 8000 in production-linux mode. Version: 7.3.3. Build: 49
[2024-07-28T01:45:21.987] [WARN] [localhost] [docId] [userId] nodeJS - Express server starting...
[2024-07-28T01:45:21.990] [WARN] [localhost] [docId] [userId] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/do                                                                                                                                             cs/latest/api/fs.html#fs_availability
[2024-07-28T01:45:22.140] [WARN] [localhost] [docId] [userId] nodeJS - Express server listening on port 8000 in production-linux mode. Version: 7.3.3. Build: 49

==> /var/log/onlyoffice/documentserver/metrics/err.log <==

==> /var/log/onlyoffice/documentserver/metrics/out.log <==
28 Jul 01:31:15 - [661] reading config file: ./config/config.js
28 Jul 01:31:15 - server is up INFO
28 Jul 01:44:52 - [652] reading config file: ./config/config.js
28 Jul 01:44:52 - server is up INFO

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
root@95ab6f946516:/# tail -f /var/log/rabbitmq/*
==> /var/log/rabbitmq/rabbit@95ab6f946516.log <==
2024-07-28 01:31:47.224826+00:00 [info] <0.993.0> accepting AMQP connection <0.993.0> (127.0.0.1:44414 -> 127.0.0.1:5672)
2024-07-28 01:31:47.271207+00:00 [info] <0.993.0> connection <0.993.0> (127.0.0.1:44414 -> 127.0.0.1:5672): user 'guest' authenticated and granted access to vhost '/'
2024-07-28 01:31:47.287604+00:00 [info] <0.1017.0> accepting AMQP connection <0.1017.0> (127.0.0.1:44416 -> 127.0.0.1:5672)
2024-07-28 01:31:47.332136+00:00 [info] <0.1017.0> connection <0.1017.0> (127.0.0.1:44416 -> 127.0.0.1:5672): user 'guest' authenticated and granted access to vhost '/'
2024-07-28 01:31:48.627052+00:00 [warn] <0.930.0> closing AMQP connection <0.930.0> (127.0.0.1:45710 -> 127.0.0.1:5672, vhost: '/', user: 'guest'):
2024-07-28 01:31:48.627052+00:00 [warn] <0.930.0> client unexpectedly closed TCP connection
2024-07-28 01:31:49.718809+00:00 [info] <0.1062.0> accepting AMQP connection <0.1062.0> (127.0.0.1:44428 -> 127.0.0.1:5672)
2024-07-28 01:31:49.764206+00:00 [info] <0.1062.0> connection <0.1062.0> (127.0.0.1:44428 -> 127.0.0.1:5672): user 'guest' authenticated and granted access to vhost '/'
2024-07-28 01:37:11.066140+00:00 [info] <0.1334.0> accepting AMQP connection <0.1334.0> (127.0.0.1:54738 -> 127.0.0.1:5672)
2024-07-28 01:37:11.111302+00:00 [info] <0.1334.0> connection <0.1334.0> (127.0.0.1:54738 -> 127.0.0.1:5672): user 'guest' authenticated and granted access to vhost '/'

==> /var/log/rabbitmq/rabbit@95ab6f946516_upgrade.log <==

==> /var/log/rabbitmq/rabbit@buildkitsandbox.log <==
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     syntax_tools
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     ssl
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     public_key
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     asn1
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     crypto
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     compiler
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     sasl
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     stdlib
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>     kernel
2023-04-10 08:19:57.704414+00:00 [info] <0.728.0>

==> /var/log/rabbitmq/rabbit@buildkitsandbox_upgrade.log <==

==> /var/log/rabbitmq/shutdown_err <==

==> /var/log/rabbitmq/shutdown_log <==
Stopping and halting node rabbit@buildkitsandbox (will monitor pid file /var/run/rabbitmq/pid) ...
process 10196 (take from pid file /var/run/rabbitmq/pid) is no longer running

==> /var/log/rabbitmq/startup_err <==

==> /var/log/rabbitmq/startup_log <==
  Tutorials:   https://rabbitmq.com/getstarted.html
  Monitoring:  https://rabbitmq.com/monitoring.html

  Logs: /var/log/rabbitmq/rabbit@95ab6f946516.log
        /var/log/rabbitmq/rabbit@95ab6f946516_upgrade.log
        <stdout>

  Config file(s): (none)

  Starting broker... completed with 0 plugins.

==> /var/log/rabbitmq/startup_err <==
tail: /var/log/rabbitmq/startup_log: file truncated

==> /var/log/rabbitmq/startup_log <==
2024-07-28 01:44:39.929328+00:00 [info] <0.233.0> Feature flags: list of feature flags found:
2024-07-28 01:44:39.973040+00:00 [info] <0.233.0> Feature flags:   [x] implicit_default_bindings
2024-07-28 01:44:39.973086+00:00 [info] <0.233.0> Feature flags:   [x] maintenance_mode_status
2024-07-28 01:44:39.973118+00:00 [info] <0.233.0> Feature flags:   [x] quorum_queue
2024-07-28 01:44:39.973158+00:00 [info] <0.233.0> Feature flags:   [x] stream_queue
2024-07-28 01:44:39.973286+00:00 [info] <0.233.0> Feature flags:   [x] user_limits
2024-07-28 01:44:39.973315+00:00 [info] <0.233.0> Feature flags:   [x] virtual_host_metadata
2024-07-28 01:44:39.973346+00:00 [info] <0.233.0> Feature flags: feature flag states written to disk: yes

==> /var/log/rabbitmq/rabbit@95ab6f946516.log <==
2024-07-28 01:44:41.187940+00:00 [noti] <0.233.0> Logging: configured log handlers are now ACTIVE

==> /var/log/rabbitmq/startup_log <==
2024-07-28 01:44:41.137945+00:00 [noti] <0.44.0> Application syslog exited with reason: stopped
2024-07-28 01:44:41.138019+00:00 [noti] <0.233.0> Logging: switching to configured handler(s); following messages may not be visible in this log output

==> /var/log/rabbitmq/rabbit@95ab6f946516.log <==
2024-07-28 01:44:49.934747+00:00 [info] <0.233.0> ra: starting system quorum_queues
2024-07-28 01:44:49.934933+00:00 [info] <0.233.0> starting Ra system: quorum_queues in directory: /var/lib/rabbitmq/mnesia/rabbit@95ab6f946516/quorum/rabbit@95ab6f946516
2024-07-28 01:44:49.941783+00:00 [info] <0.434.0> ra: meta data store initialised for system quorum_queues. 0 record(s) recovered
2024-07-28 01:44:49.942310+00:00 [noti] <0.443.0> WAL: ra_log_wal init, open tbls: ra_log_open_mem_tables, closed tbls: ra_log_closed_mem_tables
2024-07-28 01:44:49.975224+00:00 [info] <0.233.0> ra: starting system coordination
2024-07-28 01:44:49.975384+00:00 [info] <0.233.0> starting Ra system: coordination in directory: /var/lib/rabbitmq/mnesia/rabbit@95ab6f946516/coordination/rabbit@95ab6f946516
2024-07-28 01:44:49.981421+00:00 [info] <0.496.0> ra: meta data store initialised for system coordination. 0 record(s) recovered
2024-07-28 01:44:49.981749+00:00 [noti] <0.502.0> WAL: ra_coordination_log_wal init, open tbls: ra_coordination_log_open_mem_tables, closed tbls: ra_coordination_log_closed_mem_tables
2024-07-28 01:44:50.003645+00:00 [info] <0.233.0>
2024-07-28 01:44:50.003645+00:00 [info] <0.233.0>  Starting RabbitMQ 3.9.13 on Erlang 24.2.1 [jit]
2024-07-28 01:44:50.003645+00:00 [info] <0.233.0>  Copyright (c) 2007-2022 VMware, Inc. or its affiliates.
2024-07-28 01:44:50.003645+00:00 [info] <0.233.0>  Licensed under the MPL 2.0. Website: https://rabbitmq.com
2024-07-28 01:44:50.006920+00:00 [info] <0.233.0>
2024-07-28 01:44:50.006920+00:00 [info] <0.233.0>  node           : rabbit@95ab6f946516

Are you trying to run this exact version? I have to stress that it is outdated and no longer supported. I’d recommend to try running latest version of Document Server, which is 8.1.1, to see if it changes the situation.

Thank you for your reply

Now I have updated the only office/document server version.
But it will take about 3 minutes to start and complete

[root@localhost ~]# timedatectl
               Local time: 五 2024-08-02 11:12:30 CST
           Universal time: 五 2024-08-02 03:12:30 UTC
                 RTC time: 五 2024-08-02 03:12:30
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
[root@localhost ~]# docker run -itd -p 80:80 onlyoffice/documentserver
fa3a239ca865391485447aad0e3274784dd33fdd2ddd4e2e1e92460b0cb86690
[root@localhost ~]# docker logs -f fa3a239ca865391485447aad0e3274784dd33fdd2ddd4e2e1e92460b0cb86690
Generating WOPI private key...Done
Generating WOPI public key...Done
 * Starting PostgreSQL 14 database server                                                                                                                                         [ OK ]
 * Starting RabbitMQ Messaging Server rabbitmq-server                                                                                                                             [ OK ]
psql:/var/www/onlyoffice/documentserver/server/schema/postgresql/removetbl.sql:4: NOTICE:  table "doc_callbacks" does not exist, skipping
psql:/var/www/onlyoffice/documentserver/server/schema/postgresql/removetbl.sql:9: NOTICE:  function merge_db(pg_catalog.varchar,int2,int8,pg_catalog.timestamp,pg_catalog.varchar,int8,int8) does not exist, skipping
psql:/var/www/onlyoffice/documentserver/server/schema/postgresql/removetbl.sql:10: NOTICE:  function merge_db(pg_catalog.varchar,int2,int4,pg_catalog.timestamp,pg_catalog.varchar,int4,int4) does not exist, skipping
psql:/var/www/onlyoffice/documentserver/server/schema/postgresql/removetbl.sql:11: NOTICE:  function merge_db(pg_catalog.varchar,int2,int4,pg_catalog.timestamp,int4,int4,text,text) does not exist, skipping
Starting supervisor: supervisord.
 * Starting periodic command scheduler cron                                                                                                                                       [ OK ]
 * Starting nginx nginx                                                                                                                                                           [ OK ]
Generating AllFonts.js, please wait...Done
^Ccontext canceled
[root@localhost ~]# timedatectl
               Local time: 五 2024-08-02 11:15:00 CST
           Universal time: 五 2024-08-02 03:15:00 UTC
                 RTC time: 五 2024-08-02 03:15:01
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
[root@localhost ~]#

Hello @sam123
If you don’t mind, I will join this thread too.
Do I understand it right, that the issue has been resolved? If not, please update us on the current situation.

HI, Alexandre

Most machines will start and complete Onlyoffice within one minute. I don’t think the current problem has been solved. I found that there is a similar issue of long startup time in both CentOS Stream 9 and Rocky8-9 systems. All the systems I have installed are minimal installations and have not been configured with anything else.

Thank you and all the best

Hello @sam123
We have found a bug that is related to RHEL, CentOs and Oracle Linux OS (long docker container startup). We have started working on it. We will update this thread once we have something to share.
Thank you for the valuable data!

Thanks Alexandre for your reply. I will provide any logs or system information you need.

Thank you, we have all necessary information right now. The fix is ​​a matter of time now.

Hello, Alexandre
It has been 8 days, how has it been resolved? I really need relevant solutions.

have a good day, Alexandre

from sam.

Hello @sam123
We’re going to release the fix with the next version of Document server (v.8.2). The release is planned for this autumn.

Hi! Alexandre. Has the latest Docker image fixed the issue?

Hello @sam123
It will be fixed in the v.8.2. The release is planned in 2 weeks.