Thanks for the reminder to check the built-in server first; it's still trying to use SQLite. My config file says to use MySQL, but RT doesn't seem to want to. The error message I get when starting the server says to configure my database connection by visiting the "URL below", but never actually gives me a URL. I've restarted the RT service, but that didn't work.
I seem to keep going in circles with RT. I can't get it to run, likely because of it not taking my configuration changes. To apply those changes, I have to restart whatever server it's running on, but to do that, a server has to be running. /var/log/request-tracker4 has no files in it at all, so I can't look there to see if there's a missing piece. I don't know why I'm having so much trouble with what should be a relatively straightforward process; I'm either missing something very obvious, or the Debian package for RT isn't working correctly. Installing with the latest source, though, was a nightmare. Anyway, any thoughts on where to go from here? My configuration file seems to be okay, but RT doesn't want to pick it up. Maybe that's the root of my problem? On Thu, Sep 1, 2016 at 1:36 PM, Kenneth Marshall <k...@rice.edu> wrote: > On Thu, Sep 01, 2016 at 01:23:23PM -0400, Alex Hall wrote: > > Hey all, > > I think it's pretty clear by now that no one on this list uses Nginx (my > > server of choice). So, I guess I'll try to use Apache instead, using the > > official setup page: > > https://docs.bestpractical.com/rt/4.4.1/web_deployment.html > > > > I'm using 4.2.8, but it's the same thing for hosting, I hope. Anyway, the > > Nginx section of the above page looked very simple--a configuration, a > > restart of Nginx, a spawn-fcgi, and you're done. Worse are all the > warnings > > in each subsection of the Apache section. I'm not good enough with Linux > to > > fully grasp what it is they're warning me about, but when Apache, then > each > > subsection of Apache, has caveats and notes, while Nginx has none, I > > thought I'd take the safer road. If Nginx isn't an option, though, which > > method for Apache should I use to host the FCGI that RT needs in order to > > work? Is there a different RT setup/serving page that explains things > > differently? Thanks in advance. > > > > -- > > Alex Hall > > Automatic Distributors, IT department > > ah...@autodist.com > > > Hi Alex, > > We use nginx+spawn-fcgi with RT here and it works very well. I think you > will need to test each piece of your setup before moving to the next. i.e. > Does the standalone server run? Then try it with fcgi. You should also > check your RT logs, because if the backend exits, then their will be > nothing > to talk to. > > Regards, > Ken > -- Alex Hall Automatic Distributors, IT department ah...@autodist.com
--------- RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training * Boston - October 24-26 * Los Angeles - Q1 2017
