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

Proxmox Backup Server LXC fails to retart after update #1859

New Issue
Closed
opened 2025-11-20 05:18:40 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 05:18:40 -05:00
Owner
Copy Link

Originally created by @emsofo on GitHub (Sep 7, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Proxmox Backup Server LXC

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

After creating a working instance of PBS LXC - and setting it up properly, some updates came up . . . when I tried to update within the PBS interface itself, the updates seemed to have been applied, yet after rebooting the LXC - it hangs.
I then tried to update within the LXC console itself using the script - which also seemed to work - (made a snapshot in advance of course) - same effect - after rebooting the LXC simply hangs and can't use the console or anything. Seems to be running, so I can kill it - but simple shows blank screen and blinking cursor. Something is broke

🔄 Steps to reproduce the issue.

Create PBS using script - set up PBS instance (datastore, post-install script, etc.) - try to update using PBS interface or using script in LXC seems to be applied but LXC fails to reboot

❌ Paste the full error output (if available).

NO error - just doesn't boot - PVE console shows LXC start - that's all

🖼️ Additional context (optional).

No response

Originally created by @emsofo on GitHub (Sep 7, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Proxmox Backup Server LXC ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/proxmox-backup-server.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. After creating a working instance of PBS LXC - and setting it up properly, some updates came up . . . when I tried to update within the PBS interface itself, the updates seemed to have been applied, yet after rebooting the LXC - it hangs. I then tried to update within the LXC console itself using the script - which also seemed to work - (made a snapshot in advance of course) - same effect - after rebooting the LXC simply hangs and can't use the console or anything. Seems to be running, so I can kill it - but simple shows blank screen and blinking cursor. Something is broke ### 🔄 Steps to reproduce the issue. Create PBS using script - set up PBS instance (datastore, post-install script, etc.) - try to update using PBS interface or using script in LXC seems to be applied but LXC fails to reboot ### ❌ Paste the full error output (if available). NO error - just doesn't boot - PVE console shows LXC start - that's all ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:18:40 -05:00
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

And If you start with pct start ? That Sound Like an system issue Not an Script issue

@MickLesk commented on GitHub (Sep 7, 2025): And If you start with pct start ? That Sound Like an system issue Not an Script issue
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@Bartsmet commented on GitHub (Sep 7, 2025):

I have the same issue, tried it several times.

  • Install new LXC proxmox backup server. Script still installs old 3.x version.
  • Run the upgrade script : New version is installed.
  • Try to reboot the container. Container won't boot.
  • Do a manual boot :
    ()
    run_buffer: 571 Script exited with status 25
    lxc_init: 845 Failed to run lxc.hook.pre-start for container "20008"
    __lxc_start: 2034 Failed to initialize container "20008"
    TASK ERROR: startup for container '20008' failed

Edit : I suppose it has something to do with the template used, wich is a different version of debian.

@Bartsmet commented on GitHub (Sep 7, 2025): I have the same issue, tried it several times. - Install new LXC proxmox backup server. Script still installs old 3.x version. - Run the upgrade script : New version is installed. - Try to reboot the container. Container won't boot. - Do a manual boot : () run_buffer: 571 Script exited with status 25 lxc_init: 845 Failed to run lxc.hook.pre-start for container "20008" __lxc_start: 2034 Failed to initialize container "20008" TASK ERROR: startup for container '20008' failed Edit : I suppose it has something to do with the template used, wich is a different version of debian.
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

You mean Upgrade to pbs 4.0? With Debian 13?

@MickLesk commented on GitHub (Sep 7, 2025): You mean Upgrade to pbs 4.0? With Debian 13?
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@emsofo commented on GitHub (Sep 7, 2025):

You mean Upgrade to pbs 4.0? With Debian 13?

Nope - just regular updating from console with script or direct in PBS gui

@emsofo commented on GitHub (Sep 7, 2025): > You mean Upgrade to pbs 4.0? With Debian 13? Nope - just regular updating from console with script or direct in PBS gui
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

Can you Show more Output ?

pct config 20008 | grep -E 'hookscript|unprivileged|features|ostype|template|rootfs'

@MickLesk commented on GitHub (Sep 7, 2025): Can you Show more Output ? pct config 20008 | grep -E 'hookscript|unprivileged|features|ostype|template|rootfs'
saavagebueno commented 2025-11-20 05:18:41 -05:00
Author
Owner
Copy Link

@emsofo commented on GitHub (Sep 9, 2025):

here's mine if that helps:

root@FoxProxMini:~# pct config 113 | grep -E 'hookscript|unprivileged|features|ostype|template|rootfs'
features: keyctl=1,nesting=1
ostype: debian
rootfs: FPMiniThin:vm-113-disk-1,size=10G
unprivileged: 1

@emsofo commented on GitHub (Sep 9, 2025): here's mine if that helps: root@FoxProxMini:~# pct config 113 | grep -E 'hookscript|unprivileged|features|ostype|template|rootfs' features: keyctl=1,nesting=1 ostype: debian rootfs: FPMiniThin:vm-113-disk-1,size=10G unprivileged: 1
saavagebueno commented 2025-11-20 05:18:42 -05:00
Author
Owner
Copy Link

@Bartsmet commented on GitHub (Sep 9, 2025):

I did update today with a new version of pve-container and now it's working!

@Bartsmet commented on GitHub (Sep 9, 2025): I did update today with a new version of pve-container and now it's working!
saavagebueno commented 2025-11-20 05:18:42 -05:00
Author
Owner
Copy Link

@Bartsmet commented on GitHub (Sep 9, 2025):

I think this topic can be closed. Did 2 tests :

  • I was now able to boot the upgraded container from 2 days ago.
  • Creating a fresh backupserver and running the upgrade script works as well, even after a reboot and migration to another cluster host.
@Bartsmet commented on GitHub (Sep 9, 2025): I think this topic can be closed. Did 2 tests : - I was now able to boot the upgraded container from 2 days ago. - Creating a fresh backupserver and running the upgrade script works as well, even after a reboot and migration to another cluster host.
saavagebueno commented 2025-11-20 05:18:42 -05:00
Author
Owner
Copy Link

@R0rit0 commented on GitHub (Sep 9, 2025):

I had the same exact issue, nothing was working
Til I updated the 'pve-container' package on the proxmox server host as mentioned here > Worked perfectly

@R0rit0 commented on GitHub (Sep 9, 2025): I had the same exact issue, nothing was working Til I updated the 'pve-container' package on the proxmox server host as mentioned here > Worked perfectly
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#1859
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?