Hey Ken- Yep, I get that. I don't believe you can disable the wait_timeout entirely - by default, it's set to 8 hours, which is what I currently have. RT works great - for 8 hours. Just to be sane, I replaced my.cnf with the default my.cnf that gets built with a vanilla install of MySQL. Same issue.
Clearly though, I have something going on that is not-normal because if this were a real bug, lots of people would be reporting it and it's never been an issue for me before. I'm going to start over with a clean build and try again. - Jay On Mon, Nov 25, 2013 at 5:53 AM, k...@rice.edu <k...@rice.edu> wrote: > On Sat, Nov 23, 2013 at 08:35:06AM -0800, Jay Christopherson wrote: > > Interestingly, adjusting the wait_timeout to the default (8 hours) worked > > great - for 8 hours. After that 8 hours, RT once again lost all > > connectivity to the database. Running a "show processlist" on MySQL > showed > > that RT had no connections to the DB, even though RT was still running. > A > > restart fixed it - for now. > > > > I am not sure how RT does connection handling, but it seems like it > should > > attempt to reconnect? > > > > Hi Jay, > > Again, a properly managed system does not require and certainly does not > expect > to have a connection ripped out from under it. Turn off your timeout and > you > will be fine. RT will connect just fine, as you have seen. It should not > need > to "reconnect" to a properly configured DB once it has a valid connection. > > Regards, > Ken >