Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1

2017-03-29 Thread Craig Barratt
> > John Barton wrote on 2017-03-29 00:30:30 + [Re: [BackupPC-users] Error > ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1]: > > [...] > > # perl -e 'use Socket; print $Socket::VERSION . "\n"' > > 1.82 > > for reference, I get t

Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1

2017-03-29 Thread Holger Parplies
Hi, John Barton wrote on 2017-03-29 00:30:30 + [Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1]: > [...] > # perl -e 'use Socket; print $Socket::VERSION . "\n"' > 1.82 for reference, I get the following for different Deb

Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1

2017-03-28 Thread John Barton
4 PM To: General list for user discussion, questions and support <backuppc-users@lists.sourceforge.net> Subject: Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1 Steve Palm reported that error last week on this list. It relates to a patch included in 4.x

Re: [BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1

2017-03-27 Thread Craig Barratt
Steve Palm reported that error last week on this list. It relates to a patch included in 4.x to make ipv6 work. It's likely you have an old version of perl and Socket.pm. Could you tell us your versions? Run this: perl -v perl -e 'use Socket; print $Socket::VERSION . "\n"' Try upgrading

[BackupPC-users] Error ' getaddrinfo is not a valid Socket macro' after upgrading to 4.1

2017-03-27 Thread John Barton
I recently upgraded from BackupPC 3.3.0 to version 4.1. The upgrade process itself seemed to go OK, and I only had to fix a few unquoted items in my config file for BackupPC to successfully restart. Now, however, when I try to run a backup on a client that was working prior to the upgrade, I