[GH-ISSUE #792] OnlyOffice DocumentServer won't start after commit 0de5714 (5th Feb 2025)

kerem commented

2026-02-26 10:32:10 +03:00

Owner

Originally created by @HomelabHaven on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/792

Originally assigned to: @igwyd on GitHub.

Docker logs on attempted start

Starting PostgreSQL 16 database server

...done.

Starting RabbitMQ Messaging Server rabbitmq-server

FAILED - check /var/log/rabbitmq/startup_{log, _err}

...fail!
Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded!
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

The waiting continues indefinitely. I have not made any changes to my Nextcloud & OnlyOffice setup in the last year.

Originally created by @HomelabHaven on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/792 Originally assigned to: @igwyd on GitHub. Docker logs on attempted start > * Starting PostgreSQL 16 database server > > ...done. > > * Starting RabbitMQ Messaging Server rabbitmq-server > > * FAILED - check /var/log/rabbitmq/startup_\{log, _err\} > > ...fail! > Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded! > 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 The waiting continues indefinitely. I have not made any changes to my Nextcloud & OnlyOffice setup in the last year.

kerem closed this issue

2026-02-26 10:32:10 +03:00

kerem commented

2026-02-26 10:32:11 +03:00

Author

Owner

@iPCNet commented on GitHub (Feb 6, 2025):

Same issue here

Also running in docker:

root@9c2c584c0e5f:/# /bin/bash /app/ds/run-document-server.sh
 * Starting PostgreSQL 16 database server                                                                                                                                                                                                                                                                                                       [ OK ] 
 * Starting RabbitMQ Messaging Server rabbitmq-server                                                                                                                                                                                                                                                                                                   * FAILED - check /var/log/rabbitmq/startup_\{log, _err\}
                                                                                                                                                                                                                                                                                                                                                [fail]
Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded!
Waiting for connection to the localhost host on port 5672
Waiting for connection to the localhost host on port 5672
^CPreparing for shutdown, it can take a lot of time, please wait...Done

From /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

from /var/log/rabbitmq/startup_log:

2025-02-06 19:31:25.100775+00:00 [error] <0.230.0> Feature flags: `classic_mirrored_queue_version`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ.
2025-02-06 19:31:25.113919+00:00 [error] <0.230.0> Failed to initialize feature flags registry: {disabled_required_feature_flag,
2025-02-06 19:31:25.113919+00:00 [error] <0.230.0>                                               classic_mirrored_queue_version}
2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> 
2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> BOOT FAILED
2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> ===========
2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> Error during startup: {error,failed_to_initialize_feature_flags_registry}
2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> 
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>   crasher:
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     initial call: application_master:init/4
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     pid: <0.229.0>
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     registered_name: []
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     exception exit: {failed_to_initialize_feature_flags_registry,
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>                         {rabbit,start,[normal,[]]}}
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>       in function  application_master:init/4 (application_master.erl, line 142)
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     ancestors: [<0.228.0>]
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     message_queue_len: 1
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     messages: [{'EXIT',<0.230.0>,normal}]
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     links: [<0.228.0>,<0.44.0>]
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     dictionary: []
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     trap_exit: true
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     status: running
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     heap_size: 233
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     stack_size: 28
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>     reductions: 168
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0>   neighbours:
2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> 
2025-02-06 19:31:26.138687+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,[]]}}}"}

Not sure.... but:

Feature flags: classic_mirrored_queue_version: required feature flag not enabled! It must be enabled before upgrading RabbitMQ.

Seems to be the issue

@iPCNet commented on GitHub (Feb 6, 2025): Same issue here Also running in docker: ``` root@9c2c584c0e5f:/# /bin/bash /app/ds/run-document-server.sh * Starting PostgreSQL 16 database server [ OK ] * Starting RabbitMQ Messaging Server rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_\{log, _err\} [fail] Connection to localhost (::1) 5432 port [tcp/postgresql] succeeded! Waiting for connection to the localhost host on port 5672 Waiting for connection to the localhost host on port 5672 ^CPreparing for shutdown, it can take a lot of time, please wait...Done ``` From /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 ``` from /var/log/rabbitmq/startup_log: ``` 2025-02-06 19:31:25.100775+00:00 [error] <0.230.0> Feature flags: `classic_mirrored_queue_version`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ. 2025-02-06 19:31:25.113919+00:00 [error] <0.230.0> Failed to initialize feature flags registry: {disabled_required_feature_flag, 2025-02-06 19:31:25.113919+00:00 [error] <0.230.0> classic_mirrored_queue_version} 2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> 2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> BOOT FAILED 2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> =========== 2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> Error during startup: {error,failed_to_initialize_feature_flags_registry} 2025-02-06 19:31:25.124498+00:00 [error] <0.230.0> 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> crasher: 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> initial call: application_master:init/4 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> pid: <0.229.0> 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> registered_name: [] 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> exception exit: {failed_to_initialize_feature_flags_registry, 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> {rabbit,start,[normal,[]]}} 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> in function application_master:init/4 (application_master.erl, line 142) 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> ancestors: [<0.228.0>] 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> message_queue_len: 1 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> messages: [{'EXIT',<0.230.0>,normal}] 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> links: [<0.228.0>,<0.44.0>] 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> dictionary: [] 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> trap_exit: true 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> status: running 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> heap_size: 233 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> stack_size: 28 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> reductions: 168 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> neighbours: 2025-02-06 19:31:26.125477+00:00 [error] <0.229.0> 2025-02-06 19:31:26.138687+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,[]]}}}"} ``` Not sure.... but: > Feature flags: `classic_mirrored_queue_version`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ. Seems to be the issue

kerem commented

2026-02-26 10:32:11 +03:00

Author

Owner

@FelixBuehler commented on GitHub (Feb 8, 2025):

I can confirm this issue.

@FelixBuehler commented on GitHub (Feb 8, 2025): I can confirm this issue.

kerem commented

2026-02-26 10:32:11 +03:00

Author

Owner

@igwyd commented on GitHub (Feb 10, 2025):

Hello @HomelabHaven, provide the steps to reproduse please. I don't get any errors when I run the container or build it using a dockerfile.

@igwyd commented on GitHub (Feb 10, 2025): Hello @HomelabHaven, provide the steps to reproduse please. I don't get any errors when I run the container or build it using a dockerfile.

kerem commented

2026-02-26 10:32:11 +03:00

Author

Owner

@jonas0b1011001 commented on GitHub (Feb 10, 2025):

I had the same problem, removing the 'old' docker network resolved it for me.

@jonas0b1011001 commented on GitHub (Feb 10, 2025): I had the same problem, removing the 'old' docker network resolved it for me.

kerem commented

2026-02-26 10:32:11 +03:00

Author

Owner

@iPCNet commented on GitHub (Feb 10, 2025):

Following docker compose was used:

volumes:
  onlyoffice:
  onlylog:
  onlytype:
  onlylib:
  onlysql:
  onlyrmq:
  onlyredis:
    
services:
   onlyoffice:
     image: onlyoffice/documentserver:latest
     restart: always
     volumes:
      - onlyoffice:/var/www/onlyoffice/Data
      - onlylog:/var/log/onlyoffice
      - onlytype:/usr/share/fonts/truetype/custom
      - onlylib:/var/lib/onlyoffice
      - onlysql:/var/lib/postgresql
      - onlyrmq:/var/lib/rabbitmq
      - onlyredis:/var/lib/redis
     environment:
     - JWT_ENABLED=true
     - JWT_SECRET=${jwt_sec}

     labels:
        - "traefik.enable=true"
        - "traefik.http.routers.onlyoffice.tls=true"
        - "traefik.http.routers.onlyoffice.tls.certresolver=production"
        - "traefik.http.routers.onlyoffice.entrypoints=websecure"
        - "traefik.http.routers.onlyoffice.rule=Host(`***removed***`)"
        - "traefik.http.middlewares.onlyoffice-headers.headers.customResponseHeaders.X-Robots-Tag=none"
        - "traefik.http.middlewares.onlyoffice-headers.headers.customResponseHeaders.Strict-Transport-Security=max-age=63072000"
        - "traefik.http.middlewares.onlyoffice-headers.headers.browserXssFilter=true"
        - "traefik.http.middlewares.onlyoffice-headers.headers.contentTypeNosniff=true"
        - "traefik.http.middlewares.onlyoffice-headers.headers.stsIncludeSubdomains=true"
        - "traefik.http.middlewares.onlyoffice-headers.headers.stsPreload=true"
        - "traefik.http.middlewares.onlyoffice-headers.headers.stsSeconds=31536000"
        - "traefik.http.middlewares.onlyoffice-headers.headers.forceSTSHeader=true"
        - "traefik.http.middlewares.onlyoffice-headers.headers.accessControlMaxAge=15552000"
        - "traefik.http.middlewares.onlyoffice-headers.headers.customrequestheaders.X-Forwarded-Proto=https"
        - "traefik.http.middlewares.onlyoffice-headers.headers.accesscontrolalloworiginlist=*"
        - "traefik.http.routers.onlyoffice.middlewares=onlyoffice-headers"

networks:
  default:
    name: traefik_default

I purged all the volumes to get a "fresh start" -> works now. I thinks the issue occures when upgrading, since the RabbitMQ configs are persistent in a volume. Could explain the missing feature flag... but just a theory

@iPCNet commented on GitHub (Feb 10, 2025): Following docker compose was used: ``` volumes: onlyoffice: onlylog: onlytype: onlylib: onlysql: onlyrmq: onlyredis: services: onlyoffice: image: onlyoffice/documentserver:latest restart: always volumes: - onlyoffice:/var/www/onlyoffice/Data - onlylog:/var/log/onlyoffice - onlytype:/usr/share/fonts/truetype/custom - onlylib:/var/lib/onlyoffice - onlysql:/var/lib/postgresql - onlyrmq:/var/lib/rabbitmq - onlyredis:/var/lib/redis environment: - JWT_ENABLED=true - JWT_SECRET=${jwt_sec} labels: - "traefik.enable=true" - "traefik.http.routers.onlyoffice.tls=true" - "traefik.http.routers.onlyoffice.tls.certresolver=production" - "traefik.http.routers.onlyoffice.entrypoints=websecure" - "traefik.http.routers.onlyoffice.rule=Host(`***removed***`)" - "traefik.http.middlewares.onlyoffice-headers.headers.customResponseHeaders.X-Robots-Tag=none" - "traefik.http.middlewares.onlyoffice-headers.headers.customResponseHeaders.Strict-Transport-Security=max-age=63072000" - "traefik.http.middlewares.onlyoffice-headers.headers.browserXssFilter=true" - "traefik.http.middlewares.onlyoffice-headers.headers.contentTypeNosniff=true" - "traefik.http.middlewares.onlyoffice-headers.headers.stsIncludeSubdomains=true" - "traefik.http.middlewares.onlyoffice-headers.headers.stsPreload=true" - "traefik.http.middlewares.onlyoffice-headers.headers.stsSeconds=31536000" - "traefik.http.middlewares.onlyoffice-headers.headers.forceSTSHeader=true" - "traefik.http.middlewares.onlyoffice-headers.headers.accessControlMaxAge=15552000" - "traefik.http.middlewares.onlyoffice-headers.headers.customrequestheaders.X-Forwarded-Proto=https" - "traefik.http.middlewares.onlyoffice-headers.headers.accesscontrolalloworiginlist=*" - "traefik.http.routers.onlyoffice.middlewares=onlyoffice-headers" networks: default: name: traefik_default ``` I purged all the volumes to get a "fresh start" -> works now. I thinks the issue occures when upgrading, since the RabbitMQ configs are persistent in a volume. Could explain the missing feature flag... but just a theory

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@FelixBuehler commented on GitHub (Feb 10, 2025):

For me, it looks like this:

services:
  mariadb:
    image: mariadb:jammy
    ...
      
  redis:
    image: redis
    ...
      
  nextcloud:
    image: nextcloud
    ...
    
  cron:
   image: nextcloud:apache
  ...
   
  onlyoffice-documentserver:
    image: onlyoffice/documentserver:latest
    container_name: onlyoffice-documentserver
    ports:
     - 32772:443
     - 32771:80
    environment:
      - JWT_SECRET=...
    restart: unless-stopped

@FelixBuehler commented on GitHub (Feb 10, 2025): For me, it looks like this: ``` services: mariadb: image: mariadb:jammy ... redis: image: redis ... nextcloud: image: nextcloud ... cron: image: nextcloud:apache ... onlyoffice-documentserver: image: onlyoffice/documentserver:latest container_name: onlyoffice-documentserver ports: - 32772:443 - 32771:80 environment: - JWT_SECRET=... restart: unless-stopped ```

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@iPCNet commented on GitHub (Feb 10, 2025):

If I am not mistaken the container will create the volumes itself if not assigned:

github.com/ONLYOFFICE/Docker-DocumentServer@0de571477f/Dockerfile (L136)

Check:
docker inspect -f '{{ .Mounts }}' CONTAINERID
-> ContainerID of your onlyoffice-documentserver

When there is no persistent setup intended (so not to use it as a standalone instance and just as a nextcloud plugin), then I would try to delete the volumes used by onlyoffice-documentserver and redeploy the stack.

It's not an elegant solution or fix, but it should suffice as a workaround.

@iPCNet commented on GitHub (Feb 10, 2025): If I am not mistaken the container will create the volumes itself if not assigned: https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/0de571477f205b99bdf149678a5fb5b9f08f1457/Dockerfile#L136 Check: `docker inspect -f '{{ .Mounts }}' CONTAINERID` -> ContainerID of your onlyoffice-documentserver When there is no persistent setup intended (so not to use it as a standalone instance and just as a nextcloud plugin), then I would try to delete the volumes used by `onlyoffice-documentserver` and redeploy the stack. It's not an elegant solution or fix, but it should suffice as a workaround.

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@HomelabHaven commented on GitHub (Feb 10, 2025):

Hello @HomelabHaven, provide the steps to reproduse please. I don't get any errors when I run the container or build it using a dockerfile.

Hi,

here is the relevant part of my portainer stack for the onlyoffice documentserver:

onlyoffice:
image: onlyoffice/documentserver
container_name: onlyoffice
hostname: onlyoffice
environment:
- "JWT_SECRET=removed"
volumes:
- /home/serveradmin/docker/onlyoffice/logs:/var/log/onlyoffice
- /home/serveradmin/docker/onlyoffice/data:/var/www/onlyoffice/Data
- /home/serveradmin/docker/onlyoffice/cache:/var/lib/onlyoffice
- /home/serveradmin/docker/onlyoffice/rabbitmq:/var/lib/rabbitmq
- /home/serveradmin/docker/onlyoffice/redis:/var/lib/redis
- /home/serveradmin/docker/onlyoffice/db:/var/lib/postgresql
networks:
- onlyoffice
ports:
- 3213:80
restart: unless-stopped
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost"]
interval: 10s
timeout: 10s
retries: 3
start_period: 60s
start_interval: 30s
labels:
- com.centurylinklabs.watchtower.enable=true
- docker-volume-backup.stop-during-backup=true

networks:
onlyoffice:
driver: bridge
name: onlyoffice

@HomelabHaven commented on GitHub (Feb 10, 2025): > Hello [@HomelabHaven](https://github.com/HomelabHaven), provide the steps to reproduse please. I don't get any errors when I run the container or build it using a dockerfile. Hi, here is the relevant part of my portainer stack for the onlyoffice documentserver: > onlyoffice: > image: onlyoffice/documentserver > container_name: onlyoffice > hostname: onlyoffice > environment: > - "JWT_SECRET=*removed*" > volumes: > - /home/serveradmin/docker/onlyoffice/logs:/var/log/onlyoffice > - /home/serveradmin/docker/onlyoffice/data:/var/www/onlyoffice/Data > - /home/serveradmin/docker/onlyoffice/cache:/var/lib/onlyoffice > - /home/serveradmin/docker/onlyoffice/rabbitmq:/var/lib/rabbitmq > - /home/serveradmin/docker/onlyoffice/redis:/var/lib/redis > - /home/serveradmin/docker/onlyoffice/db:/var/lib/postgresql > networks: > - onlyoffice > ports: > - 3213:80 > restart: unless-stopped > healthcheck: > test: ["CMD", "curl", "-f", "http://localhost"] > interval: 10s > timeout: 10s > retries: 3 > start_period: 60s > start_interval: 30s > labels: > - com.centurylinklabs.watchtower.enable=true > - docker-volume-backup.stop-during-backup=true > > networks: > onlyoffice: > driver: bridge > name: onlyoffice

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@FelixBuehler commented on GitHub (Feb 10, 2025):

Check: docker inspect -f '{{ .Mounts }}' CONTAINERID -> ContainerID of your onlyoffice-documentserver

This results in this:

[{
        volume a3a346663e67f4f4dfde5b73fc753effc00723982f1295e740ab89b71447a3fb / volume1 /  @ docker / volumes / a3a346663e67f4f4dfde5b73fc753effc00723982f1295e740ab89b71447a3fb / _data / usr / share / fonts / truetype / custom local z true
    } {
        volume c9e77c456d211c433de8254a3f63d068c5932f7de7838f79a510d8d9b0768441 / volume1 /  @ docker / volumes / c9e77c456d211c433de8254a3f63d068c5932f7de7838f79a510d8d9b0768441 / _data / var / lib / onlyoffice local z true
    } {
        volume b780f7a29ca72989924b04b9b9b503f0fcd550a61de02a7f4a8f1e50241e6fd0 / volume1 /  @ docker / volumes / b780f7a29ca72989924b04b9b9b503f0fcd550a61de02a7f4a8f1e50241e6fd0 / _data / var / lib / postgresql local z true
    } {
        volume ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546 / volume1 /  @ docker / volumes / ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546 / _data / var / lib / rabbitmq local z true
    } {
        volume 2840aac469e014bbb4c668d3feab23cab79f2567f9d4e5f5f409f61a61caa3d5 / volume1 /  @ docker / volumes / 2840aac469e014bbb4c668d3feab23cab79f2567f9d4e5f5f409f61a61caa3d5 / _data / var / lib / redis local z true
    } {
        volume fe60009a59315497379d2e5c82c4021d5a00532087336bcd9c87a96711329b36 / volume1 /  @ docker / volumes / fe60009a59315497379d2e5c82c4021d5a00532087336bcd9c87a96711329b36 / _data / var / log / onlyoffice local z true
    } {
        volume 427db207fbc05b0a9abb6dfadf6a03aef9217ef27dd901a416213e8cb3196e66 / volume1 /  @ docker / volumes / 427db207fbc05b0a9abb6dfadf6a03aef9217ef27dd901a416213e8cb3196e66 / _data / var / www / onlyoffice / Data local z true
    }
]

Can I safely delete all of them, when having not any data in onlyoffice?

@FelixBuehler commented on GitHub (Feb 10, 2025): > Check: `docker inspect -f '{{ .Mounts }}' CONTAINERID` -> ContainerID of your onlyoffice-documentserver This results in this: ``` [{ volume a3a346663e67f4f4dfde5b73fc753effc00723982f1295e740ab89b71447a3fb / volume1 / @ docker / volumes / a3a346663e67f4f4dfde5b73fc753effc00723982f1295e740ab89b71447a3fb / _data / usr / share / fonts / truetype / custom local z true } { volume c9e77c456d211c433de8254a3f63d068c5932f7de7838f79a510d8d9b0768441 / volume1 / @ docker / volumes / c9e77c456d211c433de8254a3f63d068c5932f7de7838f79a510d8d9b0768441 / _data / var / lib / onlyoffice local z true } { volume b780f7a29ca72989924b04b9b9b503f0fcd550a61de02a7f4a8f1e50241e6fd0 / volume1 / @ docker / volumes / b780f7a29ca72989924b04b9b9b503f0fcd550a61de02a7f4a8f1e50241e6fd0 / _data / var / lib / postgresql local z true } { volume ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546 / volume1 / @ docker / volumes / ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546 / _data / var / lib / rabbitmq local z true } { volume 2840aac469e014bbb4c668d3feab23cab79f2567f9d4e5f5f409f61a61caa3d5 / volume1 / @ docker / volumes / 2840aac469e014bbb4c668d3feab23cab79f2567f9d4e5f5f409f61a61caa3d5 / _data / var / lib / redis local z true } { volume fe60009a59315497379d2e5c82c4021d5a00532087336bcd9c87a96711329b36 / volume1 / @ docker / volumes / fe60009a59315497379d2e5c82c4021d5a00532087336bcd9c87a96711329b36 / _data / var / log / onlyoffice local z true } { volume 427db207fbc05b0a9abb6dfadf6a03aef9217ef27dd901a416213e8cb3196e66 / volume1 / @ docker / volumes / 427db207fbc05b0a9abb6dfadf6a03aef9217ef27dd901a416213e8cb3196e66 / _data / var / www / onlyoffice / Data local z true } ] ``` Can I safely delete all of them, when having not any data in onlyoffice?

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@KeenMaron commented on GitHub (Feb 10, 2025):

same issue, just wanted to update and nothing works :(

@KeenMaron commented on GitHub (Feb 10, 2025): same issue, just wanted to update and nothing works :(

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@iPCNet commented on GitHub (Feb 10, 2025):

@FelixBuehler
We just use it for Nextcloud. The documents are stored there. I deleted everything... quick and dirty!
If you have custom fonts or stuff like that, then maybe not. Just try removing the rabbitmq volume first.
In your case it's the volume ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546

@iPCNet commented on GitHub (Feb 10, 2025): @FelixBuehler We just use it for Nextcloud. The documents are stored there. I deleted everything... quick and dirty! If you have custom fonts or stuff like that, then maybe not. Just try removing the rabbitmq volume first. In your case it's the volume `ae976ade4eb33868fe315e52e14c79f2812f220558e29cd8484d521b69cfb546`

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@FelixBuehler commented on GitHub (Feb 10, 2025):

Thanks that worked. So, conclusion for everyone having the same issue (and has not defined a separate volume!):

docker inspect -f '{{ .Mounts }}' CONTAINER_ID

Look for the rabbit_mq volume, then stop the volume and
docker volume rm RABBIT_MQ_VOLUME_ID

@FelixBuehler commented on GitHub (Feb 10, 2025): Thanks that worked. So, conclusion for everyone having the same issue (and has not defined a separate volume!): `docker inspect -f '{{ .Mounts }}' CONTAINER_ID` Look for the rabbit_mq volume, then stop the volume and `docker volume rm RABBIT_MQ_VOLUME_ID`

kerem commented

2026-02-26 10:32:12 +03:00

Author

Owner

@HomelabHaven commented on GitHub (Feb 10, 2025):

I deleted all files and directories recursively in my rabbitmq docker volume (bind mount to be exact) and can confirm that it starts up again.
Thank you all for the input and help.

@HomelabHaven commented on GitHub (Feb 10, 2025): I deleted all files and directories recursively in my rabbitmq docker volume (bind mount to be exact) and can confirm that it starts up again. Thank you all for the input and help.

Rows
Columns

[GH-ISSUE #792] OnlyOffice DocumentServer won't start after commit 0de5714 (5th Feb 2025) #367

[GH-ISSUE #792] OnlyOffice DocumentServer won't start after commit `0de5714` (5th Feb 2025) #367