starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

NocoDB failing after update #2440

New Issue
Open
opened 2026-02-05 04:52:01 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 04:52:01 +03:00
Owner
Copy Link

Originally created by @sirLeone on GitHub (Feb 3, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

NocoDB

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.16

📝 Provide a clear and concise description of the issue.

Updated LXC container with NocoDB causes high CPU load (90%) and failing to open nocodb'startpage.

Current version of NocoDB - (0.301.2)

🔄 Steps to reproduce the issue.

Updating process went without any errors. Just typed "update" hit enter, selected "2 YES verbose mode".

❌ Paste the full error output (if available).

Website is not loading

🖼️ Additional context (optional).

No response

Originally created by @sirLeone on GitHub (Feb 3, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? NocoDB ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.16 ### 📝 Provide a clear and concise description of the issue. Updated LXC container with NocoDB causes high CPU load (90%) and failing to open nocodb'startpage. Current version of NocoDB - (0.301.2) ### 🔄 Steps to reproduce the issue. Updating process went without any errors. Just typed "update" hit enter, selected "2 YES verbose mode". ### ❌ Paste the full error output (if available). Website is not loading ### 🖼️ Additional context (optional). _No response_
OVERLORD added the question🛑 Failure to comply with the guidelines labels 2026-02-05 04:52:01 +03:00
OVERLORD commented 2026-02-05 04:52:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2026):

where is the output? you checked verbose output, but never add this lines?

Service Output? Add more CPU? Maybe migrations are running? Its an static x64 File from there repo. So i think you should collect all informations and create an issue at nocodb.

@MickLesk commented on GitHub (Feb 3, 2026): where is the output? you checked verbose output, but never add this lines? Service Output? Add more CPU? Maybe migrations are running? Its an static x64 File from there repo. So i think you should collect all informations and create an issue at nocodb.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label question 🛑 Failure to comply with the guidelines
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2440
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?