public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
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 14:49:40 +0200	[thread overview]
Message-ID: <e77cb0fc-ec83-e284-95c4-bfd562c4d5ad@ipfire.org> (raw)
In-Reply-To: <77976961a0eab43b8d99d35a36238153f1d3f8ba.camel@ipfire.org>

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

Hallo All,

When I looked at Matthias Error Log I saw what I expected to see based 
on what I remembered Rob's report had been related to.

Looking again, I see that I made an error with what I saw in Matthias 
report.

In Rob's report he had a problem with not being able to locate LWP/Locale.pm
In Matthias report he has a notification of not being able to locate 
HTTP/Date.pm
In my error report I have a notification of not being able to locate 
URI/Escape.pm

So all three of us have similar errors but all three related to 
different modules not being located.

In my case Escape.pm is in the URI directory and has the same 
permissions as the other .pm files in that directory.

Looking in the HTTP directory I find that Date.pm is present and has the 
permissions as other .pm files in that directory.

Looking in the LWP directory then there is no Locale.pm file so Rob's 
original report seems a correct issue but Matthias and my reports may 
have been some transitory effect during the upgrade.

Regards,
Adolf.


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
>

-- 
Sent from my laptop


  parent reply	other threads:[~2022-06-16 12:49 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
2022-06-16 12:49       ` Adolf Belka [this message]
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=e77cb0fc-ec83-e284-95c4-bfd562c4d5ad@ipfire.org \
    --to=adolf.belka@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