[rt-users] Problem after system crash

[Lois Bennett]

Solved.  Running mysqlcheck -r rt3  cleared the inconsistencies in the 
database and all was fixed.

Peace,
Lois

Lois Bennett wrote:
> Hi,
> 
> We had a problem with our UPS which resulted in almost all our servers 
> going down.  I now have a problem with RT. It is working fine as far as 
> comments and replies to existing tickets.
> 
> It won't create new tickets.  I believe it it because it was in the 
> middle of creating one when the system crashed.
> 
> I have these error messages:
> 
> [Tue Aug 28 21:07:34 2007] [crit]: Couldn't create a ticket: Internal 
> Error: Couldn't execute the query 'INSERT INTO Tickets (Status, Queue, 
> Started, Type, InitialPriority, Starts, LastUpdated, Subject, 
> FinalPriority, Creator, Owner, LastUpdatedBy, Resolved, Created, 
> Priority, Due) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 
> ?)'Duplicate entry '8276' for key 1 (/opt/rt3/lib/RT/Ticket_Overlay.pm:591)
> 
> [Tue Aug 28 21:07:34 2007] [error]: WebRT: Ticket could not be created 
> due to an internal error () (/opt/rt3/share/html/Elements/Error:76)
> 
> In mysql
> mysql> select * from Tickets where id = 8276;
> Empty set (0.00 sec)
> mysql> select * from Transactions where ObjectId = 8276;
> +--------+----------+-----------+-------------+-------+----------+----------+----------------------------------------------------------------+---------+---------------------+------------+---------------+--------------+--------------+ 
> 
> | id     | ObjectId | TimeTaken | Type        | Field | OldValue | 
> NewValue | Data   | Creator | Created             | ObjectType | 
> ReferenceType | OldReference | NewReference |
> +--------+----------+-----------+-------------+-------+----------+----------+----------------------------------------------------------------+---------+---------------------+------------+---------------+--------------+--------------+ 
> 
> | 142759 |     8276 |         0 | Create      | NULL  | NULL     | NULL 
>     | NULL                                                           |   
> 20791 | 2007-08-28 18:20:47 | RT::Ticket | NULL          | NULL 
> |         NULL |
> | 142760 |     8276 |         0 | EmailRecord | NULL  | NULL     | NULL 
>     | <rt-3.6.0-17672-1188325247-1940.8276-3-0 at channing.harvard.edu> | 
>       1 | 2007-08-28 18:20:48 | RT::Ticket | NULL          | NULL 
> |         NULL |
> | 142761 |     8276 |         0 | EmailRecord | NULL  | NULL     | NULL 
>     | <rt-3.6.0-17672-1188325247-679.8276-4-0 at channing.harvard.edu>  | 
>       1 | 2007-08-28 18:20:54 | RT::Ticket | NULL          | NULL 
> |         NULL |
> +--------+----------+-----------+-------------+-------+----------+----------+----------------------------------------------------------------+---------+---------------------+------------+---------------+--------------+--------------+ 
> 
> 3 rows in set (0.00 sec)
> 
> So it was creating ticket 8276 when it crashed but how can I tell it to 
> clear out 8276 and move on?
> 
> I suspect this is in the docs somewhere and I am looking but I thought I 
> would ask too since it might take me a while to search and read.
> 
> Thanks,
> Lois
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy 
> a copy at http://rtbook.bestpractical.com