SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-31 01:48:24 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Homarr broken after update #658

New Issue
Closed
opened 2025-11-20 04:51:46 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:51:46 -05:00
Owner
Copy Link

Originally created by @OptimusGREEN on GitHub (Mar 5, 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 5, 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_
saavagebueno added the bug label 2025-11-20 04:51:46 -05:00
saavagebueno commented 2025-11-20 04:51:47 -05:00
Author
Owner
Copy Link

@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 :)
saavagebueno commented 2025-11-20 04:51:47 -05:00
Author
Owner
Copy Link

@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.
saavagebueno commented 2025-11-20 04:51:47 -05:00
Author
Owner
Copy Link

@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 ```
saavagebueno commented 2025-11-20 04:51:47 -05:00
Author
Owner
Copy Link

@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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#658
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?