Search results

@ubu did you have CephFS enabled on the pool by any chance? I had and disabling this on that pool fixed it for me.

Running into the same issue, and created a bug report: https://tracker.ceph.com/issues/61582?next_issue_id=61581

Hi Stoiko. Thanks for giving it a try. So after the weekend it keeps happening. I deleted the LXC container and created a new one, but it still happens. I only re-used the ID, as I doubt it's a specific ID problem? I am unable to find anything related to this in the (ceph) logs. The problem only...

Hi Stoiko. Thank you for your quick reply. Ofcourse! I installed it via the GUI, so should be nothing special... arch: amd64 cmode: tty console: 1 cpulimit: 0 cpuunits: 1024 hostname: galera-01.<HOSTNAME> memory: 2048 net0: name=eth0,bridge=vmbr1,hwaddr=22:DF:CA:0F:92:CA,ip=dhcp,type=veth...

Hi, I am unable to create a snapshot of 1 specific LXC container on my Ceph cluster since I migrated everything to Ceph yesterday: INFO: starting new backup job: vzdump 110 --remove 0 --notes-template '{{guestname}}' --mode snapshot --node kvm-01 --storage backup INFO: Starting Backup of VM 110...

Ohmy, okay I got it, I had to use an actual bind user, in stead of anonymous, that way groupfilters work as well.

Okay so I got my groups added, I had the wrong baseDN. But all my users are synced to Proxmox, but I only want the members of the group "proxmox_admins". So I tried a user filter like `memberOf=cn=proxmox_admins,cn=groups,cn=accounts,dc=example,dc=com`, but it doesn't sync ANY users anymore...

Hi, I will gladly admit that I am a total noob when it comes to LDAP, but I have a FreeIPA server running; I can sync users from FreeIPA to Proxmox VE. However, users have no rights, and I have to manually add groups and add permissions to that. Is there a way to sync groups as well, and give...

Thanks, that fixed it! For whoever is reading this in the future, I also had to do a find . -gid 100033 as some files were owned by 100000 but group 100033.

Yes, it was a privileged container at first, I made a backup and then restored it as unprivileged.

Hi, I want to run Proxmox backup as an unprivileged container, which backups to an external HDD. I got the external HDD part working: arch: amd64 cmode: tty console: 1 cpulimit: 0 cpuunits: 1024 hostname: backup memory: 2048 mp0: /backup,mp=/backup net0...

Ah that explains. I rebuilt all my containers as unprivileged manually. Thanks for the bug report, hopefully it helps someone in the future!

Hi, root@backup:~# proxmox-backup-manager versions --verbose proxmox-backup 1.0-4 running kernel: 5.4.114-1-pve proxmox-backup-server 1.1.9-1 running version: 1.1.9 pve-kernel-5.4 6.4-2 pve-kernel-helper 6.4-2 pve-kernel-5.4.114-1-pve...

Restoring as privileged works. Though I want to convert them from privileged > unprivileged. # pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c) pve-kernel-5.4: 6.4-2 pve-kernel-helper: 6.4-2 pve-kernel-5.4.114-1-pve: 5.4.114-1...

Thank you kindly. Am I total blind, because it's not under pct restore in the man page. It doesn't give an example, or even state that you can refer to a PBS store. EDIT: # pct restore 110 backup:backup/ct/100/2021-05-28T10:37:41Z -storage local-lvm -unprivileged 1 -ignore-unpack-errors 1...

Hi, Is it possible to use pct restore to restore a LXC container when a backup is made in PBS? pct help restore doesn't seem to have any arguments to support that. I'd like to convert privileged containers to unprivileged, but for that I need to add the flag "-ignore-unpack-errors 1"...

Even better would be to add Prometheus support as well, something I miss in PVE too.

Hi, I wanted to add the datastore to a new PBS server, and said the .chunks directory already existed. So I removed the .chunks directory. Now all my backups are corrupt. Since this is just a test, I just make new ones, however, how would one handle that when it's for real? EDIT: To explain a...

Does anyone have any other suggestions I could try? Thank you!

Thanks Dietmar for your advice. I run version 1.1.7-1 as client, and 1.1-5 as server. The file system is ext4. I'm afraid I don't understand your comment regarding the unmount. I unmounted on the server side, and tried again, resulting in the same error.