Backup stuck at 80%

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.

Rebooted the server and now I am seeing these errors pertaining to the client that is unable to complete a backup:

04.02.16 10:19 DEBUG Connecting to ClientService of “Client Server” failed: Error sending ‘running’ (2) ping to client
04.02.16 10:19 DEBUG Copying 0 files from tmp table…
04.02.16 10:19 DEBUG done.
04.02.16 10:19 DEBUG Establishing internet connection failed. Service=0
04.02.16 10:19 DEBUG Connecting to ClientService of “Client Server” failed: Error sending ‘running’ (2) ping to client
04.02.16 10:19 DEBUG Copying 0 files from tmp table…
04.02.16 10:19 DEBUG done.

Do you want memory dumps? Client or server or both?

A client dump. Thanks!

I sent a link to two client dumps from that machine to info@urbackup.org.

The previous email address I had for you (uroni@urbackup.org) failed delivery.

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.

Uploading a server dump right now. Give it a few minutes. Will get you debug logs ASAP.

@Uroni, I have almost a day’s worth of debug logs for client and server uploading right now. They are available at the same link as I sent you before.

Thanks!

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/

I rebooted both client and server and I am going to see if it finishes. If it is stuck again in the morning, I will give the latest update a try.