Re: [Duplicity-talk] hostname mismatch?

[Kenneth Loafman]

Duplicity obtains the hostname from the Python call socket.getfqdn(),
so if the host names are set up the same way on each machine, it
should return the fqdn if you've supplied it, or the simple hostname
if not.

A simple way to check is 'hostname -f' from the command line.  I've
found that the Python call returns the same answer.

...Ken

On Wed, Mar 20, 2013 at 4:59 AM,  <address@hidden> wrote:
> On 20.03.2013 04:36, Cory Coager wrote:
>> Regarding the duplicity manifest file for hostname, why does duplicity use 
>> the short name sometimes and the fqdn other times?  There doesn't seem to be 
>> any consistency.  I have 12 servers created from the same template, 8 are 
>> using the short name and 4 are using the fqdn.  Any idea why?
>>
>> I'm noticing this is an issue recently because one of my servers started 
>> complaining about,
>> "Fatal Error: Backup source host has changed."
>>
>> I'd rather avoid --allow-source-mismatch if I can.  How can I make this 
>> consistent with fqdn's?
>>
>
> to my knowledge only the source path is saved and compared resulting in the 
> error above. unfortunately i never had a look at that part of the source.
> Ken: any idea?
>
> ..ede