From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 170 is available for testing Date: Fri, 19 Aug 2022 11:54:33 +0200 Message-ID: <6a1f14d2-fa6d-1f56-c3dc-4d34c4b89b7c@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3458703944086739922==" List-Id: --===============3458703944086739922== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 19/08/2022 11:33, Adolf Belka wrote: > Hi Michael, > > On 19/08/2022 10:47, Michael Tremer wrote: >> Hi Adolf, >> >> Can we have bugzilla tickets raised for these issues, please? > Yes, of course, sorry for not doing it straight away. > > I will get them written. > > Regards > Adolf >> >>> On 16 Aug 2022, at 14:58, Adolf Belka wrote: >>> >>> >>> Hi All, >>> >>> I just tried out CU170 and tested out the fuse fix for borgbackup. >>> >>> It failed. >>> >>> When I tried to do the mount I got the message:- >>> >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 fuse: device not found, try 'modprobe fuse= ' first >>> >>> I then tried running modprobe fuse and got the following message >>> >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 modprobe: FATAL: Module fuse not found in = directory=20 >>> /lib/modules/5.15.49-ipfire >>> Should this bug be raised in the original #12611 borgbackup with pyfuse3=20 or should it be a new bug. It is not clear to me if they are related or=20 if they are separate issues, although when I tested the pyfuse3 install=20 on CU169 it worked without this message, so maybe it needs to be a=20 separate one. Regards, Adolf >>> I checked and found the modules in directory=20 >>> /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my=20 >>> running CU169. >>> >>> In CU169 running modprobe fuse causes the module to be loaded=20 >>> successfully. >>> >>> >>> I am not sure what is different with CU170 and fuse. >>> >>> Let me know if there is something I need to check out on my vm system. >>> >>> >>> >>> Regarding the IP Address Blocklists new function. This has already=20 >>> been mentioned on the forum >>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/= 8400=20 >>> >>> >>> I confirm the same effect as mentioned in the forum. Trying to=20 >>> enable any list and pressing save gives a clear white page. Reload=20 >>> does not do anything. Rerunning the IPFire web app gives a system=20 >>> with everything still disabled. >>> >>> Looked in httpd/error_log but no errors from trying to run the=20 >>> ipblocklists page but the following error entries look to have been=20 >>> from the upgrade by pakfire. >>> >>> Can't locate IO/Socket/INET.pm:=20 >>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.= pm:=20 >>> Permission denied at=20 >>> /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21. >>> Compilation failed in require at /var/ipfire/general-functions.pl=20 >>> line 19. >>> BEGIN failed--compilation aborted at=20 >>> /var/ipfire/general-functions.pl line 19. >>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi=20 >>> line 30. >>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid=20 >>> 123588682180160] [client 192.168.200.10:54370] End of script output=20 >>> before headers: pakfire.cgi, referer:=20 >>> https://ipfire.saturn.pimb.org:444/ >>> sh: error while loading shared libraries: libreadline.so.8: cannot=20 >>> open shared object file: Permission denied >>> Can't locate overload.pm:=20 >>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm:=20 >>> Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28. >>> BEGIN failed--compilation aborted at=20 >>> /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28. >>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi=20 >>> line 24. >>> BEGIN failed--compilation aborted at=20 >>> /srv/web/ipfire/cgi-bin/pakfire.cgi line 24. >>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid=20 >>> 123588782827072] [client 192.168.200.10:45148] End of script output=20 >>> before headers: pakfire.cgi, referer:=20 >>> https://ipfire.saturn.pimb.org:444/ >>> Unable to write file /var/ipfire/ipblocklist/modified at=20 >>> /var/ipfire/general-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/settings at=20 >>> /var/ipfire/general-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at=20 >>> /var/ipfire/general-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at=20 >>> /var/ipfire/general-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at=20 >>> /var/ipfire/general-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at=20 >>> /var/ipfire/general-functions.pl line 256. >> >> Stefan is going to be unavailable for the next couple of weeks. So I=20 >> will have a go at this :) >> >> -Michael >> >>> >>> >>> Regards, >>> Adolf. >>> >>> >>> On 15/08/2022 18:00, IPFire Project wrote: >>>> IPFire Logo >>>> there is a new post from Peter M=C3=BCller on the IPFire Blog: >>>> *IPFire 2.27 - Core Update 170 is available for testing* >>>> =C2=A0=C2=A0 The next Core Update is available for testing. It features = new=20 >>>> IP blocklists for the firewall engine, significant improvements to=20 >>>> Pakfire, modernizes the default cryptographic algorithm selection=20 >>>> for IPsec connections, as well as a new kernel, and a plethora of=20 >>>> bug fixes and security improvements under the hood. >>>> Click Here To Read More=20 >>>> >>>> The IPFire Project >>>> Don't like these emails? Unsubscribe=20 >>>> . >> > --=20 Sent from my laptop --===============3458703944086739922==--