SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-26 18:12:11 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

n8n update can fail due to too low disk space #1814

New Issue
Closed
opened 2025-11-20 05:17:50 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:17:50 -05:00
Owner
Copy Link

Originally created by @radry on GitHub (Aug 29, 2025).

✅ Have you read and understood the above guidelines?

yes

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

n8n

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/n8n.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.4.9/649acf70aab54798 (running kernel: 6.8.12-13-pve)

📝 Provide a clear and concise description of the issue.

When trying to update n8n it can fail with following error:

[ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n

I suspected it's due to too low free disk space because after increasing the disk size the update worked fine.
The strange thing is that there was still at least 1GB free of the default 6GB...

I have only 3 small workflows in n8n and run into this issue, so I think 6GB disk size is way too small for practical use.

Thus I suggest increasing the default disk size of the script to 10GB and/or a safeguard in the script to ensure enough free space.

🔄 Steps to reproduce the issue.

  1. Have Default setup of n8n
  2. Free disk space less than 1GB
  3. run "update"

❌ Paste the full error output (if available).

[ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n

🖼️ Additional context (optional).

No response

Originally created by @radry on GitHub (Aug 29, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? n8n ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/n8n.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.4.9/649acf70aab54798 (running kernel: 6.8.12-13-pve) ### 📝 Provide a clear and concise description of the issue. When trying to update n8n it can fail with following error: `[ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n` I suspected it's due to too low free disk space because after increasing the disk size the update worked fine. The strange thing is that there was still at least 1GB free of the default 6GB... I have only 3 small workflows in n8n and run into this issue, so I think 6GB disk size is way too small for practical use. Thus I suggest increasing the default disk size of the script to 10GB and/or a safeguard in the script to ensure enough free space. ### 🔄 Steps to reproduce the issue. 1) Have Default setup of n8n 2) Free disk space less than 1GB 3) run "update" ### ❌ Paste the full error output (if available). [ERROR] in line 44: exit code 0: while executing command $STD npm update -g n8n ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:17:50 -05:00
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#1814
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?