RT2 Web interface issue Again

Michael_Bush · August 1, 2001, 1:40pm

Hey Jesse / Everyone:

I am new to the list but have been using RT 1.0.7 for some time now.
Request Tracker has been a blessing and my clients love it. I am trying to
get RT 2.0.4 working with PostgreSQL 7.0.3. I have everything installed
(make testdeps gave me an OK on everything) and the make install went great.
However, when going to the web interface, I get the following information
displayed. It looks like a Mason issue but unsure.

---------------- snip ----------------------

<& /Elements/Header, Title=>“Start page” &> <& /Elements/Tabs &>
<& /Elements/MyTickets &>
<& /Elements/MyRequests &>

         <& /Elements/Quicksearch &>

---------------- snip -----------------------

Any ideas on how to resolve the issue? I do have PerlHandler RT::Mason in
my httpd.conf file.

Thanks in advance.

Regards,

Mike Bush
Digital Minds International
http://www.DigitalMinds.net
Tel: 615-661-7900
Fax: 615-661-7949

Miroslav_Laus1 · August 1, 2001, 2:14pm

Hi!On Wed 01.Aug, Michael Bush wrote:

Hey Jesse / Everyone:

I am new to the list but have been using RT 1.0.7 for some time now.
Request Tracker has been a blessing and my clients love it. I am trying to
get RT 2.0.4 working with PostgreSQL 7.0.3. I have everything installed
(make testdeps gave me an OK on everything) and the make install went great.
However, when going to the web interface, I get the following information
displayed. It looks like a Mason issue but unsure.

---------------- snip ----------------------

<& /Elements/Header, Title=>“Start page” &> <& /Elements/Tabs &>
<& /Elements/MyTickets &>
<& /Elements/MyRequests &>
         <& /Elements/Quicksearch &> 
---------------- snip -----------------------

Any ideas on how to resolve the issue? I do have PerlHandler RT::Mason in
my httpd.conf file.

I’m fighting the same problem. A day ago I’ve upgraded my perl
from version 5 to 5.6.1. Just to be sure, I’ve recompiled my apache
with mod_perl 1.26 again and did a clean install of RT 2.0.4.
make testdeps is OK and I’m pretty sure I’ve installed all components
from scratch after upgrading perl. Now, what RT gives is the screen
meant above. And in the apache error-log I see following:

<–snip–>
[Wed Aug 1 10:00:41 2001] [notice] child pid 7977 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:41 2001] [notice] child pid 7976 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 8001 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 8000 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 7999 exit signal Segmentation fault (11)
<–/snip–>

every time a try to access RT web interface. This is just a cut, it gives
more segfaults than this five lines.
Just to be exact, before upgrading perl all went OK

Mirek

Jesse1 · August 1, 2001, 5:48pm

The display of <& blah &> means that you haven’t properly configured
apache to use RT’s mod_perl handler. I suspect that the segfaults are
related to mod_perl being compiled as a dso.

    -jOn Wed, Aug 01, 2001 at 04:14:58PM +0200, Miroslav Laus wrote:

Hi!

On Wed 01.Aug, Michael Bush wrote:
Hey Jesse / Everyone:

I am new to the list but have been using RT 1.0.7 for some time now.
Request Tracker has been a blessing and my clients love it. I am trying to
get RT 2.0.4 working with PostgreSQL 7.0.3. I have everything installed
(make testdeps gave me an OK on everything) and the make install went great.
However, when going to the web interface, I get the following information
displayed. It looks like a Mason issue but unsure.

---------------- snip ----------------------

<& /Elements/Header, Title=>“Start page” &> <& /Elements/Tabs &>
<& /Elements/MyTickets &>
<& /Elements/MyRequests &>
         <& /Elements/Quicksearch &> 
---------------- snip -----------------------

Any ideas on how to resolve the issue? I do have PerlHandler RT::Mason in
my httpd.conf file.
I’m fighting the same problem. A day ago I’ve upgraded my perl
from version 5 to 5.6.1. Just to be sure, I’ve recompiled my apache
with mod_perl 1.26 again and did a clean install of RT 2.0.4.
make testdeps is OK and I’m pretty sure I’ve installed all components
from scratch after upgrading perl. Now, what RT gives is the screen
meant above. And in the apache error-log I see following:

<–snip–>
[Wed Aug 1 10:00:41 2001] [notice] child pid 7977 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:41 2001] [notice] child pid 7976 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 8001 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 8000 exit signal Segmentation fault (11)
[Wed Aug 1 10:00:52 2001] [notice] child pid 7999 exit signal Segmentation fault (11)
<–/snip–>

every time a try to access RT web interface. This is just a cut, it gives
more segfaults than this five lines.
Just to be exact, before upgrading perl all went OK

Mirek

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

As I sit here alone looking at green text on a laptop in a mostly bare room listening
to loud music wearing all black, I realize that that it is much less cool in real life
–Richard Tibbetts

Ayan_R_Kayal · August 1, 2001, 5:54pm

To confirm, I had seg faults like crazy until I reinstalled mod_perl. It
didn’t take very well as a DSO.

O- ~ARK
Hmedicine.com, Inc.

Michael_Bush · August 2, 2001, 4:11am

Hi Jesse/Everyone:

I have just upgrade my mod_perl from 1.24 to mod_perl 1.26 via RPM and I
still get the same problem. I am so close. Everything else seems to work.

Any ideas? Any step by step instructions to resolve the issue?

Regards,

Mike Bush
Digital Minds International
http://www.DigitalMinds.net
Tel: 615-661-7900
Fax: 615-661-7949

Miroslav_Laus1 · August 2, 2001, 5:37am

The display of <& blah &> means that you haven’t properly configured
apache to use RT’s mod_perl handler. I suspect that the segfaults are
related to mod_perl being compiled as a dso.

This is my virtualhost configuration

DocumentRoot /opt/rt2/WebRT/html ServerName rt2.xxxx.cz ServerAlias rt2

    PerlModule                      Apache::DBI
    PerlRequire                     /opt/rt2/bin/webmux.pl

    SetHandler                      perl-script
    PerlHandler                     RT::Mason

and I’m sure I’ve compiled mod_perl INTO apache, not as DSO.
Any ideas now ?

Mirek

Darrin_Walton · August 2, 2001, 6:07am

Shouldn’t it be:

darrin walton, darrinw@nixc.net

Miroslav_Laus1 · August 2, 2001, 6:10am

Shouldn’t it be:

|+
|+ DocumentRoot /opt/rt2/WebRT/html
|+ ServerName rt2.xxxx.cz
|+ ServerAlias rt2
|+
|+ PerlModule Apache::DBI
|+ PerlRequire /opt/rt2/bin/webmux.pl
|+

SetHandler perl-script
PerlHandler RT::Mason

|+
|+

I’m sure it worked before. And while it was configured on the root
of the VirtualHost, I think it was correct to omit tag.

Mirek

Darrin_Walton · August 2, 2001, 6:25am

|+ I’m sure it worked before. And while it was configured on the root
|+ of the VirtualHost, I think it was correct to omit tag.

My RT installation is running as the root virtualhost (the machine only
serves the ticketing system), and I have the location tags.

Did you try to add those tags just to see what works?

darrin walton, darrinw@nixc.net

Miroslav_Laus1 · August 2, 2001, 6:33am

My RT installation is running as the root virtualhost (the machine only
serves the ticketing system), and I have the location tags.

Did you try to add those tags just to see what works?

Of course, at this point I would try anything just to make it work

Mirek