digg_de's picture

I get a warning from the tklbam-backup script:

warning: can't update Hub of backup completed:
error(56, 'GnuTLS recv error (-54): Error in the pull function.')

Can I be sure, that my data are backuped correctly? Can everybody help to solve the warning?


Jeremy Davis's picture

TBH I haven't seen that one before. Is that in your logs, or when you run a backup manually? Also has it been occurring lots, or just intermittently?

I'm not 100% sure, but after a bit of googling it seems likely that it was caused by a networking issue.

Out of interest, where is your server running? A local VM? Hub AWS instance? Something else?

digg_de's picture

My server runs in a local VMWare Sphere. There are no known network problems?

This warning is part of the report email by the cron job. Here the complete email:


--------------[ Backup Statistics ]--------------
StartTime 1500176722.14 (Sun Jul 16 05:45:22 2017)
EndTime 1500176745.19 (Sun Jul 16 05:45:45 2017)
ElapsedTime 23.05 (23.05 seconds)
SourceFiles 22081
SourceFileSize 1311829230 (1.22 GB)
NewFiles 573
NewFileSize 19605292 (18.7 MB)
DeletedFiles 11
ChangedFiles 216
ChangedFileSize 69065247 (65.9 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 800
RawDeltaSize 79827968 (76.1 MB)
TotalDestinationSizeChange 27628595 (26.3 MB)
Errors 0

warning: can't update Hub of backup completed:
error(56, 'GnuTLS recv error (-54): Error in the pull function.')

TIP: test your backups with a trial restore BEFORE something bad happens.


Jeremy Davis's picture

Now I see the message in context, I wonder if perhaps the issue was on the Hub's end. TBH, that's what it looks like to me. I'll ask Alon (the Hub Daddy) and see what he says.

Assuming I'm right, there is no issue with your backup itself (Errors 0). It's just that for some reason the Hub doesn't know that it completed successfully. The Hub was designed so it couldn't be a single point of failure for TKLBAM.

But obviously it's not ideal. I'll let you know what Alon says ASAP.

Jeremy Davis's picture

But as i said there, I would reply with expanded info here.

Also sorry that I hadn't responded as I said I would earlier in this thread...

So my colleague Alon reported that there was nothing apparently wrong with the Hub and neither of us could reproduce the issue. So after a bit more research, it appears that the issue is related to a network traffic issue.

Unfortunately, exactly what is causing the issue is hard to diagnose. It could just be an intermittent network issue including traffic congestion (e.g. retrying again might make it work?). But it could also be something to do with the outgoing network setup for your server. E.g. if your server connects to the internet via a firewall, perhaps some of the traffic is being dropped? Or perhaps if your traffic goes through some sort of proxy that is somehow mangling the traffic?

It's unfortunate, but I don't really have any further suggestions beyond investigating your outgoing network configuration and/or just retrying (if a retry still fails, perhaps try at a different time of day).

Add new comment