October 26, 20232 yr root@unraid:/mnt/user/backups/pbs# ls -la total 4 drwxrwxrwx 1 34 34 80 Oct 26 23:47 ./ drwxrwxrwx 1 nobody users 76 May 29 19:25 ../ drwxrwxrwx 1 nobody users 57448 Apr 15 2023 .chunks/ -rw-rw-rw- 1 nobody users 318 Oct 21 02:00 .gc-status -rw-rw-rw- 1 nobody users 0 Apr 15 2023 .lock drwxrwxrwx 1 nobody users 90 Oct 25 17:33 ct/
October 27, 20232 yr Last day or 2 my backup server just stopped working. authkey errors in the logs. No idea yet how to fix this. Can anyone point me in the right direction? Thanks thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13)', src/auth_helpers.rs:162:63 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace PROXY: Starting... thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13)', src/auth_helpers.rs:162:63 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace PROXY: Starting... thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13)', src/auth_helpers.rs:162:63 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace PROXY: Starting... thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13)', src/auth_helpers.rs:162:63 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace PROXY: Starting... thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13)', src/auth_helpers.rs:162:63 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Quote
October 27, 20232 yr 10 minutes ago, ZappyZap said: check you permissions. permissions on what? Been running fine for 6 months. Nothing changed.
October 28, 20232 yr Author The log seems clear.... unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13) the container cannot read this file , who is mounted in the container from your Unraid what is the output of ls -al /etc/proxmox-backup/ Edited October 28, 20232 yr by ZappyZap
October 28, 20232 yr 7 hours ago, ZappyZap said: The log seems clear.... unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13) the container cannot read this file , who is mounted in the container from your Unraid what is the output of ls -al /etc/proxmox-backup/ thanks # ls -al /etc/proxmox-backup/ total 36 drwx------ 1 backup backup 185 Oct 27 16:03 . drwxr-xr-x 1 root root 1902 Sep 27 14:39 .. -rw-r--r-- 1 99 users 0 Sep 3 00:18 .initialized -rw-r----- 1 99 users 24 Sep 27 14:36 acl.cfg -rw------- 1 99 users 3243 Sep 3 00:18 authkey.key -rw-r----- 1 99 users 800 Sep 3 00:18 authkey.pub -rw-r----- 1 99 users 1675 Sep 3 00:18 csrf.key -rw-r----- 1 99 users 232 Sep 27 16:30 datastore.cfg -rw-r----- 1 99 users 3243 Sep 3 00:18 proxy.key -rw-r----- 1 99 users 2094 Sep 3 00:18 proxy.pem -rw------- 1 99 users 148 Sep 20 13:35 shadow.json -rw-r----- 1 99 users 114 Sep 20 13:35 user.cfg
October 28, 20232 yr As seen above, I've also had permissions strangeness. Container runs (essentially) fine using 34:34 as user/group (which means other unraid apps can't access the files, but I've worked around that), and then suddenly one (and just one) chunk has 99:100 permissions. No idea why.
October 28, 20232 yr 10 hours ago, ZappyZap said: The log seems clear.... unable to read "/etc/proxmox-backup/authkey.pub" - Permission denied (os error 13) the container cannot read this file , who is mounted in the container from your Unraid what is the output of ls -al /etc/proxmox-backup/ Fixed - granted r/w to groups and other on the pbs appdata folders. Not sure why that was altered. All running as normal now. Thanks
December 11, 20232 yr I'm excited to see this container, but it doesn't want to come up on my server Just gets stuck at 12/11/202311:31:59 AM API: Starting... 12/11/202311:32:00 AM PROXY: Starting...
December 11, 20232 yr Author 1 minute ago, zer0zer0 said: I'm excited to see this container, but it doesn't want to come up on my server Just gets stuck at 12/11/202311:31:59 AM API: Starting... 12/11/202311:32:00 AM PROXY: Starting... let me get to my host and i will see what happening there for you if i can help would be happy
March 9, 20242 yr Seems like the container does not bind a port for the Web interface by default, i had to manualy add the 8007 port so it would let data trough, after setting it i was able to open the webinterface
March 9, 20242 yr Author what do you mean ? the container use network type as Host. So no need to bind anything unless you already have something on 8007
April 15, 20242 yr For some reason the path I choose only shows up 20Gb when I add the datastore, but there should be way more. What could the issue be here?
April 15, 20242 yr Author What did you put in : Backup path ? your datastore should be /backups i have tear down my test instance for some hw maintenance. hopefully i will be able to check/test this tonight or tomorrow
April 15, 20242 yr 2 hours ago, ZappyZap said: What did you put in : Backup path ? your datastore should be /backups i have tear down my test instance for some hw maintenance. hopefully i will be able to check/test this tonight or tomorrow Oh my, stupid mistake from me… I tried /backup first and didn’t see the ‘s’. All well and working flawlessly now, thank you
September 24, 20241 yr I see there are updates to the repo, but haven't seen any new releases cut. Are there plans to do this?
September 24, 20241 yr Author 10 minutes ago, jsunjones said: I see there are updates to the repo, but haven't seen any new releases cut. Are there plans to do this? waiting on ayufan to build a new image. please ask hin in the repo
October 4, 20241 yr I'm struggling with backups now with .chunks errors and nothing will backup to my pbs datastore. Been using it for 2 years. I had recently changed my cache from btrfs to zfs and restored all of my apps. But this looks like a permission issue on the datastore on the array (not changed) Error: update atime failed for chunk/file "/datastore/.chunks/688e/688ee26ec68c1c1d4fd7e13d18cecc4731abc96bd4949142828c3dc9b6b032d0" - EPERM: Operation not permitted INFO: cleanup temporary 'vzdump' snapshot I have the following permissions set: root@Tower:/mnt/user/ProxmoxDataStore# ls -la total 2116 drwxrwxrwx 1 nobody users 96 Oct 2 00:00 ./ drwxrwxrwx 1 nobody users 115 Oct 4 13:48 ../ drwxrwxrwx 1 nobody users 1069056 Apr 2 2024 .chunks/ -rw-rw-rw- 1 nobody users 331 Oct 2 00:00 .gc-status -rw-rw-rw- 1 nobody users 0 Apr 2 2024 .lock drwxrwxrwx 1 nobody users 4096 Sep 29 13:07 ct/ drwxrwxrwx 1 nobody users 205 Oct 4 13:15 vm/ Ended up creating a new datastore on another drive of the array. I do have past backups in standard format on another drive luckily Edited October 4, 20241 yr by only-university6482
January 6, 20251 yr Hello. I setup PBS and tested it to backup a VM to Unraid. Everything works fine. My problem is the datastore size seems to default to 25gb. How can I set/change the size of the backup disk?
February 10, 20251 yr I just can't get for the backups to move to the share. It stays in the docker container. It has something to do with permissions. My expertise doesn't know where to set them. Your assistance is much appreciated. Logs: text error warn system array login rm: cannot remove '/etc/proxmox-backup/.*.lck': No such file or directory rm: cannot remove '/etc/proxmox-backup/*.lock': No such file or directory Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" } catching shutdown signal catching reload signal Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" } applied rrd journal (2 entries in 0.034 seconds) rrd journal successfully committed (0 files in 0.005 seconds) catching shutdown signal catching reload signal authentication failure; rhost=[::ffff:10.0.11.240]:62676 msg=ticket with invalid signature authentication failure; rhost=[::ffff:10.0.11.240]:62666 msg=ticket with invalid signature GET /api2/json/nodes/localhost/tasks?running=1&limit=100: 401 Unauthorized: [client [::ffff:10.0.11.240]:62676] authentication failed - ticket with invalid signature GET /api2/json/admin/datastore/Unraid-PBS/active-operations: 401 Unauthorized: [client [::ffff:10.0.11.240]:62666] authentication failed - ticket with invalid signature authentication failure; rhost=[::ffff:10.0.11.240]:62666 user=root@pam msg=authentication error - SUCCESS (0) error getting zfs devices: failed to execute "zpool" "list" "-H" "-p" "-P" "-v" - No such file or directory (os error 2) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62677] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62677] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) GET /api2/json/nodes/MSD-Unraid/tasks/UPID%3AMSD-Unraid%3A0000000A%3A01D9B932%3A00000000%3A67AA099A%3Acreate-datastore%3AUnraid%5Cx2dPBS%3Aroot%40pam%3A/status: 400 Bad Request: [client [::ffff:10.0.11.240]:62676] control socket connect failed - Permission denied (os error 13) authentication failure; rhost=[::ffff:10.0.11.240]:62676 user=root@pam msg=authentication error - SUCCESS (0) starting new backup on datastore 'Unraid-PBS' from ::ffff:10.0.11.250: "vm/101/2025-02-10T14:17:11Z" created new fixed index 1 ("vm/101/2025-02-10T14:17:11Z/drive-scsi0.img.fidx") add blob "/10.0.11.254/PBSBackup/vm/101/2025-02-10T14:17:11Z/qemu-server.conf.blob" (405 bytes, comp: 405) Upload statistics for 'drive-scsi0.img.fidx' UUID: bb326a1186a54913aa0a458443eae0ca Checksum: 4a4b97be3c42347569802f8fe796df27e6c82303735adf237d6714f723c57b44 Size: 10737418240 Chunk count: 2560 Upload size: 9281994752 (86%) Duplicates: 347+0 (13%) Compression: 57% successfully closed fixed index 1 add blob "/10.0.11.254/PBSBackup/vm/101/2025-02-10T14:17:11Z/index.json.blob" (327 bytes, comp: 327) successfully finished backup backup finished successfully PROXY: The proxmox-backup is not yet configured! CRON: Starting... Copying defaults into `/etc/proxmox-backup/` '/etc/proxmox-backup-default/./acl.cfg' -> '/etc/proxmox-backup/./acl.cfg' '/etc/proxmox-backup-default/./shadow.json' -> '/etc/proxmox-backup/./shadow.json' '/etc/proxmox-backup-default/./user.cfg' -> '/etc/proxmox-backup/./user.cfg' /etc/proxmox-backup is a mountpoint /var/lib/proxmox-backup is a mountpoint /var/log/proxmox-backup is a mountpoint /run is a mountpoint API: Starting... PROXY: The proxmox-backup is not yet configured! PROXY: The proxmox-backup is not yet configured! PROXY: Starting... Upload backup log to datastore 'Unraid-PBS', root namespace vm/101/2025-02-10T14:17:11Z/client.log.blob ------------------------------------------------------- p.s.: I should add that I removed/uninstalled it this morning. Created a new data store, and created a small 10g VM backup. SAme result. The files stay in the docker image. Edited February 10, 20251 yr by Sickdove
February 10, 20251 yr Author what is you config ? and what is the permissions on the different mount ?
February 10, 20251 yr Can this credentials be the problem? I just installed PBS as a unraid_VM with same results. TiA
February 10, 20251 yr 1 hour ago, ZappyZap said: what is you config ? and what is the permissions on the different mount ? Please let me know the contents of which file and I can share with you. ty
.thumb.jpg.bec61e4e919a9235cc4475f8cb53d5e3.jpg)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.