Bug 14166 - apache-mod_perl can't load libperl.so
Summary: apache-mod_perl can't load libperl.so
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-24 16:52 CEST by Bit Twister
Modified: 2014-10-09 12:05 CEST (History)
4 users (show)

See Also:
Source RPM: apache-mod_perl
CVE:
Status comment:


Attachments

Description Bit Twister 2014-09-24 16:52:18 CEST
Description of problem:

Snippet from journal

httpd: Syntax error on line 54 of /etc/httpd/conf/httpd.conf: Syntax error on line 10 of /etc/httpd/conf/modules.d/02-perl.conf: Cannot load modules/mod_perl.so into server: libperl.so: cannot open shared object file: No such file or directory


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. systemctl enable httpd
2. systemctl start httpd
3. systemctl status httpd



Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2014-10-05 09:28:31 CEST
$ locate mod_perl.so
/usr/lib64/httpd/modules/mod_perl.so

Source RPM: apache-2.4.10-4.mga5.src.rpm => apache-2.4.10-5.mga5

Comment 2 David Walser 2014-10-08 00:44:16 CEST
02-perl.conf comes from apache-mod_perl, not apache.

Is this bug still valid?  I'm guessing it's related to all the troubles with perl autoreq/autoprov during the mass rebuild, which is supposed to mostly sorted out now IINM.

CC: (none) => thierry.vignaud
Summary: 5a2: httpd: Syntax error line 54 /etc/httpd/conf/httpd.conf => apache-mod_perl can't load libperl.so
Source RPM: apache-2.4.10-5.mga5 => apache-mod_perl

Comment 3 Bit Twister 2014-10-08 05:19:05 CEST
(In reply to David Walser from comment #2)
 
> Is this bug still valid?  

Yes.
David Walser 2014-10-08 16:52:34 CEST

CC: (none) => jquelin, mageia, pterjan

Comment 4 Bit Twister 2014-10-09 12:05:39 CEST
Latest updates resolve the problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.