Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start lemmy_bb #72

Closed
nixoye opened this issue Dec 22, 2022 · 9 comments
Closed

Failed to start lemmy_bb #72

nixoye opened this issue Dec 22, 2022 · 9 comments
Labels
question Further information is requested

Comments

@nixoye
Copy link
Contributor

nixoye commented Dec 22, 2022

Question description

When running systemctl status lemmy_bb.service
I get this error


× lemmy_bb.service - lemmy_bb
     Loaded: loaded (/etc/systemd/system/lemmy_bb.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-12-22 06:22:10 UTC; 1min 4s ago
   Duration: 1ms
    Process: 21008 ExecStart=/opt/lemmyBB/target/release/lemmy_bb (code=exited, status=203/EXEC)
   Main PID: 21008 (code=exited, status=203/EXEC)
        CPU: 960us

Dec 22 06:22:09 g0v systemd[1]: lemmy_bb.service: Main process exited, code=exited, status=203/EXEC
Dec 22 06:22:09 g0v systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
Dec 22 06:22:10 g0v systemd[1]: lemmy_bb.service: Scheduled restart job, restart counter is at 5.
Dec 22 06:22:10 g0v systemd[1]: Stopped lemmy_bb.
Dec 22 06:22:10 g0v systemd[1]: lemmy_bb.service: Start request repeated too quickly.
Dec 22 06:22:10 g0v systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
Dec 22 06:22:10 g0v systemd[1]: Failed to start lemmy_bb
@nixoye nixoye added the question Further information is requested label Dec 22, 2022
@nixoye nixoye changed the title [Question]: Failed to start lemmy_bb Dec 22, 2022
@Tealk
Copy link
Collaborator

Tealk commented Dec 22, 2022

What does the log say?
journalctl -u lemmy_bb.service

@nixoye
Copy link
Contributor Author

nixoye commented Dec 22, 2022

@Tealk

 systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
 systemd[1]: lemmy_bb.service: Scheduled restart job, restart counter is at 3.
 systemd[1]: Stopped lemmy_bb.
 systemd[1]: Started lemmy_bb.
 systemd[1]: lemmy_bb.service: Main process exited, code=exited, status=203/EXEC
systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
systemd[1]: lemmy_bb.service: Scheduled restart job, restart counter is at 4.
systemd[1]: Stopped lemmy_bb.
systemd[1]: Started lemmy_bb.
 systemd[955]: lemmy_bb.service: Failed to locate executable /opt/lemmyBB/target/release/lemmy_bb: No such>
systemd[955]: lemmy_bb.service: Failed at step EXEC spawning /opt/lemmyBB/target/release/lemmy_bb: No suc>
 systemd[1]: lemmy_bb.service: Main process exited, code=exited, status=203/EXEC
ystemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
 systemd[1]: lemmy_bb.service: S

@Nutomic
Copy link
Member

Nutomic commented Dec 22, 2022

Seems like the file /opt/lemmyBB/target/release/lemmy_bb doesnt exist. Did you run cargo build --release? Maybe you used a different folder?

@nixoye
Copy link
Contributor Author

nixoye commented Dec 22, 2022

@Nutomic I did. I followed the instructions step by step. The status number in the error is now 101

systemctl status lemmy_bb.service
× lemmy_bb.service - lemmy_bb
     Loaded: loaded (/etc/systemd/system/lemmy_bb.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-12-22 17:05:47 UTC; 1min 15s ago
   Duration: 7ms
    Process: 1018 ExecStart=/opt/lemmyBB/target/release/lemmy_bb (code=exited, status=101)
   Main PID: 1018 (code=exited, status=101)
        CPU: 3ms

Dec 22 17:05:47 g0v systemd[1]: lemmy_bb.service: Main process exited, code=exited, status=101/n/a
Dec 22 17:05:47 g0v systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
Dec 22 17:05:47 g0v systemd[1]: lemmy_bb.service: Scheduled restart job, restart counter is at 5.
Dec 22 17:05:47 g0v systemd[1]: Stopped lemmy_bb.
Dec 22 17:05:47 g0v systemd[1]: lemmy_bb.service: Start request repeated too quickly.
Dec 22 17:05:47 g0v systemd[1]: lemmy_bb.service: Failed with result 'exit-code'.
Dec 22 17:05:47 g0v systemd[1]: Failed to start lemmy_bb

@Nutomic
Copy link
Member

Nutomic commented Dec 22, 2022

So does the mentioned file exist at that path or not?

@Tealk
Copy link
Collaborator

Tealk commented Dec 22, 2022

Show us the following output
ls -a /opt/lemmyBB/target/release

@nixoye
Copy link
Contributor Author

nixoye commented Dec 22, 2022

sorry, yes it does.

ls -a /opt/lemmyBB/target/release
.   .cargo-lock   build  examples     lemmy_bb
..  .fingerprint  deps   incremental  lemmy_bb.d

@nixoye
Copy link
Contributor Author

nixoye commented Dec 26, 2022

@Nutomic after using the updated instructions for lemmybb i fixed my install on the lemmybb side. My only issue now is this unkown directive error for lemmy

FAILED! => {"changed": true, "cmd": "nginx -s reload", "delta": "0:00:00.046506", "end": "2022-12-26 16:42:11.279902", "msg": "non-zero return code", "rc": 1, "start": "2022-12-26 16:42:11.233396", "stderr": "nginx: [emerg] unknown directive \"sdlimit_req_zone\" in /etc/nginx/sites-enabled/lemmybb.conf.save:1", "stderr_lines": ["nginx: [emerg] unknown directive \"sdlimit_req_zone\" in /etc/nginx/sites-enabled/lemmybb.conf.save:1"], "stdout": "", "stdout_lines": []}

edit: i fixed this error by replacing the lemmybb.conf.save with the .conf by saving and replacing over the conf.save manually

@nixoye nixoye closed this as completed Dec 26, 2022
@Nutomic
Copy link
Member

Nutomic commented Dec 26, 2022

There shouldnt be any .conf.save file, it was probably created by your editor. You can safely delete it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants