starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Error in build.func #829

New Issue
Closed
opened 2026-02-04 21:47:06 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 21:47:06 +03:00
Owner
Copy Link

Originally created by @kiwinh0 on GitHub (Apr 18, 2025).

📌 Task summary

Sustained consumption suggests that the process is stuck

📋 Task details

After conducting a study to determine why I was experiencing parasitic power consumption, I discovered that, for a few days now, new instances using the scripts were generating parasitic power consumption. (Confirmed in the Jellyfin LXC and Debian LXC scripts.)
The possible causes discovered within my limited knowledge are:

# Section where the crash occurs (in the build.func file)
if [[ ! -d /var ]]; then
msg_error "No ${APP} Installation Found!"
exit
fi

Process:
root 1552882 11.9 0.0 8376 3456 ? S 09:49 37:11 bash -c #!/usr/bin/env bash source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func) # Copyright (c) 2021-2025 tteck # Author: tteck (tteckster) # License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE # Source: https://www.debian.org/ APP="Debian" var_tags="${var_tags:-os}" var_cpu="${var_cpu:-1}" var_ram="${var_ram:-512}" var_disk="${var_disk:-2}" var_os="${var_os:-debian}" var_version="${var_version:-12}" var_unprivileged="${var_unprivileged:-1}" header_info "$APP" variables color catch_errors function update_script() { header_info check_container_storage check_container_resources if [[ ! -d /var ]]; then msg_error "No ${APP} Installation Found!" exit fi msg_info "Updating $APP LXC" $STD apt-get update $STD apt-get -y upgrade msg_ok "Updated $APP LXC" exit } start build_container description msg_ok "Completed Successfully!\n" echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"

Originally created by @kiwinh0 on GitHub (Apr 18, 2025). ### 📌 Task summary Sustained consumption suggests that the process is stuck ### 📋 Task details After conducting a study to determine why I was experiencing parasitic power consumption, I discovered that, for a few days now, new instances using the scripts were generating parasitic power consumption. (Confirmed in the Jellyfin LXC and Debian LXC scripts.) The possible causes discovered within my limited knowledge are: ``` # Section where the crash occurs (in the build.func file) if [[ ! -d /var ]]; then msg_error "No ${APP} Installation Found!" exit fi ``` Process: `root 1552882 11.9 0.0 8376 3456 ? S 09:49 37:11 bash -c #!/usr/bin/env bash source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func) # Copyright (c) 2021-2025 tteck # Author: tteck (tteckster) # License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE # Source: https://www.debian.org/ APP="Debian" var_tags="${var_tags:-os}" var_cpu="${var_cpu:-1}" var_ram="${var_ram:-512}" var_disk="${var_disk:-2}" var_os="${var_os:-debian}" var_version="${var_version:-12}" var_unprivileged="${var_unprivileged:-1}" header_info "$APP" variables color catch_errors function update_script() { header_info check_container_storage check_container_resources if [[ ! -d /var ]]; then msg_error "No ${APP} Installation Found!" exit fi msg_info "Updating $APP LXC" $STD apt-get update $STD apt-get -y upgrade msg_ok "Updated $APP LXC" exit } start build_container description msg_ok "Completed Successfully!\n" echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"`
OVERLORD commented 2026-02-04 21:47:20 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 18, 2025):

Use https://github.com/community-scripts/ProxmoxVE/issues/new?template=bug_report.yml since i can't see what your issue is.

@tremor021 commented on GitHub (Apr 18, 2025): Use https://github.com/community-scripts/ProxmoxVE/issues/new?template=bug_report.yml since i can't see what your issue is.
OVERLORD commented 2026-02-04 21:47:32 +03:00
Author
Owner
Copy Link

@kiwinh0 commented on GitHub (Apr 18, 2025):

Thank you @tremor021 , I had my doubts as it was something general and not explicitly referring to a service script.
Solution:

kill -15 1552882 # Clean termination
# If it persists:
kill -9 1552882 # Forced termination

A restart of proxmox and it's fixed.

@kiwinh0 commented on GitHub (Apr 18, 2025): Thank you @tremor021 , I had my doubts as it was something general and not explicitly referring to a service script. Solution: ``` kill -15 1552882 # Clean termination # If it persists: kill -9 1552882 # Forced termination ``` A restart of proxmox and it's fixed.
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
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#829
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?