sync failed with some errors authentication failed - invalidt ticket - expired
- Thread starter AngryAdm
- Start date
In general tickets time out 2h after creation for security reasons, the pbs client has an async task that renews the auth ticket every 15 minutes or so (similar to the web interface) to avoid that from happening on long-running tasks, seems a bit weird to have that fail here.
What PBS versions are in use here (remote and local), and can you please attach the full sync log (e.g., as gzip compressed or so)?
Hi, We just experienced this again, I will attempt to fill in the information you requested.
2022-02-08T06:43:51+01:00: re-sync snapshot "vm/212/2022-02-02T06:00:02Z" done
2022-02-08T06:43:51+01:00: percentage done: 80.88% (14/18 groups, 157/281 snapshots in group #15)
2022-02-08T06:43:51+01:00: sync snapshot "vm/212/2022-02-02T07:00:02Z"
2022-02-08T06:43:51+01:00: sync archive qemu-server.conf.blob
2022-02-08T06:43:51+01:00: sync archive drive-scsi3.img.fidx
2022-02-08T07:28:51+01:00: downloaded 102502791 bytes (0.04 MiB/s)
2022-02-08T07:28:51+01:00: sync archive drive-scsi2.img.fidx
2022-02-08T12:57:28+01:00: downloaded 6699457660 bytes (0.32 MiB/s)
2022-02-08T12:57:28+01:00: sync archive drive-scsi0.img.fidx
2022-02-08T13:37:32+01:00: downloaded 5735962934 bytes (2.28 MiB/s)
2022-02-08T13:37:32+01:00: sync archive drive-efidisk0.img.fidx
2022-02-08T13:37:32+01:00: downloaded 0 bytes (0.00 MiB/s)
2022-02-08T13:37:32+01:00: got backup log file "client.log.blob"
2022-02-08T13:37:32+01:00: sync snapshot "vm/212/2022-02-02T07:00:02Z" done
2022-02-08T13:37:32+01:00: percentage done: 80.90% (14/18 groups, 158/281 snapshots in group #15)
2022-02-08T13:37:35+01:00: sync group vm/212 failed - permission check failed.
2022-02-08T13:37:38+01:00: sync group vm/400 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:42+01:00: sync group vm/801 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:45+01:00: sync group vm/901 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:45+01:00: TASK ERROR: sync failed with some errors.
2022-02-08T06:43:51+01:00: re-sync snapshot "vm/212/2022-02-02T06:00:02Z" done
2022-02-08T06:43:51+01:00: percentage done: 80.88% (14/18 groups, 157/281 snapshots in group #15)
2022-02-08T06:43:51+01:00: sync snapshot "vm/212/2022-02-02T07:00:02Z"
2022-02-08T06:43:51+01:00: sync archive qemu-server.conf.blob
2022-02-08T06:43:51+01:00: sync archive drive-scsi3.img.fidx
2022-02-08T07:28:51+01:00: downloaded 102502791 bytes (0.04 MiB/s)
2022-02-08T07:28:51+01:00: sync archive drive-scsi2.img.fidx
2022-02-08T12:57:28+01:00: downloaded 6699457660 bytes (0.32 MiB/s)
2022-02-08T12:57:28+01:00: sync archive drive-scsi0.img.fidx
2022-02-08T13:37:32+01:00: downloaded 5735962934 bytes (2.28 MiB/s)
2022-02-08T13:37:32+01:00: sync archive drive-efidisk0.img.fidx
2022-02-08T13:37:32+01:00: downloaded 0 bytes (0.00 MiB/s)
2022-02-08T13:37:32+01:00: got backup log file "client.log.blob"
2022-02-08T13:37:32+01:00: sync snapshot "vm/212/2022-02-02T07:00:02Z" done
2022-02-08T13:37:32+01:00: percentage done: 80.90% (14/18 groups, 158/281 snapshots in group #15)
2022-02-08T13:37:35+01:00: sync group vm/212 failed - permission check failed.
2022-02-08T13:37:38+01:00: sync group vm/400 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:42+01:00: sync group vm/801 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:45+01:00: sync group vm/901 failed - authentication failed - invalid ticket - expired
2022-02-08T13:37:45+01:00: TASK ERROR: sync failed with some errors.
I was unable to find the tasklog in /var/log ??? So I had to copy it from UI into notepad. Which apparanty resulted in 90% blank space in the beginning of the document...
Where is the file located that you are requesting?
recieving server PBS02:
Version: 2.1-2
Kernel: 5.13.19-2-pve
data to be pulled from server PBS01:
Version: 2.1-2
Kernel: 5.13.19-4-pve
Where is the file located that you are requesting?
recieving server PBS02:
Version: 2.1-2
Kernel: 5.13.19-2-pve
data to be pulled from server PBS01:
Version: 2.1-2
Kernel: 5.13.19-4-pve
Last edited:
the log file is in /var/log/proxmox-backup/tasks/... , retrievable via
the system (journal) and PBS access logs (/var/log/proxmox-backup/access.log and auth.log) surrounding the time of the first error appearing in the log would also be interesting (from the remote system!)
proxmox-backup-manager task log UPID (the UPID is also displayed in the web UI)the system (journal) and PBS access logs (/var/log/proxmox-backup/access.log and auth.log) surrounding the time of the first error appearing in the log would also be interesting (from the remote system!)
Last edited:
FYI: That's the gui task log render optimization, it only actually adds the text in the view port and enforce empty space outside that, so that the scroll bars are correct.
Hi all
Can I ask somebody for help with how to authenticate using curl to access the proxmox backup server API.
At the moment I am using the below in a bash script
START_TASK_DATA=`curl -v -s -k --cookie "PVEAuthCookie=$TICKET" -X GET $HOST/api2/json/access/roles`
echo $START_TASK_DATA
but keep getting - "authentication failed - no authentication credentials provided."
Does anyone know how to do this? What is the syntax to use the "ticket" for authentication?
Can I ask somebody for help with how to authenticate using curl to access the proxmox backup server API.
At the moment I am using the below in a bash script
START_TASK_DATA=`curl -v -s -k --cookie "PVEAuthCookie=$TICKET" -X GET $HOST/api2/json/access/roles`
echo $START_TASK_DATA
but keep getting - "authentication failed - no authentication credentials provided."
Does anyone know how to do this? What is the syntax to use the "ticket" for authentication?
Hi,
Please do not reply to other threads with unrelated posts but open a new thread, thanks! FYI: you're using the cookie name from PVE not PBS, the latter would be
PBSAuthCookie