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

Recognize wrong RAM size (update) #159

New Issue
Closed
opened 2025-11-20 04:44:22 -05:00 by saavagebueno · 7 comments
saavagebueno commented 2025-11-20 04:44:22 -05:00
Owner
Copy Link

Originally created by @rkolja76 on GitHub (Dec 7, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Sabnzbd update script (starting install/update script inside the container) does not recognize the amount of the lxc container correctly.

"⚠️ Required: 2 CPU, 2048MB RAM | Current: 8 CPU, MB RAM
Please ensure that the SABnzbd LXC is configured with at least 2 vCPU and 2048 MB RAM for the build process."

grafik

But I have assigned 4 Gigs of RAM to the container.
I have also tried it with the zoraxy install/update script. Same error here. RAM is not recognized by the script.

Any idea?
Thanks guys!

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

grafik

Please provide detailed steps to reproduce the issue.

No response

Originally created by @rkolja76 on GitHub (Dec 7, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. Sabnzbd update script (starting install/update script inside the container) does not recognize the amount of the lxc container correctly. "⚠️ Required: 2 CPU, 2048MB RAM | Current: 8 CPU, MB RAM Please ensure that the SABnzbd LXC is configured with at least 2 vCPU and 2048 MB RAM for the build process." ![grafik](https://github.com/user-attachments/assets/c8e85ca3-aa06-4025-9949-d2175a058e71) But I have assigned 4 Gigs of RAM to the container. I have also tried it with the zoraxy install/update script. Same error here. RAM is not recognized by the script. Any idea? Thanks guys! ### What settings are you currently utilizing? - [X] Default Settings - [ ] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. ![grafik](https://github.com/user-attachments/assets/79d85deb-d261-41c4-b1e7-9a1b0ab9100f) ### Please provide detailed steps to reproduce the issue. _No response_
saavagebueno commented 2025-11-20 04:44:23 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2024):

Something in your lxc is broken. RAM Output is empty

@MickLesk commented on GitHub (Dec 7, 2024): Something in your lxc is broken. RAM Output is empty
saavagebueno commented 2025-11-20 04:44:23 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 7, 2024):

Something in your lxc is broken. RAM Output is empty

The code assumes English language which is not the case here: $(free -m | awk '/^Mem:/{print $2}')

@havardthom commented on GitHub (Dec 7, 2024): > Something in your lxc is broken. RAM Output is empty The code assumes English language which is not the case here: `$(free -m | awk '/^Mem:/{print $2}')`
saavagebueno commented 2025-11-20 04:44:24 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2024):

Puh, okay what language has this LXC?

We can change the function to:
free -m | awk 'NR==2{print $2}'

Can you test this:
echo "Systemmemory: $(free -m | awk 'NR==2{print $2}') MB"

@MickLesk commented on GitHub (Dec 7, 2024): Puh, okay what language has this LXC? We can change the function to: free -m | awk 'NR==2{print $2}' Can you test this: echo "Systemmemory: $(free -m | awk 'NR==2{print $2}') MB"
saavagebueno commented 2025-11-20 04:44:24 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 7, 2024):

The lxc is running in german. Wich is odd i guess?

@michelroegl-brunner commented on GitHub (Dec 7, 2024): The lxc is running in german. Wich is odd i guess?
saavagebueno commented 2025-11-20 04:44:24 -05:00
Author
Owner
Copy Link

@rkolja76 commented on GitHub (Dec 7, 2024):

That's correct - the lxc container is running in german.

grafik

@rkolja76 commented on GitHub (Dec 7, 2024): That's correct - the lxc container is running in german. ![grafik](https://github.com/user-attachments/assets/45a42fd5-afa8-4bb3-a1e8-4d7b47de1ccf)
saavagebueno commented 2025-11-20 04:44:24 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 7, 2024):

Okay i fix it in the next Version of Develop PR

@MickLesk commented on GitHub (Dec 7, 2024): Okay i fix it in the next Version of Develop PR
saavagebueno commented 2025-11-20 04:44:24 -05:00
Author
Owner
Copy Link

@rkolja76 commented on GitHub (Dec 8, 2024):

Thanks a lot!

@rkolja76 commented on GitHub (Dec 8, 2024): Thanks a lot!
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#159
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?