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 13 Packages Projects Releases 10 Wiki Activity

Privilege converter - backup succeeded AND failed #1098

New Issue
Closed
opened 2026-02-04 23:03:53 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 23:03:53 +03:00
Owner
Copy Link

Originally created by @Stooovie on GitHub (Jun 14, 2025).

✅ Have you read and understood the above guidelines?

yes

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

PVE Privilege Converter

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/pve-privilege-converter.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

I run the command, pick a LXC, the last lines say:

INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-108-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 108 (00:08:59)
INFO: Backup finished at 2025-06-14 19:02:26
INFO: Backup job finished successfully
INFO: notified via target `proxmobo-webhook`
INFO: notified via target `mail-to-root`
  ✖️   Backup failed

and the script stops. There's 700 GB free on my Proxmox Backup Server, the entire NC is 90 GB. There is no other indication of any error, but the script fails.

🔄 Steps to reproduce the issue.

Step 1: run Privilege Converter on a Nextcloud LXC
Step 2: it fails

❌ Paste the full error output (if available).

📦 Backing up container 108
INFO: starting new backup job: vzdump 108 --compress zstd --mode snapshot --storage pbs
INFO: Starting Backup of VM 108 (lxc)
INFO: Backup started at 2025-06-14 18:53:27
INFO: status = running
INFO: CT Name: nc
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "snap_vm-108-disk-0_vzdump" created.
WARNING: Sum of all thin volume sizes (1.61 TiB) exceeds the size of thin pool storage/storage and the size of whole volume group (931.51 GiB).
INFO: creating Proxmox Backup Server archive 'ct/108/2025-06-14T16:53:27Z'
INFO: set max number of entries in memory for file-based backups to 1048576
INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp1438267_108/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 108 --backup-time 1749920007 --entries-max 1048576 --repository root@pam@192.168.0.199:usbbackup
INFO: Starting backup: ct/108/2025-06-14T16:53:27Z
INFO: Client name: pve
INFO: Starting backup protocol: Sat Jun 14 18:53:27 2025
INFO: Downloading previous manifest (Sat Jun 14 18:42:36 2025)
INFO: Upload config file '/var/tmp/vzdumptmp1438267_108/etc/vzdump/pct.conf' to 'root@pam@192.168.0.199:8007:usbbackup' as pct.conf.blob
INFO: Upload directory '/mnt/vzsnap0' to 'root@pam@192.168.0.199:8007:usbbackup' as root.pxar.didx
INFO: processed 10.489 GiB in 1m, uploaded 6.326 MiB
INFO: processed 20.179 GiB in 2m, uploaded 6.326 MiB
INFO: processed 30.362 GiB in 3m, uploaded 6.326 MiB
INFO: processed 39.161 GiB in 4m, uploaded 103.551 MiB
INFO: processed 48.748 GiB in 5m, uploaded 103.551 MiB
INFO: processed 60.681 GiB in 6m, uploaded 103.551 MiB
INFO: processed 71.327 GiB in 7m, uploaded 103.551 MiB
INFO: processed 81.744 GiB in 8m, uploaded 103.551 MiB
INFO: root.pxar: had to backup 170.26 MiB of 93.636 GiB (compressed 25.11 MiB) in 535.82 s (average 325.385 KiB/s)
INFO: root.pxar: backup was done incrementally, reused 93.47 GiB (99.8%)
INFO: Uploaded backup catalog (14.807 MiB)
INFO: Duration: 536.54s
INFO: End Time: Sat Jun 14 19:02:24 2025
INFO: prune older backups with retention: keep-daily=2, keep-monthly=1
INFO: running 'proxmox-backup-client prune' for 'ct/108'
INFO: pruned 1 backup(s) not covered by keep-retention policy
INFO: cleanup temporary 'vzdump' snapshot
Logical volume "snap_vm-108-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 108 (00:08:59)
INFO: Backup finished at 2025-06-14 19:02:26
INFO: Backup job finished successfully
INFO: notified via target proxmobo-webhook
INFO: notified via target mail-to-root
✖️ Backup failed

🖼️ Additional context (optional).

No response

Originally created by @Stooovie on GitHub (Jun 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? PVE Privilege Converter ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/pve-privilege-converter.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. I run the command, pick a LXC, the last lines say: ``` INFO: cleanup temporary 'vzdump' snapshot Logical volume "snap_vm-108-disk-0_vzdump" successfully removed. INFO: Finished Backup of VM 108 (00:08:59) INFO: Backup finished at 2025-06-14 19:02:26 INFO: Backup job finished successfully INFO: notified via target `proxmobo-webhook` INFO: notified via target `mail-to-root` ✖️ Backup failed ``` and the script stops. There's 700 GB free on my Proxmox Backup Server, the entire NC is 90 GB. There is no other indication of any error, but the script fails. ### 🔄 Steps to reproduce the issue. Step 1: run Privilege Converter on a Nextcloud LXC Step 2: it fails ### ❌ Paste the full error output (if available). 📦 Backing up container 108 INFO: starting new backup job: vzdump 108 --compress zstd --mode snapshot --storage pbs INFO: Starting Backup of VM 108 (lxc) INFO: Backup started at 2025-06-14 18:53:27 INFO: status = running INFO: CT Name: nc INFO: including mount point rootfs ('/') in backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: create storage snapshot 'vzdump' WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full. Logical volume "snap_vm-108-disk-0_vzdump" created. WARNING: Sum of all thin volume sizes (1.61 TiB) exceeds the size of thin pool storage/storage and the size of whole volume group (931.51 GiB). INFO: creating Proxmox Backup Server archive 'ct/108/2025-06-14T16:53:27Z' INFO: set max number of entries in memory for file-based backups to 1048576 INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp1438267_108/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 108 --backup-time 1749920007 --entries-max 1048576 --repository root@pam@192.168.0.199:usbbackup INFO: Starting backup: ct/108/2025-06-14T16:53:27Z INFO: Client name: pve INFO: Starting backup protocol: Sat Jun 14 18:53:27 2025 INFO: Downloading previous manifest (Sat Jun 14 18:42:36 2025) INFO: Upload config file '/var/tmp/vzdumptmp1438267_108/etc/vzdump/pct.conf' to 'root@pam@192.168.0.199:8007:usbbackup' as pct.conf.blob INFO: Upload directory '/mnt/vzsnap0' to 'root@pam@192.168.0.199:8007:usbbackup' as root.pxar.didx INFO: processed 10.489 GiB in 1m, uploaded 6.326 MiB INFO: processed 20.179 GiB in 2m, uploaded 6.326 MiB INFO: processed 30.362 GiB in 3m, uploaded 6.326 MiB INFO: processed 39.161 GiB in 4m, uploaded 103.551 MiB INFO: processed 48.748 GiB in 5m, uploaded 103.551 MiB INFO: processed 60.681 GiB in 6m, uploaded 103.551 MiB INFO: processed 71.327 GiB in 7m, uploaded 103.551 MiB INFO: processed 81.744 GiB in 8m, uploaded 103.551 MiB INFO: root.pxar: had to backup 170.26 MiB of 93.636 GiB (compressed 25.11 MiB) in 535.82 s (average 325.385 KiB/s) INFO: root.pxar: backup was done incrementally, reused 93.47 GiB (99.8%) INFO: Uploaded backup catalog (14.807 MiB) INFO: Duration: 536.54s INFO: End Time: Sat Jun 14 19:02:24 2025 INFO: prune older backups with retention: keep-daily=2, keep-monthly=1 INFO: running 'proxmox-backup-client prune' for 'ct/108' INFO: pruned 1 backup(s) not covered by keep-retention policy INFO: cleanup temporary 'vzdump' snapshot Logical volume "snap_vm-108-disk-0_vzdump" successfully removed. INFO: Finished Backup of VM 108 (00:08:59) INFO: Backup finished at 2025-06-14 19:02:26 INFO: Backup job finished successfully INFO: notified via target `proxmobo-webhook` INFO: notified via target `mail-to-root` ✖️ Backup failed ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 23:03:53 +03:00
OVERLORD commented 2026-02-04 23:03:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 14, 2025):

You has Run into LXC or Host?

@MickLesk commented on GitHub (Jun 14, 2025): You has Run into LXC or Host?
OVERLORD commented 2026-02-04 23:04:05 +03:00
Author
Owner
Copy Link

@Stooovie commented on GitHub (Jun 14, 2025):

Host, as instructed.

@Stooovie commented on GitHub (Jun 14, 2025): Host, as instructed.
OVERLORD commented 2026-02-04 23:04:09 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 14, 2025):

Ah you save to PBS? Its developed for local storages. I dont have pbs at Test, i can develop an Feature/fix but you need to test it

@MickLesk commented on GitHub (Jun 14, 2025): Ah you save to PBS? Its developed for local storages. I dont have pbs at Test, i can develop an Feature/fix but you need to test it
OVERLORD commented 2026-02-04 23:04:14 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 14, 2025):

Can you try the develop Script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/tools/pve/pve-privilege-converter.sh)"
@MickLesk commented on GitHub (Jun 14, 2025): Can you try the develop Script? ```bash bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/tools/pve/pve-privilege-converter.sh)"
OVERLORD commented 2026-02-04 23:04:16 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 16, 2025):

@Stooovie can you test it please?

@MickLesk commented on GitHub (Jun 16, 2025): @Stooovie can you test it please?
OVERLORD commented 2026-02-04 23:04:21 +03:00
Author
Owner
Copy Link

@Stooovie commented on GitHub (Jun 16, 2025):

Doesn't work, here's the last few lines:

Suggested next free container ID: 102. Enter new container ID [default: 102]: 
🛠️ Restoring as privileged container
recovering backed-up configuration from 'ct/115/2025-06-16T15:33:59Z'
unable to restore CT 102 - can't find file 'ct/115/2025-06-16T15:33:59Z'

I was backing up to PBS (that is successful) and restoring to the original storage pool with a new ID.

@Stooovie commented on GitHub (Jun 16, 2025): Doesn't work, here's the last few lines: ``` Suggested next free container ID: 102. Enter new container ID [default: 102]: 🛠️ Restoring as privileged container recovering backed-up configuration from 'ct/115/2025-06-16T15:33:59Z' unable to restore CT 102 - can't find file 'ct/115/2025-06-16T15:33:59Z' ``` I was backing up to PBS (that is successful) and restoring to the original storage pool with a new ID.
OVERLORD commented 2026-02-04 23:04:26 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 16, 2025):

Then i can deploy tomorrow another Version, but you need to test it again, without pbs i cannot Test it

@MickLesk commented on GitHub (Jun 16, 2025): Then i can deploy tomorrow another Version, but you need to test it again, without pbs i cannot Test it
OVERLORD commented 2026-02-04 23:04:31 +03:00
Author
Owner
Copy Link

@Stooovie commented on GitHub (Jun 16, 2025):

no problem, thanks!

@Stooovie commented on GitHub (Jun 16, 2025): no problem, thanks!
OVERLORD commented 2026-02-04 23:04:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 18, 2025):

i changed the restore function, can you check again? (VED call above)

@MickLesk commented on GitHub (Jun 18, 2025): i changed the restore function, can you check again? (VED call above)
OVERLORD commented 2026-02-04 23:04:45 +03:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Jun 18, 2025):

To confirm, this also failed for me on PBS but worked fine on local storage.

@oOStroudyOo commented on GitHub (Jun 18, 2025): To confirm, this also failed for me on PBS but worked fine on local storage.
OVERLORD commented 2026-02-04 23:04:48 +03:00
Author
Owner
Copy Link

@Stooovie commented on GitHub (Jun 18, 2025):

i changed the restore function, can you check again? (VED call above)

Still not working:

Suggested next free container ID: 120. Enter new container ID [default: 120]: 
🛠️ Restoring as privileged container
Unknown option: repository
400 unable to parse option
pct restore <vmid> <ostemplate> [OPTIONS]
  ✖️   Conversion failed
@Stooovie commented on GitHub (Jun 18, 2025): > i changed the restore function, can you check again? (VED call above) Still not working: ``` Suggested next free container ID: 120. Enter new container ID [default: 120]: 🛠️ Restoring as privileged container Unknown option: repository 400 unable to parse option pct restore <vmid> <ostemplate> [OPTIONS] ✖️ Conversion failed ```
OVERLORD commented 2026-02-04 23:05:00 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 18, 2025):

PBS is so an Shit Tool 😄

I cannot fix this, without this Tool. So i remove the Option for PBS and Mark this on Website. Otherwise another Dude with pbs take a Look

@MickLesk commented on GitHub (Jun 18, 2025): PBS is so an Shit Tool :smile: I cannot fix this, without this Tool. So i remove the Option for PBS and Mark this on Website. Otherwise another Dude with pbs take a Look
OVERLORD commented 2026-02-04 23:05:10 +03:00
Author
Owner
Copy Link

@Stooovie commented on GitHub (Jun 18, 2025):

no worries :)

@Stooovie commented on GitHub (Jun 18, 2025): no worries :)
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 bug
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#1098
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?