Summary: | Pakfire: Missing perl module(s) and access errors logged in '/var/log/httpd/error_log' during Core 168 update | ||
---|---|---|---|
Product: | IPFire | Reporter: | Matthias Fischer <matthias.fischer> |
Component: | --- | Assignee: | Peter Müller <peter.mueller> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | Minor Usability | ||
Priority: | - Unknown - | CC: | granturav8 |
Version: | 2 | ||
Hardware: | all | ||
OS: | Linux | ||
Attachments: | Logged errors during update to Core 168 |
First of all, apologies for my belated response. Since Core Update 168 has been released already, this is not much of a help anymore, but anyway: I completely agree that such errors are ugly. However, given that the IPFire user most likely will conduct the upgrade via the WUI rather than the CLI, the former will constantly try to access things like speed.cgi, which eventually breaks when we replace the underlying Perl packages. For future Core Updates, I will pay better attention to the update.sh contents, to ensure that we first stop all possibly affected services before deleting or extracting any files. Closing this as CANTFIX (but will keep it in mind); please reopen, if necessary. |
Created attachment 1057 [details] Logged errors during update to Core 168 Hi, during updating to Core 168 several errors were logged in '/var/log/httpd/error_log' (log is attached): ... exec of '/srv/web/ipfire/cgi-bin/pakfire.cgi' failed ... ... 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. ... Despite these errors, update went through - no visible errors. Seems to be related to an email Rob Brewer sent to the list on 5th June. Best, Matthias