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 ...
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. ...
Can anone confirm? Should I raise a bug report?
Best, Matthias
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
Hi,
filed as #12877:
https://bugzilla.ipfire.org/show_bug.cgi?id=12877
Best, Matthias
On 16.06.2022 09: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
Hi Matthias,
This reminds me of a problem you mentioned back in March: https://lists.ipfire.org/pipermail/development/2022-March/012974.html
Could this be related? I have noticed similar errors as well. But I have never been able to find the cause or reproduce them reliably at least.
Regards, Leo
Am 16.06.2022 um 09:53 schrieb Matthias Fischer:
Hi,
filed as #12877:
https://bugzilla.ipfire.org/show_bug.cgi?id=12877
Best, Matthias
On 16.06.2022 09: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
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
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
Hi Stefan,
I think so - on my system this specific 'HTTP' dir is completely missing:
... root@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@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
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@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@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
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
Please see comments below...
On 16.06.2022 14:49, Adolf Belka wrote:
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.
Confirmed.
Looking in the HTTP directory I find that Date.pm is present and has the permissions as other .pm files in that directory.
I found 'Date.pm': './usr/lib/perl5/site_perl/5.32.1/HTTP/Date.pm' and './usr/lib/perl5/site_perl/5.32.1/Mail/Field/Date.pm'.
Rights for both/all: -r--r--r-- (100444) / root:root
Looking in the LWP directory then there is no Locale.pm file...
I found 'Locale.pm' in './usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/Unicode/Collate/Locale.pm'. Rights as above: 100444 / root:root
HTH
...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
Hi Stefan, Matthias ++
On Thursday 16 June 2022 12: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
I think the new lines in the latest version of UserAgent.pm are which wern't in the previous version:
sub env_proxy { my ($self) = @_; require Encode; require Encode::Locale; my $env_request_method= $ENV{REQUEST_METHOD}; my %seen; foreach my $k (sort keys %ENV) {
which calls for Encode::Locale which isn't present.
Regards
Rob
-
Adolf Belka -
Leo-Andres Hofmann -
Matthias Fischer -
Rob Brewer -
Stefan Schantl