Hi Matthias, Am Sonntag, den 11.10.2020, 10:00 +0200 schrieb Matthias Fischer: > Hi, > > => https://bugzilla.ipfire.org/show_bug.cgi?id=12491 > > Confirmed. > > The mean part was > https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5f1039dda984ed3a06da95ba7d9248b759cf9125 > > MT and Fred found a solution (Thanks!). Great thanks to all, haven´t checked bugzilla ;-) > > The only thing: I'm not quite sure how to integrate a fix deleting > the > old directory and file(s) under consideration of the respective > client > architecture. May i am terribly unright but shouldn´t a wildcard solve this /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS > > Best, > Matthias Best, Erik > > On 11.10.2020 09:52, ummeegge wrote: > > Hi all, > > did a fresh install of Core 150 and updated it to Core 151 testing. > > By > > calling the OpenVPN WUI i get an internal server error with the > > following error_log entry: > > > > Can't locate Net/DNS/RR/NXT.pm in @INC (you may need to install the > > Net::DNS::RR::NXT module) (@INC contains: > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi > > /usr/lib/perl5/site_perl/5.30.0 /usr/lib/perl5/5.30.0/x86_64-linux- > > thread-multi /usr/lib/perl5/5.30.0) at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/RR.pm line 86. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/RR.pm line 131. > > Compilation failed in require at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Packet.pm line 15. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Packet.pm line 15. > > Compilation failed in require at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver/Base.pm line 20. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver/Base.pm line 20. > > Compilation failed in require at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver/UNIX.pm line 9. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver/UNIX.pm line 9. > > Compilation failed in require at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver.pm line 19. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS/Resolver.pm line 22. > > Compilation failed in require at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS.pm line 37. > > BEGIN failed--compilation aborted at > > /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- > > multi/Net/DNS.pm line 37. > > Compilation failed in require at /srv/web/ipfire/cgi- > > bin/ovpnmain.cgi line 26. > > BEGIN failed--compilation aborted at /srv/web/ipfire/cgi- > > bin/ovpnmain.cgi line 26. > > [Sun Oct 11 09:48:22.546603 2020] [cgid:error] [pid 8658:tid > > 127223231145536] [client 192.168.75.2:58726] End of script output > > before headers: ovpnmain.cgi > > > > > > So it seems that some perl moduls are missing. Does someone have > > similar problems ? > > > > Best, > > > > Erik > > > > > > > > Am Sonntag, den 11.10.2020, 07:27 +0200 schrieb ummeegge: > > > Good morning, > > > > > > Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer: > > > > Hi, > > > > > > > > > On 9 Oct 2020, at 21:56, ummeegge > > > > > wrote: > > > > > > > > > > Hi all, > > > > > > > > > > Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael > > > > > Tremer: > > > > > > Hello, > > > > > > > > > > > > Could you please open a ticket on BZ for both of them? > > > > > > > > > > Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 > > > > > https://bugzilla.ipfire.org/show_bug.cgi?id=12494 > > > > > > > > Done and dealt with. > > > > > > Great. > > > > > > > > > > > > apart from that my Prime has been smoked up with a read-only > > > > > file > > > > > system and is gone into the "Ewige Jagd Gründe" after a > > > > > reboot > > > > > but > > > > > this > > > > > might have other reasons but further testings/developments > > > > > are > > > > > currently a little awkward. > > > > > > > > Software failure? > > > > > > No the SSD died. > > > > > > > > > > > -Michael > > > > > > > > > Best from shit happens, > > > > > > > > > > Erik > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > -Michael > > > > > > > > > > > > > On 9 Oct 2020, at 12:46, ummeegge > > > > > > > wrote: > > > > > > > > > > > > > > Hi all, > > > > > > > i wanted to report a problem with SSH after updating to > > > > > > > core > > > > > > > 151 > > > > > > > testing. > > > > > > > > > > > > > > SSH runs regular on port 222 after updating SSH runs on > > > > > > > port > > > > > > > 22 > > > > > > > and > > > > > > > wasn´t reachable via the old settings. After pressing the > > > > > > > save > > > > > > > button > > > > > > > in SSH section in the WUI everything worked again. > > > > > > > > > > > > > > May someone else have that too ? > > > > > > > > > > > > > > Also, /etc/os-release shows > > > > > > > > > > > > > > PRETTY_NAME="IPFire 2.25 (x86_64) - core145 Development > > > > > > > Build: > > > > > > > master/405c7326" > > > > > > > > > > > > > > but /var/ipfire/fireinfo/profile shows the correct > > > > > > > version > > > > > > > > > > > > > > "release": "IPFire 2.25 (x86_64) - core151 Development > > > > > > > Build: > > > > > > > master/5e4126c3", > > > > > > > > > > > > > > but apart from that no further problems so far. > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > Erik > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >