Closed Bug 398548 Opened 18 years ago Closed 18 years ago

Can't locate Bugzilla/Auth/Login/.pm

Categories

(Bugzilla :: Installation & Upgrading, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: mark, Unassigned)

References

()

Details

User-Agent: Opera/9.23 (Windows NT 5.1; U; en) Build Identifier: bugzilla-3.0.2.tar.gz After installation, i've tried to access the interface. I'm presented with: [Thu Oct 04 08:17:10 2007] [error] Can't locate Bugzilla/Auth/Login/.pm in @INC (@INC contains: . /home/admin/domains/intelligentflight.com.au/public_html/bugzilla /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 /etc/httpd) at /home/admin/domains/intelligentflight.com.au/public_html/bugzilla/Bugzilla/Auth/Login/Stack.pm line 36. In my log files. This is no thte SELinux bug it would appear: [root@linux bugzilla]# getenforce Disabled I have suEXEC installed, however have applied every fix i could find. Reproducible: Always Steps to Reproduce: 1. Once installed, the error occurs when attempting to access the web interface Actual Results: The website presented a 500 internal server error, and the log entry entered into Details Expected Results: Shown the bugzilla interface.. i presume. checksetup.pl has been run many times to no avail, leading to me running through fixing file permissions every time.
If SuExec is disabled, does this fix your problem? The error you get looks so similar to bug 380077 that I would be surprised if they had no relation.
suexec has its own logfile (usually /var/log/httpd/suexec.log). If suexec is causing problems it'll be logged there.
This is an SELinux or permissions problem.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.