Incorrect Stale Ticket Alerts

vermontitguy

My osTicket 1.18 has begun sending Stale Ticket Alerts erroneously. They will arrive saying "A ticket, #xxxxxx, is seriously overdue." But the ticket number shown doesn't exist, the the ID of the record in the hyperlink points to a ticket that has a different subject and is already closed. Do I have some sort of corrupt index? Is there are fix?

KevinTheJedi

vermontitguy

Take a look at your Overdue Alert Email Template to see if it includes the right variables. It could be that someone edited the template and messed some things up. If not then definitely sounds like something is going wrong. You can run commands in the database to check, optimize, and repair tables. I believe the command to check all tables at once is mysqlcheck --databases db_name. This is to be ran on the main server CLI outside of the database.

Cheers.

ntozier

Did you upgrade recently?

Do you have another instance that might be creating tickets via cron checking for emails?

vermontitguy

Well, this is embarrassing. A while back I had cloned the server on which osTicket runs to do some experimental work on an unrelated project. It turns out the Stale Ticket Alerts I've been getting have been from the clone server where the database no longer matches the production database.
Thanks for the suggestions.