Homarr broken after update #597

Closed
opened 2026-02-04 20:15:25 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @OptimusGREEN on GitHub (Mar 6, 2025).

Originally assigned to: @CrazyWolf13 on GitHub.

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

homarr

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

homarr doesn't seem to run following a seemingly succesful update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

run update command

Paste the full error output (if available).

× homarr.service - Homarr Service
     Loaded: loaded (/etc/systemd/system/homarr.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-03-05 22:14:55 GMT; 5min ago
   Duration: 398ms
    Process: 127 ExecStart=/opt/run_homarr.sh (code=exited, status=1/FAILURE)
   Main PID: 127 (code=exited, status=1/FAILURE)
        CPU: 313ms

Mar 05 22:14:55 homarr run_homarr.sh[156]:     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
Mar 05 22:14:55 homarr run_homarr.sh[156]:     at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
Mar 05 22:14:55 homarr run_homarr.sh[156]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
Mar 05 22:14:55 homarr run_homarr.sh[156]:     at node:internal/main/run_main_module:36:49 {
Mar 05 22:14:55 homarr run_homarr.sh[156]:   code: 'MODULE_NOT_FOUND',
Mar 05 22:14:55 homarr run_homarr.sh[156]:   requireStack: []
Mar 05 22:14:55 homarr run_homarr.sh[156]: }
Mar 05 22:14:55 homarr run_homarr.sh[156]: Node.js v22.14.0
Mar 05 22:14:55 homarr systemd[1]: homarr.service: Main process exited, code=exited, status=1/FAILURE
Mar 05 22:14:55 homarr systemd[1]: homarr.service: Failed with result 'exit-code'.
root@homarr:~# systemctl start homarr
root@homarr:~# systemctl status homarr
× homarr.service - Homarr Service
     Loaded: loaded (/etc/systemd/system/homarr.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-03-05 22:20:12 GMT; 2s ago
   Duration: 277ms
    Process: 1083 ExecStart=/opt/run_homarr.sh (code=exited, status=1/FAILURE)
   Main PID: 1083 (code=exited, status=1/FAILURE)
        CPU: 302ms

Mar 05 22:20:12 homarr run_homarr.sh[1102]:     at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
Mar 05 22:20:12 homarr run_homarr.sh[1102]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
Mar 05 22:20:12 homarr run_homarr.sh[1102]:     at node:internal/main/run_main_module:36:49 {
Mar 05 22:20:12 homarr run_homarr.sh[1102]:   code: 'MODULE_NOT_FOUND',
Mar 05 22:20:12 homarr run_homarr.sh[1102]:   requireStack: []
Mar 05 22:20:12 homarr run_homarr.sh[1102]: }
Mar 05 22:20:12 homarr run_homarr.sh[1102]: Node.js v22.14.0
Mar 05 22:20:12 homarr run_homarr.sh[1101]: Node.js v22.14.0

🖼️ Additional context (optional).

No response

Originally created by @OptimusGREEN on GitHub (Mar 6, 2025). Originally assigned to: @CrazyWolf13 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? homarr ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. homarr doesn't seem to run following a seemingly succesful update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. run update command ### ❌ Paste the full error output (if available). ``` × homarr.service - Homarr Service Loaded: loaded (/etc/systemd/system/homarr.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-03-05 22:14:55 GMT; 5min ago Duration: 398ms Process: 127 ExecStart=/opt/run_homarr.sh (code=exited, status=1/FAILURE) Main PID: 127 (code=exited, status=1/FAILURE) CPU: 313ms Mar 05 22:14:55 homarr run_homarr.sh[156]: at TracingChannel.traceSync (node:diagnostics_channel:322:14) Mar 05 22:14:55 homarr run_homarr.sh[156]: at wrapModuleLoad (node:internal/modules/cjs/loader:220:24) Mar 05 22:14:55 homarr run_homarr.sh[156]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) Mar 05 22:14:55 homarr run_homarr.sh[156]: at node:internal/main/run_main_module:36:49 { Mar 05 22:14:55 homarr run_homarr.sh[156]: code: 'MODULE_NOT_FOUND', Mar 05 22:14:55 homarr run_homarr.sh[156]: requireStack: [] Mar 05 22:14:55 homarr run_homarr.sh[156]: } Mar 05 22:14:55 homarr run_homarr.sh[156]: Node.js v22.14.0 Mar 05 22:14:55 homarr systemd[1]: homarr.service: Main process exited, code=exited, status=1/FAILURE Mar 05 22:14:55 homarr systemd[1]: homarr.service: Failed with result 'exit-code'. root@homarr:~# systemctl start homarr root@homarr:~# systemctl status homarr × homarr.service - Homarr Service Loaded: loaded (/etc/systemd/system/homarr.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-03-05 22:20:12 GMT; 2s ago Duration: 277ms Process: 1083 ExecStart=/opt/run_homarr.sh (code=exited, status=1/FAILURE) Main PID: 1083 (code=exited, status=1/FAILURE) CPU: 302ms Mar 05 22:20:12 homarr run_homarr.sh[1102]: at wrapModuleLoad (node:internal/modules/cjs/loader:220:24) Mar 05 22:20:12 homarr run_homarr.sh[1102]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) Mar 05 22:20:12 homarr run_homarr.sh[1102]: at node:internal/main/run_main_module:36:49 { Mar 05 22:20:12 homarr run_homarr.sh[1102]: code: 'MODULE_NOT_FOUND', Mar 05 22:20:12 homarr run_homarr.sh[1102]: requireStack: [] Mar 05 22:20:12 homarr run_homarr.sh[1102]: } Mar 05 22:20:12 homarr run_homarr.sh[1102]: Node.js v22.14.0 Mar 05 22:20:12 homarr run_homarr.sh[1101]: Node.js v22.14.0 ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:15:25 +03:00
Author
Owner

@CrazyWolf13 commented on GitHub (Mar 6, 2025):

Hi
Please reboot the LXC, I'll look into why this does not happen automatically :)

@CrazyWolf13 commented on GitHub (Mar 6, 2025): Hi Please reboot the LXC, I'll look into why this does not happen automatically :)
Author
Owner

@OptimusGREEN commented on GitHub (Mar 6, 2025):

Hi, I did reboot but that error was still there. I rolled back a snapshot to get back up and running though, so I'll hold off.

@OptimusGREEN commented on GitHub (Mar 6, 2025): Hi, I did reboot but that error was still there. I rolled back a snapshot to get back up and running though, so I'll hold off.
Author
Owner

@CrazyWolf13 commented on GitHub (Mar 6, 2025):

@OptimusGREEN Hmm weird, normally that should fix it.

With the new updated merged, could you test it again?

And possibly send the contents of the following if it still fails?

journalctl -u homarr | tail -n 100
cat /opt/homarr/run_homarr.sh
@CrazyWolf13 commented on GitHub (Mar 6, 2025): @OptimusGREEN Hmm weird, normally that should fix it. With the new updated merged, could you test it again? And possibly send the contents of the following if it still fails? ```bash journalctl -u homarr | tail -n 100 cat /opt/homarr/run_homarr.sh ```
Author
Owner

@OptimusGREEN commented on GitHub (Mar 6, 2025):

It worked fine, great work. maybe a glitch or something last time.

Thank you.

@OptimusGREEN commented on GitHub (Mar 6, 2025): It worked fine, great work. maybe a glitch or something last time. Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#597