Apache/Mason install notes

Ok, after 2.5 days of tearing out my hair I finally have RT2.0.4 running to
the point where I actually get an interface when I load up the page.

My last message about a warning message from Mason in the error_log file (
[warn] [Mason] Cannot resolve file to component:
/usr/local/apache/htdocs/rt/index.html (is file outside component root?) )
was apparently because Mason is not capable of accessing things through
simlinks (I was symlinking to the WebRT/html directory from the Apache
document root)

I had to bind a second IP to the server, and add the httpd.conf file entries
as given in the RT install guide (“The Web UI” section) and now I actually
get an interface.

This is for the archives, in case someone else comes asking with the same
questions.

Martin

|+ My last message about a warning message from Mason in the error_log file (
|+ [warn] [Mason] Cannot resolve file to component:
|+ /usr/local/apache/htdocs/rt/index.html (is file outside component root?) )
|+ was apparently because Mason is not capable of accessing things through
|+ simlinks (I was symlinking to the WebRT/html directory from the Apache
|+ document root)

Wouldn’t just symlinking this cause other problems as well? I have really
seen no reason to have to bind another IP address to my webserver just for
RT. I just followed the instructions in the installation guide, and it
worked fine with all the rest of my virtualhosts.

–darrin

Ok… sorry for all the posts, I like hearing other people’s ideas before
making changes to stuff in case I’m doing things wrong.

I have finally gotten everything to work after almost 3 days of work. I had
a virtual host with a seperate IP configured on the server which got me the
RT interface up and running but still had messed up images and links. I
finally got rid of the virtual hosts and just went with an alias to make
things simpler.

Here’s my new config options from httpd.conf

Alias /rt2 “/usr/local/rt2/WebRT/html”

RT2 config

PerlModule Apache::DBI
<Location /rt2>
PerlRequire /usr/local/rt2/bin/webmux.pl
SetHandler perl-script
PerlHandler RT::Mason

and from config.pm

$WebPath = “/rt2”;
$WebBaseURL = “http://192.168.10.1:80”;

Now I can access RT2 from http://192.168.10.1/rt2 perfectly. Thanks for the
help everyone, now I’m off to begin user configuration.

Martin

I have found that apache is much more resource-hungry when it is running RT
(having Mason and the like loaded up in each running instance I’m sure has
something to do with that).

The way I got around having these resource-hogging httpd’s running all my
webpages was simply to run apache on a different port for RT. So, I keep
two seperate config files, I setup a virtualhost called rt.domain.com and it
redirects the user to rt.domain.com:88/rt2/ – works great. This way, I
don’t have all the RT stuff in my virtualhosting httpd and it also makes it
really easy to move it off to its own server in the future (just change
rt.domain.com to point to the new address).

Just some food for thought…

Trevor Sky Garside
trevor@trevorsky.comFrom: “Martin Hemmings” mhemmings@trakonic.com
To: “rt-users-list” rt-users@lists.fsck.com
Sent: Thursday, August 09, 2001 10:29 AM
Subject: RE: [rt-users] Apache/Mason install notes

Ok… sorry for all the posts, I like hearing other people’s ideas before
making changes to stuff in case I’m doing things wrong.

I have finally gotten everything to work after almost 3 days of work. I
had
a virtual host with a seperate IP configured on the server which got me
the
RT interface up and running but still had messed up images and links. I
finally got rid of the virtual hosts and just went with an alias to make
things simpler.

Here’s my new config options from httpd.conf

Alias /rt2 “/usr/local/rt2/WebRT/html”

RT2 config

PerlModule Apache::DBI
<Location /rt2>
PerlRequire /usr/local/rt2/bin/webmux.pl
SetHandler perl-script
PerlHandler RT::Mason

and from config.pm

$WebPath = “/rt2”;
$WebBaseURL = “http://192.168.10.1:80”;

Now I can access RT2 from http://192.168.10.1/rt2 perfectly. Thanks for
the
help everyone, now I’m off to begin user configuration.

Martin

That’s rather similar to how I do things, except I install a
ProxyPass /rt http://localhost:88/rt

on the mail webserver for user convenience…On Thu, Aug 09, 2001 at 02:35:38PM -0700, Trevor Sky Garside wrote:

I have found that apache is much more resource-hungry when it is running RT
(having Mason and the like loaded up in each running instance I’m sure has
something to do with that).

The way I got around having these resource-hogging httpd’s running all my
webpages was simply to run apache on a different port for RT. So, I keep
two seperate config files, I setup a virtualhost called rt.domain.com and it
redirects the user to rt.domain.com:88/rt2/ – works great. This way, I
don’t have all the RT stuff in my virtualhosting httpd and it also makes it
really easy to move it off to its own server in the future (just change
rt.domain.com to point to the new address).

Just some food for thought…

Trevor Sky Garside
trevor@trevorsky.com

----- Original Message -----
From: “Martin Hemmings” mhemmings@trakonic.com
To: “rt-users-list” rt-users@lists.fsck.com
Sent: Thursday, August 09, 2001 10:29 AM
Subject: RE: [rt-users] Apache/Mason install notes

Ok… sorry for all the posts, I like hearing other people’s ideas before
making changes to stuff in case I’m doing things wrong.

I have finally gotten everything to work after almost 3 days of work. I
had
a virtual host with a seperate IP configured on the server which got me
the
RT interface up and running but still had messed up images and links. I
finally got rid of the virtual hosts and just went with an alias to make
things simpler.

Here’s my new config options from httpd.conf

Alias /rt2 “/usr/local/rt2/WebRT/html”

RT2 config

PerlModule Apache::DBI
<Location /rt2>
PerlRequire /usr/local/rt2/bin/webmux.pl
SetHandler perl-script
PerlHandler RT::Mason

and from config.pm

$WebPath = “/rt2”;
$WebBaseURL = “http://192.168.10.1:80”;

Now I can access RT2 from http://192.168.10.1/rt2 perfectly. Thanks for
the
help everyone, now I’m off to begin user configuration.

Martin


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

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

<Dr_Memory> the point is that words were exchanged. neurolinguistic
programming will do the rest. they should be showing up at my house
any day now.

yes same thing for us , we run it on a different apache process with a
different port … I first installed RT on a server who had 1 million
requests a day , and was impossible to afford the # of requests with rt, was
way too big. Now its on a standalone machine but i still run on a different
port… :slight_smile:

Regards,

Steve

Steve Poirier
Project manager
Inet-Technologies inc.From: “Trevor Sky Garside” rt-list@trevorsky.com
To: “rt-users-list” rt-users@lists.fsck.com
Sent: Thursday, August 09, 2001 5:35 PM
Subject: Re: [rt-users] Apache/Mason install notes

I have found that apache is much more resource-hungry when it is running
RT
(having Mason and the like loaded up in each running instance I’m sure has
something to do with that).

The way I got around having these resource-hogging httpd’s running all my
webpages was simply to run apache on a different port for RT. So, I keep
two seperate config files, I setup a virtualhost called rt.domain.com and
it
redirects the user to rt.domain.com:88/rt2/ – works great. This way, I
don’t have all the RT stuff in my virtualhosting httpd and it also makes
it
really easy to move it off to its own server in the future (just change
rt.domain.com to point to the new address).

Just some food for thought…

Trevor Sky Garside
trevor@trevorsky.com

----- Original Message -----
From: “Martin Hemmings” mhemmings@trakonic.com
To: “rt-users-list” rt-users@lists.fsck.com
Sent: Thursday, August 09, 2001 10:29 AM
Subject: RE: [rt-users] Apache/Mason install notes

Ok… sorry for all the posts, I like hearing other people’s ideas before
making changes to stuff in case I’m doing things wrong.

I have finally gotten everything to work after almost 3 days of work. I
had
a virtual host with a seperate IP configured on the server which got me
the
RT interface up and running but still had messed up images and links. I
finally got rid of the virtual hosts and just went with an alias to make
things simpler.

Here’s my new config options from httpd.conf

Alias /rt2 “/usr/local/rt2/WebRT/html”

RT2 config

PerlModule Apache::DBI
<Location /rt2>
PerlRequire /usr/local/rt2/bin/webmux.pl
SetHandler perl-script
PerlHandler RT::Mason

and from config.pm

$WebPath = “/rt2”;
$WebBaseURL = “http://192.168.10.1:80”;

Now I can access RT2 from http://192.168.10.1/rt2 perfectly. Thanks for
the
help everyone, now I’m off to begin user configuration.

Martin


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