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 09:00:27 +0100 [thread overview]
Message-ID: <t8enur$ihr$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <dfd47242-c5f6-9162-e749-bf1ba4f541c9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
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.
Rob
next prev parent reply other threads:[~2022-06-16 8:00 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 [this message]
2022-06-16 11:53 ` Stefan Schantl
2022-06-16 12:36 ` Matthias Fischer
2022-06-16 12:47 ` Rob Brewer
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='t8enur$ihr$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