Re: Several errors in /var/log/httpd/error_log during Pakfire update to Core 168

[Matthias Fischer <matthias.fischer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3500 bytes --]

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

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
> 
>