RT DB acting up

RT 2.0.8 on Solaris with mySql 3.23.41. We were running just
fine for over 6 months, but something occured in the past month and
now it’s acting very odd.
When we hit “submit” to set tickets to “resolved”, the next
page displayed is a completely different ticket and always that same
ticket regardless of what other ticker we are closing. If we go back
to the queue, the ticket we intended to resolve is still open. If we
use the command line to set the --status=resolved, it is resolved.
Also, if I do a “rt --summary --limit-status=dead” I get
nothing returned, but there are many with this status. If I use
"mysql" directly with ‘select * from tickets where status = “dead”’,
they all are shown.
I have run “myisamchk” and it reports the DB files as clean
after fixing the flags about being left open. Any thoughts on what
may be wrong and who I might recover? There have been no changes to
the entire RT code tree, the only mods are the sessiondata files.


  • Kyle
    Kyle Tucker - Manager of IT Tel: (978) 816-0229
    Incyte Genomics - Proteome Division Fax: (978) 922-3971
    100 Cummings Center, Suite 420B Email - kylet@incyte.com
    Beverly, MA 01915 Web - http://www.incyte.com