We’re administering an RT 3.6.5 with MySQL ver 14.12 Distrib 5.0.51a for a
customer. While other uses of the system is relatively quick and painless,
getting the screen to “resolve” the ticket after clicking the resolve link
can take minutes. Actually resolving the ticket again is a snap.
Is the database stuck? Number of pipelines from RT to MySQL inadequate (or
is there even such a thing?)? What would be appropriate debugging
procedures to take?
~Robin Laurén / eCraft