Backup - Error: not a valid user id

[Frenshow]

Hello guys,

I created a new PBS storage in one of my server. All of my containers save themselves without problem. But, there is one, when I try to backup it I have the following error : "Error: not a valid user id". So, I tried to backup it on the old PBS storage and it is works. I would like to know, where does the problem comes ?

Thanks

 

[dylanw]

Are you sure that these containers (working and not working) are sending backups to the exact same PBS storage? Could you post the output of cat /etc/pve/storage.cfg?

 

[Frenshow]

Are you sure that these containers (working and not working) are sending backups to the exact same PBS storage? Could you post the output of cat /etc/pve/storage.cfg?

In fact, this containers sent backups in a 'A' storage and now I want this containers sent backups in 'B' storage

 

[dylanw]

I'm having a hard time seeing what might trigger this error. I assume you're using vzdump or the PVE GUI for container backups?
Could you post the output of pveversion -v and proxmox-backup-manager versions --verbose?
It could also be helpful to see cat /etc/pve/storage.cfg and the container config (cat /etc/pve/lxc/<id>.conf) in case just one container is causing issues.

 

[Frenshow]

This is the output of pveversion -v

proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

This is the output of cat /etc/pve/storage.cfg

pbs: XXX
datastore dt1
server XXX.XXX.XXX.XXX
content backup
fingerprint XXXXXXXXXXXXXXXXXXXXXXXXXX
prune-backups keep-all=1
username XXXX@XXX

pbs: XXX
datastore dtn1
server XXX.XXX.XXX.XXX
content backup
fingerprint XXXXXXXXXXXXXXXXXXXXXXXXXX
prune-backups keep-all=1
username XXXX@XXX

And this is the output of cat /etc/pve/lxc/<id>.conf

arch: amd64
cores: 8
hostname: XXXX
memory: 8192
net0: name=eth0,bridge=vmbr0,firewall=1,gw=XXX.XXX.XXX.XX,hwaddr=XXXXXXXXXXip=XXX.XXX.XXX.XXXtype=veth
onboot: 1
ostype: ubuntu
rootfs: local-zfs:subvol-XXX-disk-0,size=15G
swap: 8192

Thank you !

 

[dylanw]

Are the usernames for each backup server the same? Could you possibly provide them?

 

[Denny Fuchs]

hi,

I have the same issue, on a single VM. All VMs can backuped, also on the same PVE ...

Task viewer: VM/CT 127 - Backup

OutputStatus

Stop
INFO: starting new backup job: vzdump 127 --node fra-corp-pmox-03 --remove 0 --storage fra-corp-srv-backup --mode snapshot
INFO: Starting Backup of VM 127 (qemu)
INFO: Backup started at 2021-05-14 13:44:48
INFO: status = running
INFO: VM Name: fra-corp-consul-03
INFO: include disk 'scsi0' 'lenovo-san-01:vm-127-disk-0' 8G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/127/2021-05-14T11:44:48Z'
INFO: enabling encryption
ERROR: VM 127 qmp command 'backup' failed - backup connect failed: command error: not a valid user id
INFO: aborting backup job
ERROR: Backup of VM 127 failed - VM 127 qmp command 'backup' failed - backup connect failed: command error: not a valid user id
INFO: Failed at 2021-05-14 13:44:48
INFO: Backup job finished with errors
TASK ERROR: job errors

On the same node, different VM

Task viewer: VM/CT 123 - Backup

OutputStatus

Stop
INFO: starting new backup job: vzdump 123 --remove 0 --node fra-corp-pmox-03 --mode snapshot --storage fra-corp-srv-backup
INFO: Starting Backup of VM 123 (qemu)
INFO: Backup started at 2021-05-14 13:44:05
INFO: status = running
INFO: VM Name: fra-corp-admin-01
INFO: include disk 'scsi0' 'lenovo-san-01:vm-123-disk-0' 10G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/123/2021-05-14T11:44:05Z'
INFO: enabling encryption
INFO: started backup task '12728d53-4740-4bf4-b249-69a86ebeaac5'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (792.0 MiB of 10.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 792.0 MiB dirty of 10.0 GiB total
INFO:  58% (464.0 MiB of 792.0 MiB) in 3s, read: 154.7 MiB/s, write: 150.7 MiB/s
INFO: 100% (792.0 MiB of 792.0 MiB) in 6s, read: 109.3 MiB/s, write: 96.0 MiB/s
INFO: backup was done incrementally, reused 9.28 GiB (92%)
INFO: transferred 792.00 MiB in 6 seconds (132.0 MiB/s)
INFO: Finished Backup of VM 123 (00:00:06)
INFO: Backup finished at 2021-05-14 13:44:11
INFO: Backup job finished successfully
TASK OK

Migrate / shutdown / start VM does not help.

On the backup server I can see:

May 14 14:05:21 fra-corp-srv-backup proxmox-backup-proxy[624]: GET /api2/json/backup?backup-id=127&backup-time=1620993920&backup-type=vm&benchmark=false&debug=false&store=store-01: 400 Bad Request: [client [::ffff:192.168.43.4]:35606] not a valid user id

May 14 14:06:54 fra-corp-srv-backup proxmox-backup-proxy[624]: Failed to get owner of group 'store-01/vm/127' - not a valid user id

Any suggestions ?

cu denny

 

[Denny Fuchs]

Ok, solved

root@fra-corp-srv-backup:[/mnt/datastore/store-01/vm/127]: ls -l
total 0
-rw-r--r-- 1 backup backup 0 May 12 06:08 owner

root@fra-corp-srv-backup:[/mnt/datastore/store-01/vm]: rm -Rf 127/

So I've deleted that folder ... and backup works now. The origin problem was, that the content from file "owner" was empty.

 

[Jesse Norell]

The origin problem was, that the content from file "owner" was empty.

We have the exact same issue on one vm, and just adding a bit of info that might be a clue to help catch/address these in the future, we recently ran out of space on that datastore so backups were failing - it's possible (though I'm not positive) that vm was created and the initial backup job ran when the datastore was in an out of space condition, or ran out of space while backups were underway. I suppose it would be easy enough for PBS to test for an empty "owner" file and remove it - though no idea if that is a proper thing for it to do.