I am trying to host my own Lemmy instance. It was running great for awhile. I built the server using the ansible method. When I tried to rebuild the docker containers with ansible last night, I ran into this error.

FAILED! => {“changed”: true, “cmd”: “nginx -s reload”, “delta”: “0:00:00.066477”, “end”: “2023-07-27 23:12:26.216505”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2023-07-27 23:12:26.150028”, “stderr”: “2023/07/27 23:12:26 [notice] 7635#7635: signal process started\n2023/07/27 23:12:26 [error] 7635#7635: open() “/run/nginx.pid” failed (2: No such file or directory)”, “stderr_lines”: [“2023/07/27 23:12:26 [notice] 7635#7635: signal process started”, “2023/07/27 23:12:26 [error] 7635#7635: open() “/run/nginx.pid” failed (2: No such file or directory)”], “stdout”: “”, “stdout_lines”: []}

Any ideas?

  • dan@upvote.auEnglish
    7·
    11 months ago

    This is an Nginx error, not a Lemmy error. The PID file (which contains the process ID of the current main Nginx instance) was missing. My guess is that it tried to tell Nginx to reload its config, but Nginx wasn’t running at the time. Try starting Nginx (or the Nginx container) and see if that works.

  • nbailey@lemmy.caEnglish
    11·
    11 months ago

    It looks like it’s not able to reload the service. Could be permissions? As the nginx user (www-data often), try touch /run/nginx.pid

    • dan@upvote.auEnglish
      1·
      11 months ago

      If it was permissions, then it’d say “permission denied”, not “no such file or directory”.

      • nbailey@lemmy.caEnglish
        1·
        11 months ago

        Generally speaking, yes, but things can get a little weird when you’re dealing with an abstraction like docker.