Bug 122891 - Can't locate object method "boot"
Summary: Can't locate object method "boot"
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_perl
Version: 1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-10 03:05 UTC by Gunnar Hjalmarsson
Modified: 2007-11-30 22:10 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-05-16 07:30:56 UTC


Attachments (Terms of Use)

Description Gunnar Hjalmarsson 2004-05-10 03:05:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007

Description of problem:
No errors were reported when installing the mod_perl RPM distribution
from the Fedora download server. However, running a simple "Hello
World" script resulted in "Internal Server Error" and this complaint
in the error log:

Can't locate object method "boot" via package "mod_perl" at
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi/Apache/Log.pm
line 6.


Version-Release number of selected component (if applicable):
mod_perl-1.99_09-10

How reproducible:
Always

Steps to Reproduce:
Step-by-step description not needed.


Additional info:

The Apache/Log.pm module, that causes the error, is not very big:

1. package Apache::Log;
2.
3. use mod_perl ();
4.
5. $VERSION = '1.01';
6. __PACKAGE__->mod_perl::boot($VERSION);
7.
8. 1;
9. __END__

To be able to run my test script, I have either commented out line 6
or simply renamed the whole file. (There is another Apache/Log.pm file
in @INC, with different code, and having two modules with identical
names seems a little odd anyway...).

I have no idea if my quick fix is appropriate, or if there are adverse
implications.

Comment 1 Gunnar Hjalmarsson 2004-05-16 07:30:56 UTC
I believe that this was a 'user bug' rather than anything wrong with
the mod_perl distribution. See the thread in redhat-list that started
with: http://www.redhat.com/archives/redhat-list/2004-May/msg00574.html



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