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:35:31 +0200 Message-ID: <9a2200ad-e24e-8fee-fbaf-73b777843897@ipfire.org> In-Reply-To: <2cd15fdb-8273-7bb2-05a8-2e4d259b4fa3@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1768650763462838334==" List-Id: --===============1768650763462838334== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On 19/08/2022 11:12, Peter M=C3=BCller wrote: > Hello *, >=20 >> Hi Adolf, >> >> Can we have bugzilla tickets raised for these issues, please? >=20 > first, thank you for the testing feedback. Second, I second the wish for ti= ckets. :-) Will do so. >=20 > On the general front, apologies for being rather quiet recently. I will wor= k through > the mailing list and community later today and tomorrow, and give Core Upda= te 170 and > all the other things in need of it some love and care. No problems, I know you are all very busy people. I know you will get=20 round to the emails when you are able to. Regards, Adolf. >=20 > Also, due to ${dayjob}, I will be unavailable from August 23 to August 29. >=20 > Thanks, and best regards, > Peter M=C3=BCller >=20 >=20 >> >>> 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:- >>> >>> fuse: device not found, try 'modprobe fuse' first >>> >>> I then tried running modprobe fuse and got the following message >>> >>> modprobe: FATAL: Module fuse not found in directory /lib/modules/5= .15.49-ipfire >>> >>> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/= kernel/fs/fuse/ just the same as in my running CU169. >>> >>> In CU169 running modprobe fuse causes the module to be loaded successfull= y. >>> >>> >>> 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 been m= entioned on the forum >>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/= 8400 >>> >>> I confirm the same effect as mentioned in the forum. Trying to enable any= list 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. >>> >>> Looked in httpd/error_log but no errors from trying to run the ipblocklis= ts page but the following error entries look to have been from the upgrade by= pakfire. >>> >>> Can't locate IO/Socket/INET.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-= linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.3= 2.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 lin= e 19. >>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line= 30. >>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 12358868218= 0160] [client 192.168.200.10:54370] End of script output before headers: pakf= ire.cgi, referer: https://ipfire.saturn.pimb.org:444/ >>> sh: error while loading shared libraries: libreadline.so.8: cannot open s= hared object file: Permission denied >>> Can't locate overload.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-= thread-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= 24. >>> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi = line 24. >>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 12358878282= 7072] [client 192.168.200.10:45148] End of script output before headers: pakf= ire.cgi, referer: https://ipfire.saturn.pimb.org:444/ >>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/gene= ral-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/gene= ral-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/gene= ral-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/gene= ral-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/gene= ral-functions.pl line 256. >>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/gene= ral-functions.pl line 256. >> >> Stefan is going to be unavailable for the next couple of weeks. So I 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* >>>> The next Core Update is available for testing. It features new IP bl= ocklists for the firewall engine, significant improvements to Pakfire, modern= izes the default cryptographic algorithm selection for IPsec connections, as = well as a new kernel, and a plethora of bug fixes and security improvements u= nder the hood. >>>> Click Here To Read More >>>> The IPFire Project >>>> Don't like these emails? Unsubscribe . >> --=20 Sent from my laptop --===============1768650763462838334==--