I have a client that had its last backup on 1-23 and has been stuck on 80% since 1-24. @uroni, do you want a memory dump? All other clients on that server have been functioning just fine. Server version 1.4.12, client version 1.4.9.
Let me know when you can, as when I know whether or not you want a memory dump or any other debugging information, I plan on doing a manual upgrade to the latest client version.
If it does not go forward at all this could be a server bug.
A while a go I had a case where the hard disk was failing and taking half an hour to read one sector. The S.M.A.R.T. attribute “pending sector count” was very high. Could you check the S.M.A.R.T. status as well?
If that isn’t the case I would be interested in a memory dump.
The larger dump is somehow implausible (stack corrupt?) – don’t know where that is coming from. The other one shows nothing out of the ordinary.
For further debugging: Either a server dump, tracing a backup with e.g. Wireshark, client debug logs would be helpful as well.
It has a hash mismatch after which it has to request a whole block. It opens a new connection to the client for that but for some reason that connection immediately has an error.
After reconnection there is a bug in the request code (it’s missing). Could you try if adding this fixes your issue? Windows server here: https://limitingfactor.urbackup.org/Server/1.4.13/