The solution that worked for me last night
was to run completely separate instances of
httpd for each RT instance, instead of using
vhost definitions under 1 httpd instance.
On 3/23/2010 6:26 PM, Jeff Blaine wrote:
Adding some 'warn' statements to Mason/Resolver/File.pm
in
This has me really scratching my head. If it makes any
difference, this host (rtdev1) serves two separate RT
instances, each on different ports. The other is working
fine
rtdev1 RT: [Mason] Cannot resolve file to component:
/apps/rt_rtsrv1_dev/share/html/index.html (is file outside component
This is 3.8.7 + mod_perl
On 3/23/2010 2:57 PM, Jeff Blaine wrote:
This has me really scratching my head. If it makes any
difference, this host (rtdev1) serves two separate RT
instances, each on different ports. The other is working
fine
rtdev1 RT: [Mason] Cannot resolve file to component:
And...
the following in RT_SiteConfig.pm does not help (a
solution that worked for someone in 2009):
Set($MasonComponentRoot, /apps/rt_rtsrv1_dev/share/html);
Set($MasonLocalComponentRoot, /apps/rt_rtsrv1_dev/local);
Set($MasonDataDir, /apps/rt_rtsrv1_dev/var/mason_data);
Set($MasonSessionDir,
Adding some 'warn' statements to Mason/Resolver/File.pm
in apache_request_to_comp_path() shows that my
virtual host is using my other virtual host's
component paths.
I installed RT 3.8.7 in /apps/rt. Works fine.
I installed (from pristine tar.gz) another instance
of RT in /apps/rt_rtsrv1_dev.
I have already installed RT 3.8.4 , and it works fine (on a test
server). However, in the process of installing RT 3.8.4 on a new
server (production), RT's UI fails to launch (404 Not Found). I am
getting the following error message in my Apache error_log file (my
Prod server):
[warning]:
