Selfhosted

40368 readers

373 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Lemmy Instance: /run/nginx.pid" failed (2: No such file or directory) (self.selfhosted)

submitted 1 year ago by starkcommando to c/selfhosted

4 comments fedilink hide all child comments

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?

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 7 points 1 year 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.

[–] [email protected] 0 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

If it was permissions, then it'd say "permission denied", not "no such file or directory".

[–] [email protected] 1 points 1 year ago

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