From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: Several errors in /var/log/httpd/error_log during Pakfire update to Core 168
Date: Thu, 16 Jun 2022 13:47:21 +0100 [thread overview]
Message-ID: <t8f8oq$k4v$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <e6c0dd5e-9529-ac8c-45f9-967673db6560@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 5102 bytes --]
Hi Matthias
On Thursday 16 June 2022 13:36 Matthias Fischer wrote:
> Hi Stefan,
>
> I think so - on my system this specific 'HTTP' dir is completely missing:
>
> ...
> root(a)ipfire: / # cd
> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/HTTP
> -bash: cd: HTTP: No such file or directory
> ...
>
> And the 'HTTP'-dir doesn't exist on Core 168, either (clean build, a few
> minutes ago):
>
> ...
> root(a)Devel64-1: /git/ipfire-2.x/build # cd
> usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/HTTP
> -bash: cd:
> usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/HTTP: No such
> file or directory
> ...
>
> I found 'Date.pm' in
> '/git/ipfire-2.x/config/rootfiles/common/perl-HTTP-Date':
>
> Contents:
> usr/lib/perl5/site_perl/5.32.1/HTTP/Date.pm
> #usr/lib/perl5/site_perl/5.32.1/xxxMACHINExxx-linux-thread-
multi/auto/HTTP/Date
> #usr/lib/perl5/site_perl/5.32.1/xxxMACHINExxx-linux-thread-
multi/auto/HTTP/Date/.packlist
> #usr/share/man/man3/HTTP::Date.3
>
> Something went wrong here...?
>
> Best,
> Matthias
>
Did you look for /usr/lib/perl5/site_perl/5.32.1/HTTP
I have
/usr/lib/perl5/5.32.1/HTTP
/usr/lib/perl5/5.32.1/HTTP/Tiny.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP
/usr/lib/perl5/site_perl/5.32.1/HTTP/Config.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Cookies
/usr/lib/perl5/site_perl/5.32.1/HTTP/Cookies.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Cookies/Microsoft.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Cookies/Netscape.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Daemon.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Date.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Headers
/usr/lib/perl5/site_perl/5.32.1/HTTP/Headers.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Headers/Auth.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Headers/ETag.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Headers/Util.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Message.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Negotiate.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Request
/usr/lib/perl5/site_perl/5.32.1/HTTP/Request.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Request/Common.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Response.pm
/usr/lib/perl5/site_perl/5.32.1/HTTP/Status.pm
/usr/lib/perl5/site_perl/5.32.1/LWP/Debug/TraceHTTP.pm
/usr/lib/perl5/site_perl/5.32.1/LWP/Protocol/GHTTP.pm
/usr/lib/perl5/site_perl/5.32.1/Net/DNS/RR/HTTPS.pm
/usr/lib/perl5/site_perl/5.32.1/Net/HTTP
/usr/lib/perl5/site_perl/5.32.1/Net/HTTP.pm
/usr/lib/perl5/site_perl/5.32.1/Net/HTTP/Methods.pm
/usr/lib/perl5/site_perl/5.32.1/Net/HTTP/NB.pm
/usr/lib/perl5/site_perl/5.32.1/Net/HTTPS.pm
Rob
> On 16.06.2022 13:53, Stefan Schantl wrote:
>> Hello Rob, Matthias and *,
>>> Hi *
>>>
>>> On Thursday 16 June 2022 08:10 Adolf Belka wrote:
>>>
>>> > Hi Matthias,
>>> >
>>> > On 16/06/2022 08:55, Matthias Fischer wrote:
>>> > > Hi all,
>>> > >
>>> > > although the update to Core 168 via pakfire ran without visible
>>> > > errors
>>> > > and system is up and running, I've found some errors in
>>> > > '/var/log/httpd/error_log' after upgrading - please see attached
>>> > > log.
>>> > >
>>> > > On the one hand there are several access errors:
>>> > >
>>> > > ...
>>> > > exec of '/srv/web/ipfire/cgi-bin/pakfire.cgi' failed
>>> > > ...
>>> > I also have the exec and permissions errors in my error_log
>>> > > On the other hand (verified) a perl library is missing:
>>> > >
>>> > > ...
>>> > > Can't locate HTTP/Date.pm:
>>> > > /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-
>>> > > multi/HTTP/Date.pm
>>> > > BEGIN failed--compilation aborted at
>>> > > /usr/lib/perl5/site_perl/5.32.1/LWP/UserAgent.pm line 11.
>>> > > Compilation failed in require at /opt/pakfire/lib/functions.pl
>>> > > line 27.
>>> > > BEGIN failed--compilation aborted at
>>> > > /opt/pakfire/lib/functions.pl line
>>> > > 27. Compilation failed in require at /srv/web/ipfire/cgi-
>>> > > bin/pakfire.cgi
>>> > > line 33.
>>> > > ...
>>> > Rob Brewer flagged this up in an email to the list on 5th June.
>>> > Adding
>>> > this module in was on my list of things to do now that I am back
>>> > from my
>>> > vacation.
>>> > > Can anone confirm? Should I raise a bug report?
>>> > I think that would be a good idea. My perl knowledge is not good
>>> > enough
>>> > to be able to figure out if the exec permissions issue is related
>>> > to the
>>> > missing perl module or is a separate issue.
>>> >
>>> > Regards,
>>> > Adolf.
>>> > > Best,
>>> > > Matthias
>>> >
>>> I have Date.pm on my CU 167 (stable) box so I dont't expect that is
>>> the
>>> issue. After I imported the Locale.pm module from my Debiaan PC I was
>>> able
>>> to run UserAgent.pm without errors.
>>
>> The perl HTTP::Date module has been added to the Core Distribution in
>> early February this year. The rootfile seems to be correct and points
>> to the core system - so the file always should be present on the
>> installed systems.
>>
>> If I remember correctly we had a similar issues with a suddenly removed
>> perl module some time ago (affected guardian).
>>
>> May this issue happened with this module again?
>>
>> Best regards,
>>
>> -Stefan
>>
>>>
>>> Rob
>>
>>
next prev parent reply other threads:[~2022-06-16 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 6:55 Matthias Fischer
2022-06-16 7:10 ` Adolf Belka
2022-06-16 7:53 ` Matthias Fischer
2022-06-16 13:33 ` Leo-Andres Hofmann
2022-06-16 8:00 ` Rob Brewer
2022-06-16 11:53 ` Stefan Schantl
2022-06-16 12:36 ` Matthias Fischer
2022-06-16 12:47 ` Rob Brewer [this message]
2022-06-16 12:49 ` Adolf Belka
2022-06-16 13:03 ` Matthias Fischer
2022-06-16 12:54 ` Rob Brewer
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='t8f8oq$k4v$1@tuscan3.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--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