Re: [BackupPC-users] getaddrinfo is not a valid Socket macro after Update to version 4.0.0

[Diane Leon]

​
Craig,

I have installed BackupPC Version 4.2.1 and it resolved the problem and of
course I had to update other software related.

Thanks for your help.

Diane

On Wed, May 23, 2018 at 2:53 PM, Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> Diane,
>
> That problem is related to the old version of perl and Socket you are
> running.
>
> This was fixed in BackupPC version 4.1.1 last year (it detects which
> version of Socket you are using, and defaults to old interface if
> necessary).  I strongly recommend upgrading to the most recent version of
> BackupPC (4.2.1), or the prior version (4.1.5).
>
> ​​
> Craig
>
> On Wed, May 23, 2018 at 10:20 AM, Diane Leon  wrote:
>
>> Hi,
>>
>> I am using BackupPC software for more that 4 years for my job and I never
>> had problem but last week I had the bad idea to update the software to
>> version 4.0.0 and now I have a problem running backups.
>>
>> I got the following error:
>>
>>  active1: getaddrinfo is not a valid Socket macro at
>> /usr/share/BackupPC/lib/BackupPC/Lib.pm line 1412
>>
>> I have found an email with the same problem from 2017, I have the same
>> perl version and socket, I have installed cpan and run install Socket but
>> didn't help.
>>
>> Do you have another suggestion to resolve the problem? Do I have to
>> install a new version of Perl?, I think I can install a new version in
>> different directory but how BackupPC will point to it.
>>
>> ​
>> root@sv02 usr]# perl -v
>>
>> This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi
>>
>> Copyright 1987-2009, Larry Wall
>>
>> Perl may be copied only under the terms of either the Artistic License or
>> the
>> GNU General Public License, which may be found in the Perl 5 source kit.
>>
>> Complete documentation for Perl, including FAQ lists, should be found on
>> this system using "man perl" or "perldoc perl".  If you have access to the
>> Internet, point your browser at http://www.perl.org/, the Perl Home Page.
>>
>> [root@sv02 usr]# perl -e 'use Socket; print $Socket::VERSION . "\n"'
>> 1.82
>>
>> Old Ticket with the error
>> https://sourceforge.net/p/backuppc/mailman/message/35753460/
>>
>> ​I am using Centos 6.5
>>
>> Thanks for your help
>>
>> Diane Leon
>> Senior Systems Administrator
>> di...@tbi.ca
>> (403) 702-3294
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> BackupPC-users mailing list
>> BackupPC-users@lists.sourceforge.net
>> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki:http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>>
>>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>


-- 

Diane Leon
Senior Systems Administrator
di...@tbi.ca
(403) 702-3294
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Out of inodes, how to recover?

[Holger Parplies]

Hi,

Tapio Lehtonen wrote on 2018-05-15 14:14:36 +0300 [[BackupPC-users] Out of 
inodes, how to recover?]:
> Backing up a single desktop computer, BackupPC host ran out of
> inodes at 15 million inodes used. Reading old messages from this
> list I was surprised to learn BackupPC uses only one (or two?)
> inodes per backed up file, no matter how  many hard links are used.

I believe the details depend on the BackupPC version you are using (4.x
vs. 3.x).

> I am thus at a loss to explain how come 15 million inodes is not
> enough for backing up this single desktop computer.

Explaining will only help if something is actually going wrong - which
might be the case (something not excluded that should be?).

It may be worth noting, though, that each *directory* in each backup will
also use up one inode, and possibly another one for an attrib file (in 3.x,
attrib files are pooled, in 4.x, I believe they aren't, but I'm not sure).
And it's more like "one inode per backed up version of each file", so
quickly changing data together with a large number of backups might be a
factor.

> [...]
> Question: The host is already out of inodes on backuppc partition,
> can it still remove old backups now obsolete since lower
> FullKeepCnt?

For 3.x, I can only imagine that you might need some few free inodes
for log files, the server unix domain socket, and a backup of a
'backups' file. Aside from that, expiring a backup is just deleting
files and directories - and for the directories, you immediately
regain a free inode. If nothing else helps, you can get yourself back
into business by deleting (part of) a directory tree that BackupPC
is supposed to expire. That will delete some directories and thus
free up inodes. For the actual expiration, BackupPC will look at some
meta data and then recursively delete the tree structure without
further inspecting attrib files, so it won't even notice that part of
the tree is already missing. To be safe, start somewhere below the root
and choose the correct backup (in particular, not a full backup with
dependant incrementals):

rm -r $TopDir/pc/host/num/f%2fmy%2fshare%2fname/ffoo

Again, you might not even need to worry about this. It may just work
by itself.

For 4.x, that is a good question. I could imagine the reverse delta
storage might cause problems on a full file system (storage or inode
wise), but I'm only guessing here. Deleting the oldest backups (i.e.
not intermediate ones) is probably safe.

> [...]
> From what I learned from reading discussions, copying the pool to
> larger disk with more inodes is not feasible.

That is not true. It will take its time, and it may require some thought.
cp, tar, rsync et al. may or may not work for you, BackupPC_copyPool likely
will, but it is rather experimental as in "not widely tested" (please ask
me if you're interested). And this is for 3.x. A 4.x pool should be easily
copied with the usual tools without any problems.

> [...]
> So it is time to
> start planning a new backuppc host and use lower bytes-per-inode or
> use a filesystem with dynamic inodes.

Whether a new host or just a new file system to copy the existing pool to
- I would recommend dynamic inode allocation, if just to avoid running into
the same problem again at a later point in time.

Hope that helps.

Regards,
Holger

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Out of inodes, how to recover?

[Carl W. Soderstrom]

On 05/24 05:21 , Holger Parplies wrote:
> The BackupPC daemon remembers the correct usage, and tends to ensure that
> BackupPC_nightly is not run concurrently with BackupPC_link (or whatever
> restrictions may apply for your version of BackupPC).
> 
>   BackupPC_serverMesg BackupPC_nightly run
> 
> appears to be the correct invocation to *let the BackupPC server* run
> BackupPC_nightly as soon as it is safe to do so. You will need to run
> that as the backuppc user.

Ah, yes, thank you for the reminder. It's been a few years since I had to do
this.

-- 
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Out of inodes, how to recover?

[Holger Parplies]

Hi,

Carl W. Soderstrom wrote on 2018-05-15 09:56:13 -0400 [Re: [BackupPC-users] Out 
of inodes, how to recover?]:
> [...]
> It is possible to run BackupPC_nightly by hand.

unfortunately true. You should never do that under any circumstances.

> [...]
> and here's an example usage (from memory, so this may be wrong):

The BackupPC daemon remembers the correct usage, and tends to ensure that
BackupPC_nightly is not run concurrently with BackupPC_link (or whatever
restrictions may apply for your version of BackupPC).

BackupPC_serverMesg BackupPC_nightly run

appears to be the correct invocation to *let the BackupPC server* run
BackupPC_nightly as soon as it is safe to do so. You will need to run
that as the backuppc user.

Regards,
Holger

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] getaddrinfo is not a valid Socket macro after Update to version 4.0.0

[G.W. Haywood via BackupPC-users]

Hi there,

On Thu, 24 May 2018, Diane Leon wrote:


I installed Perl 5.8.8 ...


Why on Earth did you install such out-of-date software?

https://en.wikipedia.org/wiki/Perl#2000%E2%80%93present

--

73,
Ged.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/