Todd, thank you very much for your reply. This is an upgrade from 4.2.9, but we have a long story with RT (since 2008) and we have always been upgrading without ever doing a clean install. I think some minor corruption may have been adding up through the years.
Anyway, I just finished creating a couple of VMs, cloning the production server. I have been running rt-validator --check --verbose --resolve on the copy and now I am testing to verify that RT is still working as expected. rt-validator reported a lor of errors, but mainly due to missing principals (principals that existed at the time but have been delete since). In the next days, as my time permits, I'll be testing the approvals workflow on the copies and see if the problem is solved or at least if I can get a clearer debug log. Cris On 11/06/2015 03:18, Todd Wade wrote: > Looking at the code, that error is because a RT template didn't load. > ->Load probably returns an error message that should be logged, but > its pretty bad that your RT is crashing there. > > Is this a clean install of 4.2.10? Or did you upgrade from a previous > version? If so, what version? > > In general approvals are known to be working correctly, so its likely > something specific to the contents of your database, its somehow got > in to a bad state. You might want to check your database with > sbin/rt-validator: > > https://bestpractical.com/docs/rt/latest/rt-validator.html >