Restarting the server should reload the configuration. To confirm what
configuration RT has loaded, you can check the System Configuration page
at Admin > Tools > System Configuration. There you can check
DatabaseType, DatabaseHost, and other Database configuration. If it's
not what you expect, it could be RT is loading some configuration from
some other location. You can see the config files in the "Loaded config
files" section on that same page.
You set these in RT_Config.pm by selecting different options when
running the initial configure script. After that, you can override in
RT_SiteConfig.pm.
On 8/29/16 2:27 PM, Alex Hall wrote:
Hello list,
Until I can find out why FCGI processes don't work, I'm trying to run RT
on its own server with:
sudo /usr/share/request-tracker4/libexec/rt-server --port 8485
but I get an error about SQLite3 not working. The thing is, I have it
set to MySQL, not SQLite, so I don't know why it's not using MySQL. I
made a change to /etc/request-tracker4/RT_SiteConfig.pm, and the same to
RT_SiteConfig.d/51-DBConfig, but it didn't help. I tried
sudo /etc/init.d/request-tracker4 restart
to get the change to register, but had no luck. What do I have to do to
get RT to see configuration changes? This seems like a simple thing, but
I can't find it online, and the restart doesn't seem to have helped. If
there's something obvious I've missed in my DB setup that would cause it
to use the wrong backend, I'd love to know that as well. RT4.2.8 on
Debian 8. Thanks.
--
Alex Hall
Automatic Distributors, IT department
[email protected] <mailto:[email protected]>
---------
RT 4.4 and RTIR training sessions, and a new workshop day!
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017
---------
RT 4.4 and RTIR training sessions, and a new workshop day!
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017
