public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
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	[thread overview]
Message-ID: <6a1f14d2-fa6d-1f56-c3dc-4d34c4b89b7c@ipfire.org> (raw)
In-Reply-To: <e53e4cdc-39c8-fcc2-b134-0b89b30c57c5@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 5386 bytes --]

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 <adolf.belka(a)ipfire.org> 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
>>>
Should this bug be raised in the original #12611 borgbackup with pyfuse3 
or should it be a new bug. It is not clear to me if they are related or 
if they are separate issues, although when I tested the pyfuse3 install 
on CU169 it worked without this message, so maybe it needs to be a 
separate one.

Regards,

Adolf
>>> 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 
>>> 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 
>>> been mentioned 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 
>>> ipblocklists 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.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 30.
>>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 
>>> 123588682180160] [client 192.168.200.10:54370] End of script output 
>>> before headers: pakfire.cgi, referer: 
>>> https://ipfire.saturn.pimb.org:444/
>>> sh: error while loading shared libraries: libreadline.so.8: cannot 
>>> open shared 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 
>>> 123588782827072] [client 192.168.200.10:45148] End of script output 
>>> before headers: pakfire.cgi, referer: 
>>> https://ipfire.saturn.pimb.org:444/
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/settings at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-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üller 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 blocklists for the firewall engine, significant improvements to 
>>>> Pakfire, modernizes the default cryptographic algorithm selection 
>>>> for IPsec connections, as well as a new kernel, and a plethora of 
>>>> bug fixes and security improvements under the hood.
>>>> Click Here To Read More 
>>>> <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>>> The IPFire Project
>>>> Don't like these emails? Unsubscribe 
>>>> <https://people.ipfire.org/unsubscribe>.
>>
>

-- 
Sent from my laptop


  reply	other threads:[~2022-08-19  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166057920894.3662646.17671924655074704229.ipfire@ipfire.org>
2022-08-16 13:58 ` Adolf Belka
2022-08-16 14:36   ` Adolf Belka
2022-08-18 16:47     ` Adolf Belka
2022-08-19  8:46   ` Michael Tremer
2022-08-19  9:12     ` Peter Müller
2022-08-19  9:35       ` Adolf Belka
2022-08-19  8:47   ` Michael Tremer
2022-08-19  9:33     ` Adolf Belka
2022-08-19  9:54       ` Adolf Belka [this message]
2022-08-19 10:09         ` Adolf Belka
2022-08-22 20:36           ` Peter Müller
2022-09-01 15:02             ` Michael Tremer
2022-09-01 20:51               ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a1f14d2-fa6d-1f56-c3dc-4d34c4b89b7c@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox