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: [email protected] [mailto:[email protected]] On Behalf Of Kevin Falcone Sent: Wednesday, July 03, 2013 12:03 PM To: [email protected] 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
