Closed
Bug 176064
Opened 23 years ago
Closed 23 years ago
When I try to get to index.cgi - get an exception trace
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: haranath, Assigned: zach)
Details
Attachments
(1 file)
|
4.69 KB,
text/plain
|
Details |
Hi,
I just installed Bugzilla 2.16 on a RH7.3. I ran checksetup.pl and everything
cameout to be fine (did not install the optional charting component).
When I then try to go to the index.cgi via my browser I get the following stack
trace.
Pls help
Thanks
Haranath
Bugzilla has suffered an internal error. Please save this page and send it to
THE MAINTAINER HAS NOT YET BEEN SET with details of what you were doing at the
time this message appeared.
URL: http://localhost/bugzilla/index.cgi
Template->process() failed twice.
First error: Uncaught exception from user code: Template::Exception at
/usr/lib/perl5/5.6.1/CGI/Carp.pm line 301.
CGI::Carp::realdie('Template::Exception') called at
/usr/lib/perl5/5.6.1/CGI/Carp.pm line 371 CGI::Carp::die('Template::Exception')
called at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Context.pm line 452
Template::Context::throw('Template::Context=HASH(0x857bf90)', 'file', 'cache
failed to write index.html.tmpl: Uncaught exception from u...') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Context.pm line 137
Template::Context::template('Template::Context=HASH(0x857bf90)',
'index.html.tmpl') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Service.pm line 67 eval {...}
called at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Service.pm line 67
Template::Service::process('Template::Service=HASH(0x83ecb00)',
'index.html.tmpl', 'HASH(0x859a0dc)') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template.pm line 59
Template::process('Template=HASH(0x83f1b20)', 'index.html.tmpl',
'HASH(0x859a0dc)') called at /opt/apache/bugzilla-2.16/index.cgi line 62
Second error: Uncaught exception from user code: mkdir
data/template/en/default/global: Permission denied at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Provider.pm line 837
Carp::croak('mkdir data/template/en/default/global: Permission denied') called
at /usr/lib/perl5/5.6.1/File/Path.pm line 140
File::Path::mkpath('data/template/en/default/global') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Provider.pm line 837
Template::Provider::_compile('Template::Provider=HASH(0x855b6d0)',
'HASH(0x8679b48)', 'data/template/en/default/global/code-error.html.tmpl')
called at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Provider.pm line
522 Template::Provider::_fetch_path('Template::Provider=HASH(0x855b6d0)',
'global/code-error.html.tmpl') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Provider.pm line 127
Template::Provider::fetch('Template::Provider=HASH(0x855b6d0)',
'global/code-error.html.tmpl', undef) called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Context.pm line 133
Template::Context::template('Template::Context=HASH(0x857bf90)',
'global/code-error.html.tmpl') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Service.pm line 67 eval {...}
called at /usr/lib/perl5/site_perl/5.6.1/i386-linux/Template/Service.pm line 67
Template::Service::process('Template::Service=HASH(0x83ecb00)',
'global/code-error.html.tmpl', 'HASH(0x859a0dc)') called at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Template.pm line 59
Template::process('Template=HASH(0x83f1b20)', 'global/code-error.html.tmpl',
'HASH(0x859a0dc)') called at CGI.pl line 956 main::ThrowTemplateError('Uncaught
exception from user code:^J^ITemplate::Exception at /usr/...') called at
/opt/apache/bugzilla-2.16/index.cgi line 62
Comment 1•23 years ago
|
||
Haranath:
Under what userid is your webserver running? Please also provide the
results on "ls -l . data templates " in your main Bugzilla directory and the
contents of your localconfig file (minus, of course, your password).
To begin with I'm using extremely poor security (this is a test instance) and
right now apache is running under root.
ls -al for the data folder is
-rwxrwxrwx 1 root nobody 4832 Oct 7 16:32 params
drwxr-xr-x 3 root nobody 4096 Oct 7 16:32 template
Comment 4•23 years ago
|
||
It is quite likely that your webserver is actually switching to another ID
immediately after starting. Look in your httpd.conf file for something like....
User nobody
Group #-1
(or just include the httpd.conf file here)
These need to be a real user and group and the webservergroup in localconfig
needs to be the same group. Then, rerun checksetup and see what happens.
Hmmm, I just was looking the processes running and I see...
root 10261 1 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10262 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10263 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10264 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10265 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10266 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
nobody 10267 10261 0 Oct21 ? 00:00:00 /opt/apache/bin/httpd -k start
haranath 11220 1396 0 17:31 pts/1 00:00:00 grep httpd
I did check the httpd.conf and it has
User nobody
Group #-1
and the localconfig file also has
$webservergroup = "nobody";
Comment 6•23 years ago
|
||
nobody is a special user. There are 2 ways you can approach this...
1) (preferred) Create a user and group for the webserver (like "www" for the
user and "www" for the group) and specify them in both files, and make sure that
the user "www" is a member of group "www".
2) change webservergroup to be = "" so that checksetup will make those
directories publicly accessible.
Thanks much. That worked, I created a new www user and a www group and its
working fine now.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 8•23 years ago
|
||
Just to keep stats correct reopening and changing resolution status. (since
there is no code change)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•23 years ago
|
||
marking invalid.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Severity: major → trivial
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•