Okay, that makes more sense. Now I'm back to my FCGI problem: the process
spawns, but netstat shows nothing on the address:port I assign when using the
command. I can't kill or restart it because it doesn't seem to exist, though I
get a success message and can't spawn a new process on that port
We started using RT as our ticket system around version 3.8 and are currently
running 4.4.1. We have approximately 8600 tickets in the system. We have been
experiencing issues with our current install (Scrips not firing properly,
extensions no longer needed/compatible, etc.). If I use rt-seriali
On 8/30/16 9:22 AM, Alex Hall wrote:
So doing
/etc/init.d/nginx restart
is enough to reload RT's configuration as well? Great, that makes things
easier. It seems odd, since I thought Nginx (or whatever your server)
was separate from RT and needed the middleware of a FastCGI or similar
process t
So doing
/etc/init.d/nginx restart
is enough to reload RT's configuration as well? Great, that makes things
easier. It seems odd, since I thought Nginx (or whatever your server) was
separate from RT and needed the middleware of a FastCGI or similar process to
let the two talk. I'm glad I was wro
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,
I figured it out, actually they were tickets that were from no longer
existing queues. I bulk moved them to an existing queue and they no longer
showed up.
On Aug 29, 2016 5:59 PM, "Chris McClement" wrote:
> Did you apply the permissions globally or just to the queue? My guess is
> the former,
