Error: The directory named as part of the path /var/run/supervisord/supervisord.pid does not exist

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Not sure - aio-nextcloud:latest
  • Operating system and version (e.g., Ubuntu 24.04):
    • Debian 12 - dockge LXC on Proxmox
  • Web server and version (e.g, Apache 2.4.25):
    • Not sure
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Cosmos cloud 0.23.4
  • PHP version (e.g, 8.3):
    • replace me
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • Several days ago
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

Nextcloud is unavailable, and appears to be stalled waiting for nginx to start.

Nginx is failing to start with this error:

Connection to nextcloud-aio-nextcloud (172.21.0.7) 9000 port [tcp/*] succeeded!
nextcloud aio Error: The directory named as part of the path /var/run/supervisord/supervisord.pid does not exist

Steps to replicate it (hint: details matter!):

  1. Apologies but I do not know.

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

I guess this is related to the update to Nextcloud AIO 14.1.1 which changed some references to how the apache mounts /run and loses the visibility of supervisord.

In this Nextcloud AIO 14.1.1 version it assumes an apache more recent version, but since the apache container with older version is still running, it never gets updated.

i’ve managed to fix this by going directly to the Nextcloud AIO interface at
local-IP-address:8080

Since the mastercontainer is stuck, there is a message in the AIO interface instructing to run a sudo command:
“sudo docker exec nextcloud-aio-mastercontainer rm /mnt/docker-aio-config/data/daily_backup_running”

Run that command, then STOP all containers and after that push “Update and start containers”.

At that point it will update the nextcloud-aio-apache container image to the latest, it will take quite some time to backup the whole thing, and then start all nextcloud containers successfully.

I fixed my Nextcloud AIO in this way!

But it would have been good a heads-up from the AIO update for this.