On Tue, Jun 12, 2012 at 12:11:53AM -0700, tomse wrote:

> The above message is now shown after upgrading from 5.1.x to 5.2.6
> 
> Doing a manual backup using same jobs etc it works perfectly.
> So keys are good.
> 
> This only occurs with the automatic backup running through a SSH
> Tunnel (following the ssh tunnel guide in the manual)
> 
> anyone has any ideas to fix this ?

I'm afraid I do not know the answer but to me it looks like in the case
of backing up through the SSH tunnel, one of the parties (or both) uses
an IP different from that specified in the configuration.
This also might have something to do with DNS resolution.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users