Bug 104943 - After updating to Apache 1.3.27-2.7.1 and Perl 5.6.1 on Sept 23, the httpd server would not start.
Summary: After updating to Apache 1.3.27-2.7.1 and Perl 5.6.1 on Sept 23, the httpd se...
Keywords:
Status: CLOSED DUPLICATE of bug 104888
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.1
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-23 19:21 UTC by Andrew McNeil
Modified: 2006-02-21 18:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:58:41 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrew McNeil 2003-09-23 19:21:23 UTC 
Description of problem:

After updating to Apache 1.3.27-2.7.1 and Perl 5.6.1 on Sept 23 using the
up2date utility, the httpd server will not restart.

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

Apache 1.3.27-2.7.1 and Perl 5.6.1

How reproducible:

Always

Steps to Reproduce:
1. Update httpd and Perl
2. /sbin/service restart
3. Error message is produced to stdout
    
Actual results:

httpd exits with an error, does not start

Expected results:

httpd starts

Additional info:

Unexpected bummer. This is a production server which serves between 10k and 100k
http requests per week.
Comment 1 Andrew McNeil 2003-09-23 19:23:50 UTC 
Error Report:

Sep 23 12:18:25 dan httpd: httpd shutdown succeeded
Sep 23 12:18:26 dan httpd: [Tue Sep 23 12:18:26 2003] [error] Can't locate
strict.pm in @INC (@INC contains: /usr/lib/perl5/5.6.0/i386-linux
/usr/lib/perl5/5.6.0 /usr/lib/perl5/site_perl/5.6.0/i386-linux
/usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl . /etc/httpd/
/etc/httpd/lib/perl) at /usr/lib/perl5/site_perl/5.6.0/i386-linux/Apache.pm line
3.!BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Apache.pm line 3.!Compilation failed
in require at (eval 1) line 3.!
Comment 2 Jon Warbrick 2003-09-24 09:19:08 UTC 
In case you hadn't noticed, this looks to be a DUPL of

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104888

which contains a work-around that does work.
Comment 3 Joe Orton 2004-01-03 18:52:36 UTC 

*** This bug has been marked as a duplicate of 104888 ***
Comment 4 Red Hat Bugzilla 2006-02-21 18:58:41 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.