Problem with RT_SiteConfig changes Showing on Web

System Information:

OS: RHEL 5.9
RT version 4
Apache 2.2.24
Mod_perl 2.0 (statically linked)

DNS is a little weird. The server is located in a domain different from the one where users access the web site. For instance the server’s name is host.domainA but is accessed via the web by host.domainB. The server has a DNS A Record on domainB’s DNS server. The server has an A record and an alias on domainA’s DNS server. My RT_SiteConfig sets the $rtname, $Organization, and $webdomain to the host.domainB name.

ErrorLog /opt/rt4/var/log/apache2.error TransferLog /opt/rt4/var/log/apache2.access LogLevel debug
    AddDefaultCharset UTF-8

    DocumentRoot "/opt/rt4/share/html"
    <Location />
        Order allow,deny
        Allow from all

        SetHandler modperl
        PerlResponseHandler Plack::Handler::Apache2
        PerlSetVar psgi_app /opt/rt4/sbin/rt-server
    </Location>
    <Perl>
        use Plack::Handler::Apache2;
        Plack::Handler::Apache2->preload("/opt/rt4/sbin/rt-server");
    </Perl>

I am new to RT and recently stood up my RT server. I am still in the initial configuration stage. When I make changes to the RT_SiteConfig.pm file I then stop/start httpd. However, the changes never make it to the web until I reboot the server. Additionally, when the server comes back up from the reboot, httpd has started but RT has not. I have to start RT by running the command: “rt-server &”. I thought that RT should stop/start with httpd. Does anyone know if there is something I need to do so that when I stop/start apache the RT config will effect its changes to the web? Also, if anyone can tell me if RT is supposed to start/stop with Apache?

I have tried making changes to the way my VH is configured in by using the IP, the name, and *. My httpd.conf file is configured to use the httpd-vhosts.conf file. Running httpd -t shows that my vhost file is syntactically correct.

I have googled, searched the wiki, and searched through past rt-users inquiries to no avail. The only thing I found was that you need to stop/start httpd rather than just restarting it.

Thanks
Sarah

Yes, sorry I had tried that and it also did not work.

Thanks

Remember to include the list in replies :slight_smile:

Does anyone else have problems with apache not starting/restarting RT so that changes to the RT_SiteConfig.pm file are seen on the Web? I still cannot find a resolution to this.

thanksFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Eyler, Sarah [USA]
Sent: Thursday, June 27, 2013 1:06 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Problem with RT_SiteConfig changes Showing on Web

System Information:

OS: RHEL 5.9
RT version 4
Apache 2.2.24
Mod_perl 2.0 (statically linked)

DNS is a little weird. The server is located in a domain different from the one where users access the web site. For instance the server’s name is host.domainA but is accessed via the web by host.domainB. The server has a DNS A Record on domainB’s DNS server. The server has an A record and an alias on domainA’s DNS server. My RT_SiteConfig sets the $rtname, $Organization, and $webdomain to the host.domainB name.

ErrorLog /opt/rt4/var/log/apache2.error TransferLog /opt/rt4/var/log/apache2.access LogLevel debug
    AddDefaultCharset UTF-8

    DocumentRoot "/opt/rt4/share/html"
    <Location />
        Order allow,deny
        Allow from all

        SetHandler modperl
        PerlResponseHandler Plack::Handler::Apache2
        PerlSetVar psgi_app /opt/rt4/sbin/rt-server
    </Location>
    <Perl>
        use Plack::Handler::Apache2;
        Plack::Handler::Apache2->preload("/opt/rt4/sbin/rt-server");
    </Perl>

I am new to RT and recently stood up my RT server. I am still in the initial configuration stage. When I make changes to the RT_SiteConfig.pm file I then stop/start httpd. However, the changes never make it to the web until I reboot the server. Additionally, when the server comes back up from the reboot, httpd has started but RT has not. I have to start RT by running the command: “rt-server &”. I thought that RT should stop/start with httpd. Does anyone know if there is something I need to do so that when I stop/start apache the RT config will effect its changes to the web? Also, if anyone can tell me if RT is supposed to start/stop with Apache?

I have tried making changes to the way my VH is configured in by using the IP, the name, and *. My httpd.conf file is configured to use the httpd-vhosts.conf file. Running httpd -t shows that my vhost file is syntactically correct.

I have googled, searched the wiki, and searched through past rt-users inquiries to no avail. The only thing I found was that you need to stop/start httpd rather than just restarting it.

Thanks
Sarah

Does anyone else have problems with apache not starting/restarting RT so that changes to the
RT_SiteConfig.pm file are seen on the Web? I still cannot find a resolution to this.

I am new to RT and recently stood up my RT server. I am still in the initial configuration
stage. When I make changes to the RT_SiteConfig.pm file I then stop/start httpd. However,
the changes never make it to the web until I reboot the server. Additionally, when the server
comes back up from the reboot, httpd has started but RT has not. I have to start RT by
running the command: “rt-server &”. I thought that RT should stop/start with httpd. Does

Your config says that mod_perl is running RT, but if you have to run
rt-server manually, then that isn’t true.

If you’re running rt-server then it is connecting to port 80 on the
server and serving content. If that is true, what port do you have
Apache running on?

If apache was actually invoking and serving RT for you, you would not
need to reboot to see config changes.

Running rt-server manually to serve RT is contradictory to trying to
run RT under mod_perl.

I suspect that your DNS shenanigans and VirtualHost directives aren’t
working together as you expect.

-kevin

Kevin,

Thank you! Your question " what port do you have Apache running on?" made me realize that my httpd.conf was configured to listen on port 80 while my RT was listening on port 8080 as was my Vhost. I changed my httpd.conf to listen on port 8080 and now RT stops/starts with Apache.

Problem resolved, thank you for your help.-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, July 03, 2013 12:03 PM
To: rt-users@lists.bestpractical.com
Subject: [External] Re: [rt-users] Problem with RT_SiteConfig changes Showing on Web

On Wed, Jul 03, 2013 at 01:46:00PM +0000, Eyler, Sarah [USA] wrote:

Does anyone else have problems with apache not starting/restarting RT so that changes to the
RT_SiteConfig.pm file are seen on the Web? I still cannot find a resolution to this.

I am new to RT and recently stood up my RT server. I am still in the initial configuration
stage. When I make changes to the RT_SiteConfig.pm file I then stop/start httpd. However,
the changes never make it to the web until I reboot the server. Additionally, when the server
comes back up from the reboot, httpd has started but RT has not. I have to start RT by
running the command: “rt-server &”. I thought that RT should
stop/start with httpd. Does

Your config says that mod_perl is running RT, but if you have to run rt-server manually, then that isn’t true.

If you’re running rt-server then it is connecting to port 80 on the server and serving content. If that is true, what port do you have Apache running on?

If apache was actually invoking and serving RT for you, you would not need to reboot to see config changes.

Running rt-server manually to serve RT is contradictory to trying to run RT under mod_perl.

I suspect that your DNS shenanigans and VirtualHost directives aren’t working together as you expect.

-kevin