Core Update 167 Failed to start Starting Guardian

Getting Started with IPFire Updates Trouble
1

Starting Guardian…
Can’t locate Net/IP.pm in @INC (you may need to install the Net::IP module) (@INC contains: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.32.1 /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/5.32.1) at /usr/lib/perl5/site_perl/5.32.1/Guardian/Base.pm line 9.
BEGIN failed–compilation aborted at /usr/lib/perl5/site_perl/5.32.1/Guardian/Base.pm line 9.
Compilation failed in require at /usr/sbin/guardian line 30. [ FAIL ]

perl-NET-IP is installed
pakfire list | grep perl-Net-IP
Name: perl-Net-IP

ls -l /usr/lib/perl5/site_perl/5.32.1/Net/IP.pm
ls: cannot access ‘/usr/lib/perl5/site_perl/5.32.1/Net/IP.pm’: No such file or directory

but was there before update
locate IP.pm | grep 5.32.1
/usr/lib/perl5/5.32.1/IO/Socket/IP.pm
/usr/lib/perl5/site_perl/5.32.1/Net/DNS/RR/HIP.pm
/usr/lib/perl5/site_perl/5.32.1/Net/IP.pm
/usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/NetAddr/IP.pm

reinstall (uninstall/install) perl-Net-IP via pakfire solved the Problem!

You want to uninstall the following packages: perl-Net-IP There may be depending packages, here is a list of packages that need to be installed.
PAKFIRE RESV: perl-Net-IP: Resolving dependencies…

NO output !

dependencies missing ?

2

It looks like the update.sh script for CU167 has removed that file in error.

I will flag it up to the devs on the mailing list.

3

Yes you are right.
Searched the update-core-upgrade-167.log
…
removed ‘/usr/lib/perl5/site_perl/5.32.1/Net/IP.pm’
…
There are many other deletions of
/usr/lib/perl5/site_perl/5.30.0/…
and new installation of
usr/lib/perl5/site_perl/5.32.1/ in the udpdate log
so may be the perl update removed all “old” perl modules…

4

The script was removing the old perl version which was changed several core updates ago. I suspect that the removal of a file from the 5.32.1 version got in the list as a typo.

5

Bug that has been raised on this issue earlier.
https://bugzilla.ipfire.org/show_bug.cgi?id=12841

1 Like
6

Sorry. Did not see this.
New on testing updates :wink:

7

No problem. I also hadn’t seen it until i had communicated to the mailing list.

Main thing is it will be fixed. Thanks for your input.

2 Likes
8

Hi,

for the records, this has been fixed in this commit.

Thanks, and best regards,
Peter Müller

1 Like