* Core 151 testing feedback @ 2020-10-09 11:46 ummeegge 2020-10-09 14:26 ` Michael Tremer 2020-10-09 19:31 ` Peter Müller 0 siblings, 2 replies; 16+ messages in thread From: ummeegge @ 2020-10-09 11:46 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 649 bytes --] 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-09 11:46 Core 151 testing feedback ummeegge @ 2020-10-09 14:26 ` Michael Tremer 2020-10-09 20:56 ` ummeegge 2020-10-09 19:31 ` Peter Müller 1 sibling, 1 reply; 16+ messages in thread From: Michael Tremer @ 2020-10-09 14:26 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 862 bytes --] Hello, Could you please open a ticket on BZ for both of them? 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 > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-09 14:26 ` Michael Tremer @ 2020-10-09 20:56 ` ummeegge 2020-10-10 11:52 ` Michael Tremer 0 siblings, 1 reply; 16+ messages in thread From: ummeegge @ 2020-10-09 20:56 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1361 bytes --] 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 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. 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 > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-09 20:56 ` ummeegge @ 2020-10-10 11:52 ` Michael Tremer 2020-10-11 5:27 ` ummeegge 0 siblings, 1 reply; 16+ messages in thread From: Michael Tremer @ 2020-10-10 11:52 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1527 bytes --] 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. > 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? -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 >>> >>> >>> >> >> > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-10 11:52 ` Michael Tremer @ 2020-10-11 5:27 ` ummeegge 2020-10-11 7:52 ` ummeegge 0 siblings, 1 reply; 16+ messages in thread From: ummeegge @ 2020-10-11 5:27 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1863 bytes --] 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 > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-11 5:27 ` ummeegge @ 2020-10-11 7:52 ` ummeegge 2020-10-11 8:00 ` Matthias Fischer 0 siblings, 1 reply; 16+ messages in thread From: ummeegge @ 2020-10-11 7:52 UTC (permalink / raw) To: development [-- 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-11 7:52 ` ummeegge @ 2020-10-11 8:00 ` Matthias Fischer 2020-10-11 11:57 ` ummeegge 0 siblings, 1 reply; 16+ messages in thread From: Matthias Fischer @ 2020-10-11 8:00 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 5148 bytes --] 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!). 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: > > 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 >> > > > > >> > > > > >> > > > > >> > > > >> > > > >> > >> > >> >> > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-11 8:00 ` Matthias Fischer @ 2020-10-11 11:57 ` ummeegge 2020-10-11 16:29 ` Matthias Fischer 0 siblings, 1 reply; 16+ messages in thread From: ummeegge @ 2020-10-11 11:57 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 6087 bytes --] 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 <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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-11 11:57 ` ummeegge @ 2020-10-11 16:29 ` Matthias Fischer 0 siblings, 0 replies; 16+ messages in thread From: Matthias Fischer @ 2020-10-11 16:29 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 828 bytes --] Hi, [unneeded stuff deleted] On 11.10.2020 13:57, ummeegge wrote: > ... >> 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 > *Sigh* You're right. I'm in the need of holidays... Wrote patch. Tested. Works. Please confirm. => https://bugzilla.ipfire.org/show_bug.cgi?id=12491#c9 I also added it here. Please find attached an updated 'update.sh' plus a proposed patch for Core 151 for .../config/rootfiles/core/151'. I didn't want to push this to the 'master' branch and something like https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/core151 doesn't exist yet. Best, Matthias [-- Attachment #2: update.sh --] [-- Type: text/plain, Size: 2812 bytes --] #!/bin/bash ############################################################################ # # # This file is part of the IPFire Firewall. # # # # IPFire is free software; you can redistribute it and/or modify # # it under the terms of the GNU General Public License as published by # # the Free Software Foundation; either version 3 of the License, or # # (at your option) any later version. # # # # IPFire is distributed in the hope that it will be useful, # # but WITHOUT ANY WARRANTY; without even the implied warranty of # # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # # GNU General Public License for more details. # # # # You should have received a copy of the GNU General Public License # # along with IPFire; if not, write to the Free Software # # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA # # # # Copyright (C) 2020 IPFire-Team <info@ipfire.org>. # # # ############################################################################ # . /opt/pakfire/lib/functions.sh /usr/local/bin/backupctrl exclude >/dev/null 2>&1 core=151 # Remove old core updates from pakfire cache to save space... for (( i=1; i<=$core; i++ )); do rm -f /var/cache/pakfire/core-upgrade-*-$i.ipfire done # Remove files rm -rfv \ /usr/lib/perl5/site_perl/5.30.0/Locale rm -rfv \ /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS rm -fv \ /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS.pm # Stop services /etc/init.d/ipsec stop # Extract files extract_files # update linker config ldconfig # Update Language cache /usr/local/bin/update-lang-cache # Filesytem cleanup /usr/local/bin/filesystem-cleanup # Apply local configuration to sshd_config /usr/local/bin/sshctrl # Start services /etc/init.d/sshd restart if grep -q "ENABLED=on" /var/ipfire/vpn/settings; then /etc/init.d/ipsec start fi /etc/init.d/collectd restart # Reload sysctl.conf sysctl -p # This update needs a reboot... #touch /var/run/need_reboot # Finish /etc/init.d/fireinfo start sendprofile # Update grub config to display new core version if [ -e /boot/grub/grub.cfg ]; then grub-mkconfig -o /boot/grub/grub.cfg fi sync # Don't report the exitcode last command exit 0 [-- Attachment #3: core151_fix_for_net-dns_problem.patch --] [-- Type: text/plain, Size: 452 bytes --] diff --git a/config/rootfiles/core/151/update.sh b/config/rootfiles/core/151/update.sh index 699528274..fa7e3a3bf 100644 --- a/config/rootfiles/core/151/update.sh +++ b/config/rootfiles/core/151/update.sh @@ -34,6 +34,10 @@ done # Remove files rm -rfv \ /usr/lib/perl5/site_perl/5.30.0/Locale +rm -rfv \ + /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS +rm -fv \ + /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS.pm # Stop services /etc/init.d/ipsec stop ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-09 11:46 Core 151 testing feedback ummeegge 2020-10-09 14:26 ` Michael Tremer @ 2020-10-09 19:31 ` Peter Müller 2020-10-11 11:18 ` Adolf Belka 1 sibling, 1 reply; 16+ messages in thread From: Peter Müller @ 2020-10-09 19:31 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1356 bytes --] Hello *, upcoming Core Update 151 (testing) still contains some glitches. > 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 ? Yes, I bumped into that as well. > 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", This issue can be reproduced here. > but apart from that no further problems so far. The IPsec and OpenVPN CGIs are rendered unusable in Core Update 151 at the time of writing, most probably due to a missing Perl dependency in Net::DNS. This issue is tracked as #12491 and is currently a show-stopper from my point of view. Further, the Tor CGI did not call some location module functions properly, which is tracked as #12492 and fixed by https://patchwork.ipfire.org/patch/3519/. Notices regarding IP addresses belonging to anonymous proxies, satellite providers or anycast services are a bit messy and not translated into German, but this is only a minor issue. Thanks, and best regards, Peter Müller ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-09 19:31 ` Peter Müller @ 2020-10-11 11:18 ` Adolf Belka 2020-10-11 11:58 ` Adolf Belka 0 siblings, 1 reply; 16+ messages in thread From: Adolf Belka @ 2020-10-11 11:18 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1610 bytes --] Hi everyone, On 09/10/2020 21:31, Peter Müller wrote: > Hello *, > > upcoming Core Update 151 (testing) still contains some glitches. > >> 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 ? > > Yes, I bumped into that as well. The ssh effect did not happen to me. I updated to core 151 and rebooted and after that was able to ssh in with port 222 as normal. > >> 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", > > This issue can be reproduced here. > >> but apart from that no further problems so far. > > The IPsec and OpenVPN CGIs are rendered unusable in Core Update 151 at the time > of writing, most probably due to a missing Perl dependency in Net::DNS. This > issue is tracked as #12491 and is currently a show-stopper from my point of view. > > Further, the Tor CGI did not call some location module functions properly, which > is tracked as #12492 and fixed by https://patchwork.ipfire.org/patch/3519/. > > Notices regarding IP addresses belonging to anonymous proxies, satellite providers > or anycast services are a bit messy and not translated into German, but this is > only a minor issue. > > Thanks, and best regards, > Peter Müller > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 testing feedback 2020-10-11 11:18 ` Adolf Belka @ 2020-10-11 11:58 ` Adolf Belka 0 siblings, 0 replies; 16+ messages in thread From: Adolf Belka @ 2020-10-11 11:58 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1956 bytes --] Hi everyone, I also found the mismatch in os-release but in my case it showed:- PRETTY_NAME="IPFire 2.25 (x86_64) - core147" fireinfo/profile showed:- "release": "IPFire 2.25 (x86_64) - core151 Development Build: master/a9f69cbf" Regards, Adolf On 11/10/2020 13:18, Adolf Belka wrote: > Hi everyone, > > > On 09/10/2020 21:31, Peter Müller wrote: >> Hello *, >> >> upcoming Core Update 151 (testing) still contains some glitches. >> >>> 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 ? >> >> Yes, I bumped into that as well. > The ssh effect did not happen to me. I updated to core 151 and rebooted and after that was able to ssh in with port 222 as normal. >> >>> 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", >> >> This issue can be reproduced here. >> >>> but apart from that no further problems so far. >> >> The IPsec and OpenVPN CGIs are rendered unusable in Core Update 151 at the time >> of writing, most probably due to a missing Perl dependency in Net::DNS. This >> issue is tracked as #12491 and is currently a show-stopper from my point of view. >> >> Further, the Tor CGI did not call some location module functions properly, which >> is tracked as #12492 and fixed by https://patchwork.ipfire.org/patch/3519/. >> >> Notices regarding IP addresses belonging to anonymous proxies, satellite providers >> or anycast services are a bit messy and not translated into German, but this is >> only a minor issue. >> >> Thanks, and best regards, >> Peter Müller >> ^ permalink raw reply [flat|nested] 16+ messages in thread
* Core 151 Testing feedback @ 2020-10-11 11:29 Adolf Belka 2020-10-12 10:14 ` Michael Tremer 0 siblings, 1 reply; 16+ messages in thread From: Adolf Belka @ 2020-10-11 11:29 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 259 bytes --] Hallo All, Other than the OpenVPN and IPSec page issues mentioned by other people I have not found any other problems. I can confirm that the bacula update to 9.6.6 works fine in Core 151, with a successful backup carried out. Regards, Adolf ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 Testing feedback 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 0 siblings, 1 reply; 16+ messages in thread From: Michael Tremer @ 2020-10-12 10:14 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 386 bytes --] > On 11 Oct 2020, at 12:29, Adolf Belka <ahb.ipfire(a)gmail.com> wrote: > > Hallo All, > > Other than the OpenVPN and IPSec page issues mentioned by other people I have not found any other problems. Which are those? > > I can confirm that the bacula update to 9.6.6 works fine in Core 151, with a successful backup carried out. > > > Regards, > > Adolf > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 Testing feedback 2020-10-12 10:14 ` Michael Tremer @ 2020-10-12 11:14 ` Adolf Belka 2020-10-12 13:10 ` Michael Tremer 0 siblings, 1 reply; 16+ messages in thread From: Adolf Belka @ 2020-10-12 11:14 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 698 bytes --] Hi Michael, Both pages come up with a page with an internal server error. Erik mentioned it for the OpenVPN WUI and Peter mentioned it for both the OpenVPN and IPSec pages. Peter mentioned bug #12491 as tracking the issue. Regards, Adolf. On 12/10/2020 12:14, Michael Tremer wrote: > > >> On 11 Oct 2020, at 12:29, Adolf Belka <ahb.ipfire(a)gmail.com> wrote: >> >> Hallo All, >> >> Other than the OpenVPN and IPSec page issues mentioned by other people I have not found any other problems. > > Which are those? > >> >> I can confirm that the bacula update to 9.6.6 works fine in Core 151, with a successful backup carried out. >> >> >> Regards, >> >> Adolf >> > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Core 151 Testing feedback 2020-10-12 11:14 ` Adolf Belka @ 2020-10-12 13:10 ` Michael Tremer 0 siblings, 0 replies; 16+ messages in thread From: Michael Tremer @ 2020-10-12 13:10 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 927 bytes --] Oh the Net:DNS module one. Got you now… That has a fix that is currently being tested and I asked Matthias to submit a patch. > On 12 Oct 2020, at 12:14, Adolf Belka <ahb.ipfire(a)gmail.com> wrote: > > Hi Michael, > > Both pages come up with a page with an internal server error. > Erik mentioned it for the OpenVPN WUI and Peter mentioned it for both the OpenVPN and IPSec pages. Peter mentioned bug #12491 as tracking the issue. > > Regards, > Adolf. > > On 12/10/2020 12:14, Michael Tremer wrote: >>> On 11 Oct 2020, at 12:29, Adolf Belka <ahb.ipfire(a)gmail.com> wrote: >>> >>> Hallo All, >>> >>> Other than the OpenVPN and IPSec page issues mentioned by other people I have not found any other problems. >> Which are those? >>> >>> I can confirm that the bacula update to 9.6.6 works fine in Core 151, with a successful backup carried out. >>> >>> >>> Regards, >>> >>> Adolf >>> ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2020-10-12 13:10 UTC | newest] Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-10-09 11:46 Core 151 testing feedback 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 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox