[GH-ISSUE #836] mkdir: cannot create directory /var/run/rabbitmq': Permission denied #405

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

Originally created by @foreverlover1991 on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/836

Linux system:Lihux zdzntpt 4.19.90-52.52.v2207.ky10.x86 64 #3 SMP Thu Sep 25 07:18:35 UTC 2025 X86 64 X86 64 X86 64 GNU/LInUX
office version:7.1.1
docker version:24
command:sudo docker run -i -t -d -p 8080:80 onlyoffice/documentserver:7.1.1

launch log:

  • Starting PostgreSQL 12 database server [ OK ]
  • Starting RabbitMQ Messaging Server rabbitmq-server
  • FAILED - check /var/log/rabbitmq/startup_{log, _err} [fail]

/var/log/rabbitmq/startup_err

mkdir: cannot create directory /var/run/rabbitmq': Permission denied

Running directly on Linux zdzntpt 4.19.90-52.22.v2207.ky10.x86_64 #3 SMP Thu Sep 25 07:18:35 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux works without any issues, but this problem occurs specifically on this system when running inside a container.

After executing the container startup command and immediately entering the container, we observed the following:
The rabbitmq directory is first created, then quickly deleted.
Simultaneously, the error is thrown:
FAILED - check /var/log/rabbitmq/startup_{log,_err}                                                                                                                                                                                                                                                           ......[fail]
At no point is a PID file ever created.
Additionally, no super...pid file is found under /var/run.

Originally created by @foreverlover1991 on GitHub (Nov 21, 2025). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/836 Linux system:Lihux zdzntpt 4.19.90-52.52.v2207.ky10.x86 64 #3 SMP Thu Sep 25 07:18:35 UTC 2025 X86 64 X86 64 X86 64 GNU/LInUX office version:7.1.1 docker version:24 command:sudo docker run -i -t -d -p 8080:80 onlyoffice/documentserver:7.1.1 launch log: * Starting PostgreSQL 12 database server [ OK ] * Starting RabbitMQ Messaging Server rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_\{log, _err\} [fail] /var/log/rabbitmq/startup_err mkdir: cannot create directory /var/run/rabbitmq': Permission denied Running directly on Linux zdzntpt 4.19.90-52.22.v2207.ky10.x86_64 #3 SMP Thu Sep 25 07:18:35 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux works without any issues, but this problem occurs specifically on this system when running inside a container. After executing the container startup command and immediately entering the container, we observed the following: The rabbitmq directory is first created, then quickly deleted. Simultaneously, the error is thrown: FAILED - check /var/log/rabbitmq/startup_{log,_err}                                                                                                                                                                                                                                                           ......[fail] At no point is a PID file ever created. Additionally, no super...pid file is found under /var/run.
kerem closed this issue 2026-02-26 10:32:24 +03:00
Author
Owner

@foreverlover1991 commented on GitHub (Nov 21, 2025):

The reason for RabbitMQ startup failure remains unknown.

After starting the container and entering it, the following files were changed to have 644 permissions:
/etc/onlyoffice/documentserver/local.json
/etc/onlyoffice/documentserver/log4js/production.json

Then, the following commands were executed:
bash
usermod -s /bin/bash rabbitmq # Change the login shell for the rabbitmq user
su rabbitmq # Switch to the rabbitmq user
rabbitmq-server # Start RabbitMQ manually

With the above steps, DocumentServer functions normally.

However, the root cause of the failure when launching the container directly via Docker has still not been identified.

<!-- gh-comment-id:3561874734 --> @foreverlover1991 commented on GitHub (Nov 21, 2025): The reason for RabbitMQ startup failure remains unknown. After starting the container and entering it, the following files were changed to have 644 permissions: /etc/onlyoffice/documentserver/local.json /etc/onlyoffice/documentserver/log4js/production.json Then, the following commands were executed: bash usermod -s /bin/bash rabbitmq # Change the login shell for the rabbitmq user su rabbitmq # Switch to the rabbitmq user rabbitmq-server # Start RabbitMQ manually With the above steps, DocumentServer functions normally. However, the root cause of the failure when launching the container directly via Docker has still not been identified.
Author
Owner

@igwyd commented on GitHub (Nov 24, 2025):

Hello @foreverlover1991, describe your issue in English please. I noticed you're using an old version that's not supported. Try the new version of the documentserver 9.1.0.

<!-- gh-comment-id:3569089533 --> @igwyd commented on GitHub (Nov 24, 2025): Hello @foreverlover1991, describe your issue in English please. I noticed you're using an old version that's not supported. Try the new version of the documentserver 9.1.0.
Author
Owner

@foreverlover1991 commented on GitHub (Dec 3, 2025):

Hello @foreverlover1991, describe your issue in English please. I noticed you're using an old version that's not supported. Try the new version of the documentserver 9.1.0.

We must use this version, as changing the component's version could introduce further compatibility issues.

<!-- gh-comment-id:3605643437 --> @foreverlover1991 commented on GitHub (Dec 3, 2025): > Hello [@foreverlover1991](https://github.com/foreverlover1991), describe your issue in English please. I noticed you're using an old version that's not supported. Try the new version of the documentserver 9.1.0. We must use this version, as changing the component's version could introduce further compatibility issues.
Author
Owner

@igwyd commented on GitHub (Dec 5, 2025):

We support the current version of our product and recommend updat. Your issue most likely has been fixed in new version.

<!-- gh-comment-id:3616499972 --> @igwyd commented on GitHub (Dec 5, 2025): We support the current version of our product and recommend updat. Your issue most likely has been fixed in new version.
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#405
No description provided.