2.3.0~ynh1 service dies immediately and causes 502 Bad Gateway

[silverhook]

I upgraded to 2.3.0~ynh1 and got 502 Bad Gateway.

After checking with the Tools↦Services it turns out borgwarehouse.service exits immediately after it’s started.

LOGFILE: journalctl
-- Journal begins at Fri 2023-12-29 00:37:14 CET, ends at Wed 2024-05-15 09:36:26 CEST. --
May 15 09:32:15 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:32:15 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:32:15 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 5.
May 15 09:32:15 systemd[1]: Stopped BorgWarehouse.
May 15 09:32:15 systemd[1]: borgwarehouse.service: Start request repeated too quickly.
May 15 09:32:15 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:32:15 systemd[1]: Failed to start BorgWarehouse.
May 15 09:36:23 systemd[1]: Started BorgWarehouse.
May 15 09:36:24 npm[528998]: > borgwarehouse@2.3.0 start
May 15 09:36:24 npm[528998]: > next start
May 15 09:36:24 npm[529050]: sh: 1: next: not found
May 15 09:36:24 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:36:24 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:24 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 1.
May 15 09:36:24 systemd[1]: Stopped BorgWarehouse.
May 15 09:36:24 systemd[1]: Started BorgWarehouse.
May 15 09:36:24 npm[529067]: > borgwarehouse@2.3.0 start
May 15 09:36:24 npm[529067]: > next start
May 15 09:36:24 npm[529078]: sh: 1: next: not found
May 15 09:36:24 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:36:24 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:24 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 2.
May 15 09:36:24 systemd[1]: Stopped BorgWarehouse.
May 15 09:36:24 systemd[1]: Started BorgWarehouse.
May 15 09:36:25 npm[529080]: > borgwarehouse@2.3.0 start
May 15 09:36:25 npm[529080]: > next start
May 15 09:36:25 npm[529091]: sh: 1: next: not found
May 15 09:36:25 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:36:25 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:25 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 3.
May 15 09:36:25 systemd[1]: Stopped BorgWarehouse.
May 15 09:36:25 systemd[1]: Started BorgWarehouse.
May 15 09:36:25 npm[529092]: > borgwarehouse@2.3.0 start
May 15 09:36:25 npm[529092]: > next start
May 15 09:36:25 npm[529103]: sh: 1: next: not found
May 15 09:36:25 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:36:25 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:25 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 4.
May 15 09:36:25 systemd[1]: Stopped BorgWarehouse.
May 15 09:36:25 systemd[1]: Started BorgWarehouse.
May 15 09:36:26 npm[529104]: > borgwarehouse@2.3.0 start
May 15 09:36:26 npm[529104]: > next start
May 15 09:36:26 npm[529115]: sh: 1: next: not found
May 15 09:36:26 systemd[1]: borgwarehouse.service: Main process exited, code=exited, status=127/n/a
May 15 09:36:26 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:26 systemd[1]: borgwarehouse.service: Scheduled restart job, restart counter is at 5.
May 15 09:36:26 systemd[1]: Stopped BorgWarehouse.
May 15 09:36:26 systemd[1]: borgwarehouse.service: Start request repeated too quickly.
May 15 09:36:26 systemd[1]: borgwarehouse.service: Failed with result 'exit-code'.
May 15 09:36:26 systemd[1]: Failed to start BorgWarehouse.

[Limezy]

You upgraded from which version ? It's probably a problem with the upgrade script. On my side I did an installation from scratch and everything is fine.

[Limezy]

Should be fixed on testing branch, I let you try. The part where the app was built was missing 🤣

[silverhook]

I think I upgraded from 2.2.0 (“stable”)

The part where the app was built was missing 🤣

LOL, happens :rofl:

[silverhook]

I just tried to upgrade from testing, but it said it’s already up-to-date, so I went ahead and un-installed it and simply (re-)installed testing. That seems to have worked.

There are some other issues I found, I’ll log them separately.

[Limezy]

Next time you can upgrade with the --force option

[silverhook]

I guess we can close this now?