From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Errors during update to Core165 found in '/var/log/httpd/error_log'
Date: Fri, 01 Apr 2022 17:55:37 +0200 [thread overview]
Message-ID: <6f29b0be-9770-6ef5-c9af-6260c057b394@ipfire.org> (raw)
In-Reply-To: <7894e8fc-daa6-ab03-343f-5eddeabbf440@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
Hi,
just did the update to Core 166.
Checked the logs: no more errors: everything's clean.
Best,
Matthias
On 31.03.2022 21:33, Bernhard Bitsch wrote:
> Hi,
>
> I had some 'gimmicks' during the update process also.
> But I regarded them as a 'price' of my early update try ( the mirrors
> didn't show the CU first).
>
> Looking at Matthias' observation lets guess me, that the Perl modules
> were installed with the update first. Perl doesn't reread the include
> namespace. Therefore the modules are know not earlier than after a
> restart/reboot.
>
> Regards,
> Bernhard
>
> Am 31.03.2022 um 20:52 schrieb Matthias Fischer:
>> Hi,
>>
>> I've found the missing files:
>>
>> ...
>> root(a)ipfire: / # find -name Ping.pm
>> ./usr/lib/perl5/5.32.1/Net/Ping.pm
>> root(a)ipfire: / # find -name Copy.pm
>> ./usr/lib/perl5/5.32.1/File/Copy.pm
>> ...
>>
>> It seems, 'pakfire.cgi' searches in the wrong directory...
>>
>> But I must confess - I have no idea how to fix this.
>>
>> Best,
>> Matthias
>>
>> On 31.03.2022 19:22, Adolf Belka wrote:
>>> Hi Matthias,
>>>
>>> I have found similar messages on my system but some of them are from around when I did the upgrade from CU164 to CU165.
>>>
>>>
>>> Additionally I have the same messages with earlier time stamps, previous day, which would have been from when it was still running as CU164.
>>>
>>> I have just checked the timestamp for my CU165 log and it is after the messages. So all those messages were from when IPFire was running as CU164.
>>>
>>>
>>> Regards,
>>>
>>> Adolf
>>>
>>> On 31/03/2022 19:09, Matthias Fischer wrote:
>>>> Hi,
>>>>
>>>> first: update to Core 165 ran through - no seen errors. Pakfire looked
>>>> good, system is running with .
>>>>
>>>> But after digging deeper in the logs I found some errors that made me
>>>> ...nervous...:
>>>>
>>>> Looking at '/var/log/httpd/error_log' I found a bunch of "tac: write
>>>> error: Broken pipe", some "Permission denied:"-messages regarding
>>>> 'pakfire.cgi', some Perl errors and a "Could not open password file:
>>>> /var/ipfire/auth/users"-error. I wouldn't have noticed if I hadn't take
>>>> a closer look.
>>>>
>>>> In detail:
>>>> Perl couldn't locate two files - "Net/Ping.pm" and "File/Copy.pm" needed
>>>> by '/opt/pakfire/lib/functions.pl'. These doesn't exist.
>>>>
>>>> Current log file ('/var/log/httpd/error_log') is attached.
>>>>
>>>> Nevertheless - system is up and running. WebGui is running.
>>>>
>>>> Can anyone confirm?
>>>>
>>>> Best,
>>>> Matthias
>>
next parent reply other threads:[~2022-04-01 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7894e8fc-daa6-ab03-343f-5eddeabbf440@ipfire.org>
2022-04-01 15:55 ` Matthias Fischer [this message]
2022-05-07 12:50 ` Leo Hofmann
2022-05-12 9:50 ` Michael Tremer
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=6f29b0be-9770-6ef5-c9af-6260c057b394@ipfire.org \
--to=matthias.fischer@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