From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 170 is available for testing Date: Fri, 19 Aug 2022 09:46:03 +0100 Message-ID: <815015ED-680E-475E-9FCA-AD0739B19059@ipfire.org> In-Reply-To: <80c5aa2e-54f3-df52-c598-1d98d9f579e0@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7773049833651829347==" List-Id: --===============7773049833651829347== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Adolf, Can we have bugzilla tickets raised for these issues, please? > On 16 Aug 2022, at 14:58, Adolf Belka wrote: >=20 >=20 > Hi All, >=20 > I just tried out CU170 and tested out the fuse fix for borgbackup. >=20 > It failed. >=20 > When I tried to do the mount I got the message:- >=20 > fuse: device not found, try 'modprobe fuse' first >=20 > I then tried running modprobe fuse and got the following message >=20 > modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15= .49-ipfire >=20 > I checked and found the modules in directory /lib/modules/5.15.59-ipfire/ke= rnel/fs/fuse/ just the same as in my running CU169. >=20 > In CU169 running modprobe fuse causes the module to be loaded successfully. >=20 >=20 > I am not sure what is different with CU170 and fuse. >=20 > Let me know if there is something I need to check out on my vm system. >=20 >=20 >=20 > Regarding the IP Address Blocklists new function. This has already been men= tioned on the forum > https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/84= 00 >=20 > I confirm the same effect as mentioned in the forum. Trying to enable any l= ist and pressing save gives a clear white page. Reload does not do anything. = Rerunning the IPFire web app gives a system with everything still disabled. >=20 > Looked in httpd/error_log but no errors from trying to run the ipblocklists= page but the following error entries look to have been from the upgrade by p= akfire. >=20 > Can't locate IO/Socket/INET.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-li= nux-thread-multi/IO/Socket/INET.pm: Permission denied at /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 line 19. > BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line = 19. > Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 3= 0. > [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 1235886821801= 60] [client 192.168.200.10:54370] End of script output before headers: pakfir= e.cgi, referer: https://ipfire.saturn.pimb.org:444/ > sh: error while loading shared libraries: libreadline.so.8: cannot open sha= red object file: Permission denied > Can't locate overload.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-th= read-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/= URI.pm line 28. > BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm= line 28. > Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 2= 4. > BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi li= ne 24. > [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 1235887828270= 72] [client 192.168.200.10:45148] End of script output before headers: pakfir= e.cgi, referer: https://ipfire.saturn.pimb.org:444/ > Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/genera= l-functions.pl line 256. > Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/genera= l-functions.pl line 256. > Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/genera= l-functions.pl line 256. > Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/genera= l-functions.pl line 256. > Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/genera= l-functions.pl line 256. > Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/genera= l-functions.pl line 256. Stefan is going to be unavailable for the next couple of weeks. So I will hav= e a go at this :) -Michael >=20 >=20 > Regards, > Adolf. >=20 >=20 > 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* >> The next Core Update is available for testing. It features new IP block= lists for the firewall engine, significant improvements to Pakfire, modernize= s the default cryptographic algorithm selection for IPsec connections, as wel= l as a new kernel, and a plethora of bug fixes and security improvements unde= r the hood. >> Click Here To Read More >> The IPFire Project >> Don't like these emails? Unsubscribe . --===============7773049833651829347==--