fiveangle's latest activity
-
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.I wrote earlier: …and i still have no clue how to do so. What "environment" do backup jobs that call vzdump inside an LXC run in ? vzdump runs inside the LXC, triggered from PVE sending the LXC scheduled for backup to the PBS datastore the...
-
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.I still have on my todo list to restore the pbs to its previous failing state and run thru the pbs updates to determine if a pbs fix resolved and will report back for posterity
-
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.You can see here from the snippet that I posted at start of this thread that the job fires PBC within the context of the LXC, and after a day and a half of trying (and failing) couldn’t find how to enable extra verbose logging for these scheduled...
-
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.The question isn’t how to increase logging on Proxmox-backup-client. Who uses that to backup PVE ? These backups are typical scheduled backups that are fired off within the context of the lxc thru a layer of obfuscation that there seems to be no...
-
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.i don't have a deep testing to confirm it was scanopy, so it is certainly possible a pbs update was applied between times that it had confirmed it was still failing, and when i removed scanopy and tested again (at a later date). I still wish...
-
Ffiveangle reacted to Robert Obkircher's post in the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. } with
Like.
There was a bug in the ChunkStream that was fixed [1] in version 4.1.5. I'm not sure if it could have caused this particular crash, but there is a chance that your issue was actually resolved by a client update. [1]... -
Ffiveangle replied to the thread tokio-runtime-worker' panicked…called `Result::unwrap()` on an `Err` value: SendError { .. }.I believe this issue is related to some incompatibility with an update to the open-source scanopy network monitoring framework (thank goodness). We disabled scanopy and the network hiccups causing pbs jobs to disconnect ceased. Be forewarned for...