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

Homarr error while installing #433

New Issue
Closed
opened 2025-11-20 04:48:27 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:48:27 -05:00
Owner
Copy Link

Originally created by @kimsvane on GitHub (Jan 28, 2025).

✅ 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?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)"

📝 Provide a clear and concise description of the issue.

During install the error which is described in the issue creating is posted.
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run script from proxmox shell

❌ Paste the full error output (if available).

@homarr/nextjs:build:    Creating an optimized production build ...
 ⠹@homarr/nextjs:build: 
@homarr/nextjs:build: <--- Last few GCs --->
@homarr/nextjs:build: 
@homarr/nextjs:build: [8387:0x8167000]    76940 ms: Mark-Compact 984.9 (1049.2) -> 975.2 (1044.1) MB, pooled: 0 MB, 707.27 / 0.00 ms  (average mu = 0.217, current mu = 0.177) allocation failure; GC in old space requested
@homarr/nextjs:build: [8387:0x8167000]    77745 ms: Mark-Compact 975.2 (1044.1) -> 975.2 (1052.1) MB, pooled: 0 MB, 804.31 / 0.00 ms  (average mu = 0.114, current mu = 0.000) allocation failure; GC in old space requested
@homarr/nextjs:build: 
@homarr/nextjs:build: 
@homarr/nextjs:build: <--- JS stacktrace --->
@homarr/nextjs:build: 
@homarr/nextjs:build: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
@homarr/nextjs:build: ----- Native stack trace -----
@homarr/nextjs:build: 
@homarr/nextjs:build:  1: 0xe3811e node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  2: 0x125fb70 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  3: 0x125fe47 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  4: 0x148d885  [node]
@homarr/nextjs:build:  5: 0x148d8b3  [node]
@homarr/nextjs:build:  6: 0x14a696a  [node]
@homarr/nextjs:build:  7: 0x14a9b38  [node]
@homarr/nextjs:build:  8: 0x1ce63d1  [node]
 ⠼@homarr/nextjs:build: Aborted
@homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134.
 ⠴@homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134.
@homarr/nextjs:build: ERROR: command finished with error: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134)
@homarr/nextjs#build: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134)

 Tasks:    4 successful, 5 total
Cached:    0 cached, 5 total
  Time:    1m22.911s 
Failed:    @homarr/nextjs#build

>   ...Finishing writing to cache...                                                                                               WARNING  no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json`
 ERROR  run failed: command  exited (134)
 ELIFECYCLE  Command failed with exit code 134.

[ERROR] in line 63: exit code 0: while executing command $STD pnpm build
root@proxmox:~#

🖼️ Additional context (optional).

No response

Originally created by @kimsvane on GitHub (Jan 28, 2025). ### ✅ 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? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)" ### 📝 Provide a clear and concise description of the issue. During install the error which is described in the issue creating is posted. [ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1 ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run script from proxmox shell ### ❌ Paste the full error output (if available). ``` @homarr/nextjs:build: Creating an optimized production build ... ⠹@homarr/nextjs:build: @homarr/nextjs:build: <--- Last few GCs ---> @homarr/nextjs:build: @homarr/nextjs:build: [8387:0x8167000] 76940 ms: Mark-Compact 984.9 (1049.2) -> 975.2 (1044.1) MB, pooled: 0 MB, 707.27 / 0.00 ms (average mu = 0.217, current mu = 0.177) allocation failure; GC in old space requested @homarr/nextjs:build: [8387:0x8167000] 77745 ms: Mark-Compact 975.2 (1044.1) -> 975.2 (1052.1) MB, pooled: 0 MB, 804.31 / 0.00 ms (average mu = 0.114, current mu = 0.000) allocation failure; GC in old space requested @homarr/nextjs:build: @homarr/nextjs:build: @homarr/nextjs:build: <--- JS stacktrace ---> @homarr/nextjs:build: @homarr/nextjs:build: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory @homarr/nextjs:build: ----- Native stack trace ----- @homarr/nextjs:build: @homarr/nextjs:build: 1: 0xe3811e node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node] @homarr/nextjs:build: 2: 0x125fb70 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node] @homarr/nextjs:build: 3: 0x125fe47 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node] @homarr/nextjs:build: 4: 0x148d885 [node] @homarr/nextjs:build: 5: 0x148d8b3 [node] @homarr/nextjs:build: 6: 0x14a696a [node] @homarr/nextjs:build: 7: 0x14a9b38 [node] @homarr/nextjs:build: 8: 0x1ce63d1 [node] ⠼@homarr/nextjs:build: Aborted @homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134. ⠴@homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134. @homarr/nextjs:build: ERROR: command finished with error: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134) @homarr/nextjs#build: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134) Tasks: 4 successful, 5 total Cached: 0 cached, 5 total Time: 1m22.911s Failed: @homarr/nextjs#build > ...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json` ERROR run failed: command exited (134)  ELIFECYCLE  Command failed with exit code 134. [ERROR] in line 63: exit code 0: while executing command $STD pnpm build root@proxmox:~# ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:48:28 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 28, 2025):

Increase RAM.

@MickLesk commented on GitHub (Jan 28, 2025): Increase RAM.
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
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#433
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?