From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 151 testing feedback
Date: Sun, 11 Oct 2020 09:52:15 +0200 [thread overview]
Message-ID: <81491e45e5efccc203ce2d8c3d4f1645ec2927bd.camel@ipfire.org> (raw)
In-Reply-To: <6eb60401e4f138f3671827476331df8c4586087c.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4539 bytes --]
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 <ummeegge(a)ipfire.org> 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 <ummeegge(a)ipfire.org>
> > > > > 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
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> >
> >
>
>
next prev parent reply other threads:[~2020-10-11 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 11:46 ummeegge
2020-10-09 14:26 ` Michael Tremer
2020-10-09 20:56 ` ummeegge
2020-10-10 11:52 ` Michael Tremer
2020-10-11 5:27 ` ummeegge
2020-10-11 7:52 ` ummeegge [this message]
2020-10-11 8:00 ` Matthias Fischer
2020-10-11 11:57 ` ummeegge
2020-10-11 16:29 ` Matthias Fischer
2020-10-09 19:31 ` Peter Müller
2020-10-11 11:18 ` Adolf Belka
2020-10-11 11:58 ` Adolf Belka
2020-10-11 11:29 Core 151 Testing feedback Adolf Belka
2020-10-12 10:14 ` Michael Tremer
2020-10-12 11:14 ` Adolf Belka
2020-10-12 13:10 ` Michael Tremer
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=81491e45e5efccc203ce2d8c3d4f1645ec2927bd.camel@ipfire.org \
--to=ummeegge@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