[GH-ISSUE #824] Error when upgrading from 8.x to version 9.x #393

Closed
opened 2026-02-26 10:32:21 +03:00 by kerem · 9 comments
Owner

Originally created by @ovizii on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/824

Originally assigned to: @igwyd on GitHub.

I see this continuously scrolling past in my logs:

Waiting for connection to the localhost host on port 5672

Btw. is there a changelog for the DocumentServer releases available?

Originally created by @ovizii on GitHub (Jul 27, 2025). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/824 Originally assigned to: @igwyd on GitHub. I see this continuously scrolling past in my logs: ` Waiting for connection to the localhost host on port 5672` Btw. is there a changelog for the DocumentServer releases available?
kerem closed this issue 2026-02-26 10:32:21 +03:00
Author
Owner

@igwyd commented on GitHub (Jul 28, 2025):

Hello @ovizii, we have a guide on updating in docker, try using it https://helpcenter.onlyoffice.com/docs/installation/docs-community-update-docker.aspx. You can vew the changelog here https://github.com/ONLYOFFICE/DocumentServer/blob/master/CHANGELOG.md#903

<!-- gh-comment-id:3126995804 --> @igwyd commented on GitHub (Jul 28, 2025): Hello @ovizii, we have a guide on updating in docker, try using it https://helpcenter.onlyoffice.com/docs/installation/docs-community-update-docker.aspx. You can vew the changelog here https://github.com/ONLYOFFICE/DocumentServer/blob/master/CHANGELOG.md#903
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

Thanks a lot for the links. I checked the changelogs and can't see any breaking changes, so not sure where my problem comes when going from 8.x to 9.x

I admit that when I upgrade, I do it like with all other containers: shut down the container, replace the image line say from image: onlyoffice/documentserver:8.2 to image: onlyoffice/documentserver:9.0.1 and do a docker-compose up -d

Do I really need the script:
sudo docker exec {{DOCUMENT_SERVER_ID}} documentserver-prepare4shutdown.sh
since I am the only user?

Apart from that, what I did to upgrade looks right. The volume mapping paths are correct and the same as in the previous version since I didn't touch anything except the image: onlyoffice/documentserver:8.2 line.

Can you tell me anything about the error or warning above:
Waiting for connection to the localhost host on port 5672

Who or what is supposed to connect to this port and how, via the public URL of my DocumentServer or via internal IP?

<!-- gh-comment-id:3131085254 --> @ovizii commented on GitHub (Jul 29, 2025): Thanks a lot for the links. I checked the changelogs and can't see any breaking changes, so not sure where my problem comes when going from 8.x to 9.x I admit that when I upgrade, I do it like with all other containers: shut down the container, replace the image line say from ` image: onlyoffice/documentserver:8.2` to `image: onlyoffice/documentserver:9.0.1` and do a docker-compose up -d Do I really need the script: `sudo docker exec {{DOCUMENT_SERVER_ID}} documentserver-prepare4shutdown.sh` since I am the only user? Apart from that, what I did to upgrade looks right. The volume mapping paths are correct and the same as in the previous version since I didn't touch anything except the `image: onlyoffice/documentserver:8.2` line. Can you tell me anything about the error or warning above: `Waiting for connection to the localhost host on port 5672` Who or what is supposed to connect to this port and how, via the public URL of my DocumentServer or via internal IP?
Author
Owner

@igwyd commented on GitHub (Jul 29, 2025):

Waiting for connection to localhost on port 5672 logs say rabbitmq not starting inside docker container. This can happen, for example, if the container does not have enough resources. Are you following System requirements?

<!-- gh-comment-id:3131164987 --> @igwyd commented on GitHub (Jul 29, 2025): `Waiting for connection to localhost on port 5672` logs say rabbitmq not starting inside docker container. This can happen, for example, if the container does not have enough resources. Are you following [System requirements](https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx)?
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

The current resource limits of the DocumentServer container are:

    cpus: 2
    mem_limit: 4G

The official requirements you linked to state:

CPU: dual core 2 GHz or better
RAM: 4 GB or more
HDD: at least 40 GB of free space
SWAP: at least 4 GB, but depends on the host OS. More is better
OS: amd64 Linux distribution with kernel version 3.10 or later

My host has swapping disabled. I will try once more and simply give the container more RAM to see if that was the problem somehow. Or maybe the CPU limitations are preventing rabbitmq from starting?
I also saw a very old post with a temp fix suggesting: docker exec <name-of-container> service rabbitmq-server restart

I will try all of these ideas one by one and post here again. Thanks for the help so far, lets see what the issue is in the end :-)

<!-- gh-comment-id:3131206512 --> @ovizii commented on GitHub (Jul 29, 2025): The current resource limits of the DocumentServer container are: ``` cpus: 2 mem_limit: 4G ``` The official requirements you linked to state: ``` CPU: dual core 2 GHz or better RAM: 4 GB or more HDD: at least 40 GB of free space SWAP: at least 4 GB, but depends on the host OS. More is better OS: amd64 Linux distribution with kernel version 3.10 or later ``` My host has swapping disabled. I will try once more and simply give the container more RAM to see if that was the problem somehow. Or maybe the CPU limitations are preventing rabbitmq from starting? I also saw a very old post with a temp fix suggesting: `docker exec <name-of-container> service rabbitmq-server restart` I will try all of these ideas one by one and post here again. Thanks for the help so far, lets see what the issue is in the end :-)
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

OK, tried again, no changes yet but since I was quicker checking the logs while starting up I caught this:

 find: ‘/var/www/onlyoffice/Data/certs’: No such file or directory                                                                                                  │
│    * Starting PostgreSQL 16 database server       [80G [74G[ OK ]                                                                                                    │
│    * Starting RabbitMQ Messaging Server rabbitmq-server       [80G  [33m*[0m FAILED - check /var/log/rabbitmq/startup_\{log, _err\}                                  │
│   [74G[[31mfail[0m]                                                                                                                                                  │
│   Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded!                                                                                                │
│   Waiting for connection to the localhost host on port 5672         

checking /var/log/rabbitmq/startup_{log, _err} with docker exec -ti filerun-onlyoffice bash

 cat /var/log/rabbitmq/startup_err

BOOT FAILED
===========
Error during startup: {error,failed_to_initialize_feature_flags_registry}

Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}})

Crash dump is being written to: erl_crash.dump...done

cat /var/log/rabbitmq/startup_log

2025-07-29 08:16:57.399854+00:00 [error] <0.234.0> Feature flags: `classic_mirrored_queue_version`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ.
2025-07-29 08:16:57.412306+00:00 [error] <0.234.0> Failed to initialize feature flags registry: {disabled_required_feature_flag,
2025-07-29 08:16:57.412306+00:00 [error] <0.234.0>                                               classic_mirrored_queue_version}
2025-07-29 08:16:57.429019+00:00 [error] <0.234.0>
2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> BOOT FAILED
2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> ===========
2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> Error during startup: {error,failed_to_initialize_feature_flags_registry}
2025-07-29 08:16:57.429019+00:00 [error] <0.234.0>
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>   crasher:
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     initial call: application_master:init/4
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     pid: <0.233.0>
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     registered_name: []
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     exception exit: {failed_to_initialize_feature_flags_registry,
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>                         {rabbit,start,[normal,[]]}}
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>       in function  application_master:init/4 (application_master.erl, line 142)
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     ancestors: [<0.232.0>]
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     message_queue_len: 1
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     messages: [{'EXIT',<0.234.0>,normal}]
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     links: [<0.232.0>,<0.44.0>]
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     dictionary: []
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     trap_exit: true
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     status: running
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     heap_size: 233
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     stack_size: 28
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>     reductions: 168
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>   neighbours:
2025-07-29 08:16:58.430300+00:00 [error] <0.233.0>
2025-07-29 08:16:58.445905+00:00 [notice] <0.44.0> Application rabbit exited with reason: {failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}}"}

ls -al /var/log/rabbitmq/
total 40
drwxr-xr-x  2 rabbitmq rabbitmq     7 Jul  8 04:04 .
drwxr-xr-x 13 root     root        22 Jul 29 08:16 ..
-rw-r--r--  1 rabbitmq rabbitmq 22151 Jul  8 04:04 rabbit@buildkitsandbox.log
-rw-r--r--  1 root     root         0 Jul  8 04:04 shutdown_err
-rw-r--r--  1 root     root       177 Jul  8 04:04 shutdown_log
-rw-r--r--  1 rabbitmq rabbitmq   315 Jul 29 08:17 startup_err
-rw-r--r--  1 rabbitmq rabbitmq  2640 Jul 29 08:16 startup_log

Any ideas?

<!-- gh-comment-id:3131247835 --> @ovizii commented on GitHub (Jul 29, 2025): OK, tried again, no changes yet but since I was quicker checking the logs while starting up I caught this: ``` find: ‘/var/www/onlyoffice/Data/certs’: No such file or directory │ │ * Starting PostgreSQL 16 database server [80G [74G[ OK ] │ │ * Starting RabbitMQ Messaging Server rabbitmq-server [80G [33m*[0m FAILED - check /var/log/rabbitmq/startup_\{log, _err\} │ │ [74G[[31mfail[0m] │ │ Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded! │ │ Waiting for connection to the localhost host on port 5672 ``` checking /var/log/rabbitmq/startup_\{log, _err\} with `docker exec -ti filerun-onlyoffice bash ` ``` cat /var/log/rabbitmq/startup_err BOOT FAILED =========== Error during startup: {error,failed_to_initialize_feature_flags_registry} Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}}) Crash dump is being written to: erl_crash.dump...done ``` ``` cat /var/log/rabbitmq/startup_log 2025-07-29 08:16:57.399854+00:00 [error] <0.234.0> Feature flags: `classic_mirrored_queue_version`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ. 2025-07-29 08:16:57.412306+00:00 [error] <0.234.0> Failed to initialize feature flags registry: {disabled_required_feature_flag, 2025-07-29 08:16:57.412306+00:00 [error] <0.234.0> classic_mirrored_queue_version} 2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> 2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> BOOT FAILED 2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> =========== 2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> Error during startup: {error,failed_to_initialize_feature_flags_registry} 2025-07-29 08:16:57.429019+00:00 [error] <0.234.0> 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> crasher: 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> initial call: application_master:init/4 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> pid: <0.233.0> 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> registered_name: [] 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> exception exit: {failed_to_initialize_feature_flags_registry, 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> {rabbit,start,[normal,[]]}} 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> in function application_master:init/4 (application_master.erl, line 142) 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> ancestors: [<0.232.0>] 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> message_queue_len: 1 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> messages: [{'EXIT',<0.234.0>,normal}] 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> links: [<0.232.0>,<0.44.0>] 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> dictionary: [] 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> trap_exit: true 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> status: running 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> heap_size: 233 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> stack_size: 28 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> reductions: 168 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> neighbours: 2025-07-29 08:16:58.430300+00:00 [error] <0.233.0> 2025-07-29 08:16:58.445905+00:00 [notice] <0.44.0> Application rabbit exited with reason: {failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}} {"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}}"} ``` ``` ls -al /var/log/rabbitmq/ total 40 drwxr-xr-x 2 rabbitmq rabbitmq 7 Jul 8 04:04 . drwxr-xr-x 13 root root 22 Jul 29 08:16 .. -rw-r--r-- 1 rabbitmq rabbitmq 22151 Jul 8 04:04 rabbit@buildkitsandbox.log -rw-r--r-- 1 root root 0 Jul 8 04:04 shutdown_err -rw-r--r-- 1 root root 177 Jul 8 04:04 shutdown_log -rw-r--r-- 1 rabbitmq rabbitmq 315 Jul 29 08:17 startup_err -rw-r--r-- 1 rabbitmq rabbitmq 2640 Jul 29 08:16 startup_log ``` Any ideas?
Author
Owner

@igwyd commented on GitHub (Jul 29, 2025):

It seems that this is due to the fact that old classic queues are left on the volume https://www.rabbitmq.com/docs/3.13/ha. After stopping the onlyoffice/documentserver 8.2 container, you need to delete the old data:

rm -rf /path/to/rabbitmq/data

or remove the volume if you mounted it like that

docker volume ls  # find volume RabbitMQ
docker volume rm <volume_name>

and then start a new onlyoffice/documentserver 9.0 container.

PS if you are sure that all your documents are saved, then you don’t need to run sudo docker exec {{DOCUMENT_SERVER_ID}} documentserver-prepare4shutdown.sh

<!-- gh-comment-id:3131508939 --> @igwyd commented on GitHub (Jul 29, 2025): It seems that this is due to the fact that old classic queues are left on the volume https://www.rabbitmq.com/docs/3.13/ha. After stopping the onlyoffice/documentserver 8.2 container, you need to delete the old data: ``` rm -rf /path/to/rabbitmq/data ``` or remove the volume if you mounted it like that ``` docker volume ls # find volume RabbitMQ docker volume rm <volume_name> ``` and then start a new onlyoffice/documentserver 9.0 container. PS if you are sure that all your documents are saved, then you don’t need to run `sudo docker exec {{DOCUMENT_SERVER_ID}} documentserver-prepare4shutdown.sh`
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

I assumed that rabbitmg data is located in the volume mounted here:
- ./data/onlyoffice/rabbitmq:/var/lib/rabbitmq

So I deleted the content of that folder and it worked. Thank you so much for the support!

│    * Starting PostgreSQL 16 database server       [80G [74G[ OK ]                                                                                                    │
│    * Starting RabbitMQ Messaging Server rabbitmq-server       [80G [74G[ OK ]                                                                                        │
│   Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded!                                                                                                │
│   Connection to localhost (::1) 5672 port [tcp/amqp] succeeded!                                                                                                      │
│   Starting supervisor: supervisord.                                                                                                                                 
<!-- gh-comment-id:3131634690 --> @ovizii commented on GitHub (Jul 29, 2025): I assumed that rabbitmg data is located in the volume mounted here: ` - ./data/onlyoffice/rabbitmq:/var/lib/rabbitmq ` So I deleted the content of that folder and it worked. **Thank you so much for the support!** ``` │ * Starting PostgreSQL 16 database server [80G [74G[ OK ] │ │ * Starting RabbitMQ Messaging Server rabbitmq-server [80G [74G[ OK ] │ │ Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded! │ │ Connection to localhost (::1) 5672 port [tcp/amqp] succeeded! │ │ Starting supervisor: supervisord. ```
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

Please allow a follow-up question as I have just read the changelogs again and found mentioning of AI - is that also available in this self-hosted community edition? I can't see any AI options anywhere. Not needing this, just checking.

<!-- gh-comment-id:3131722127 --> @ovizii commented on GitHub (Jul 29, 2025): Please allow a follow-up question as I have just read the changelogs again and found mentioning of AI - is that also available in this self-hosted community edition? I can't see any AI options anywhere. Not needing this, just checking.
Author
Owner

@ovizii commented on GitHub (Jul 29, 2025):

Please allow a follow-up question as I have just read the changelogs again and found mentioning of AI - is that also available in this self-hosted community edition? I can't see any AI options anywhere. Not needing this, just checking.

Found the answer here in this video: https://www.onlyoffice.com/blog/2025/06/onlyoffice-docs-9-0-released

You need to enable the AI plugin.

<!-- gh-comment-id:3131734785 --> @ovizii commented on GitHub (Jul 29, 2025): > Please allow a follow-up question as I have just read the changelogs again and found mentioning of AI - is that also available in this self-hosted community edition? I can't see any AI options anywhere. Not needing this, just checking. Found the answer here in this video: https://www.onlyoffice.com/blog/2025/06/onlyoffice-docs-9-0-released **You need to enable the AI plugin.**
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#393
No description provided.