From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Core 151 testing feedback Date: Sun, 11 Oct 2020 10:00:54 +0200 Message-ID: In-Reply-To: <81491e45e5efccc203ce2d8c3d4f1645ec2927bd.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7324206771701571881==" List-Id: --===============7324206771701571881== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =3D> https://bugzilla.ipfire.org/show_bug.cgi?id=3D12491 Confirmed. The mean part was https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D5f1039dda984ed3a06d= a95ba7d9248b759cf9125 MT and Fred found a solution (Thanks!). 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. Best, Matthias 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: >=20 > Can't locate Net/DNS/RR/NXT.pm in @INC (you may need to install the Net::DN= S::RR::NXT module) (@INC contains: /usr/lib/perl5/site_perl/5.30.0/x86_64-lin= ux-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-lin= ux-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-lin= ux-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-lin= ux-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-lin= ux-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-lin= ux-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 l= ine 26. > [Sun Oct 11 09:48:22.546603 2020] [cgid:error] [pid 8658:tid 12722323114553= 6] [client 192.168.75.2:58726] End of script output before headers: ovpnmain.= cgi >=20 >=20 > So it seems that some perl moduls are missing. Does someone have > similar problems ? >=20 > Best, >=20 > Erik >=20 >=20 >=20 > Am Sonntag, den 11.10.2020, 07:27 +0200 schrieb ummeegge: >> Good morning, >>=20 >> Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer: >> > Hi, >> >=20 >> > > On 9 Oct 2020, at 21:56, ummeegge wrote: >> > >=20 >> > > Hi all, >> > >=20 >> > > Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer: >> > > > Hello, >> > > >=20 >> > > > Could you please open a ticket on BZ for both of them? >> > >=20 >> > > Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=3D12495=20 >> > > https://bugzilla.ipfire.org/show_bug.cgi?id=3D12494 >> >=20 >> > Done and dealt with. >>=20 >> Great. >>=20 >> >=20 >> > > apart from that my Prime has been smoked up with a read-only file >> > > system and is gone into the "Ewige Jagd Gr=C3=BCnde" after a reboot >> > > but >> > > this >> > > might have other reasons but further testings/developments are >> > > currently a little awkward. >> >=20 >> > Software failure? >>=20 >> No the SSD died. >>=20 >> >=20 >> > -Michael >> >=20 >> > > Best from shit happens, >> > >=20 >> > > Erik >> > >=20 >> > >=20 >> > > >=20 >> > > > Best, >> > > > -Michael >> > > >=20 >> > > > > On 9 Oct 2020, at 12:46, ummeegge >> > > > > wrote: >> > > > >=20 >> > > > > Hi all, >> > > > > i wanted to report a problem with SSH after updating to core >> > > > > 151 >> > > > > testing. >> > > > >=20 >> > > > > SSH runs regular on port 222 after updating SSH runs on port >> > > > > 22 >> > > > > and >> > > > > wasn=C2=B4t reachable via the old settings. After pressing the >> > > > > save >> > > > > button >> > > > > in SSH section in the WUI everything worked again. >> > > > >=20 >> > > > > May someone else have that too ? >> > > > >=20 >> > > > > Also, /etc/os-release shows >> > > > >=20 >> > > > > PRETTY_NAME=3D"IPFire 2.25 (x86_64) - core145 Development >> > > > > Build: >> > > > > master/405c7326" >> > > > >=20 >> > > > > but /var/ipfire/fireinfo/profile shows the correct version >> > > > >=20 >> > > > > "release": "IPFire 2.25 (x86_64) - core151 Development Build: >> > > > > master/5e4126c3", >> > > > >=20 >> > > > > but apart from that no further problems so far. >> > > > >=20 >> > > > > Best, >> > > > >=20 >> > > > > Erik >> > > > >=20 >> > > > >=20 >> > > > >=20 >> > > >=20 >> > > >=20 >> >=20 >> >=20 >>=20 >>=20 >=20 --===============7324206771701571881==--