this post was submitted on 24 Jun 2023
6 points (87.5% liked)

Lemmy Support

4651 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago
MODERATORS
dessalines@lemmy.ml
6
Main PID: 45485 (code=exited, status=203/EXEC) (lemmy.ml)
submitted 2 years ago by DocTator@lemmy.ml to c/lemmy_support@lemmy.ml
8 comments fedilink hide all child comments
 

Hello all, Rather stumped with this one. Trying to install Lemmy, and getting the below error after running systemctl status lemmy ... The full error is below :

 root@lemmy:/etc/systemd# systemctl status lemmy.service
● lemmy.service - Lemmy - A link aggregator for the fediverse
     Loaded: loaded (/etc/systemd/system/lemmy.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2023-06-24 03:03:26 UTC; 28min ago
    Process: 45485 ExecStart=/usr/bin/lemmy_server (code=exited, status=203/EXEC)
   Main PID: 45485 (code=exited, status=203/EXEC)

Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Scheduled restart job, restart counter is at 5.
Jun 24 03:03:26 lemmy systemd[1]: Stopped Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:26 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:27 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.

If anyone could assist, I'd be more than appreciative. So far these logs don't seem to point to where to look for the issue even.

top 8 comments
sorted by: hot top controversial new old
[–] NettoHikari@social.fossware.space 1 points 2 years ago (1 children)

What about:

journalctl -f -u lemmy.service

?

[–] DocTator@lemmy.ml 1 points 2 years ago (1 children) 
doc@lemmy:~$ journalctl -f -u lemmy.service
-- Logs begin at Sat 2023-06-24 01:25:51 UTC. --
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Main process exited, code=exited, status=203/EXEC
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Scheduled restart job, restart counter is at 5.
Jun 24 03:03:26 lemmy systemd[1]: Stopped Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:26 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:27 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.
[–] NettoHikari@social.fossware.space 1 points 2 years ago (1 children)

What happens if you try to run Lemmy without systemd, just to test it out?

So, stop Lemmy first with systemctl stop lemmy.service and then run it directly with /usr/bin/lemmy_server ?

If you don't get sufficient logs, you can also do:

RUST_LOG=info lemmy_server or RUST_LOG=verbose lemmy_server

[–] DocTator@lemmy.ml 1 points 2 years ago (1 children)

it can't even find /usr/bin/lemmy_server to run it... maybe thats where the problem is? lol

[–] NettoHikari@social.fossware.space 1 points 2 years ago

Well, it looks to me that you're doing the install from scratch. So if /usr/bin/lemmy_server is missing, you dungoofed.

[–] RoundSparrow@lemmy.ml 1 points 2 years ago (1 children)

So far these logs don’t seem to point to where to look for the issue even.

i agree, I don't see anything in that log that indicates what is going on.

I don't see any long about database migrations, so maybe it is failing before that logs. How did you install the server, Docker? Is PostgreSQL running and working?

[–] DocTator@lemmy.ml 1 points 2 years ago (1 children)

Server was installed from scratch, but I might try a Docker run just to see if there's any difference. PostgreSQL is up and running :

doc@lemmy:/usr/bin$ systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
     Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sat 2023-06-24 01:41:07 UTC; 23h ago
   Main PID: 25761 (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 4594)
     Memory: 0B
     CGroup: /system.slice/postgresql.service

Jun 24 01:41:07 lemmy systemd[1]: Starting PostgreSQL RDBMS...
Jun 24 01:41:07 lemmy systemd[1]: Finished PostgreSQL RDBMS.
doc@lemmy:/usr/bin$
[–] RoundSparrow@lemmy.ml 1 points 2 years ago

Maybe try the lemmy_server binary interactive? I know there are some environment variables to set