Every now and then RT 2.0.15 goes out to lunch. The main symptom is
that one of the mysqld threads is 100% cpu bound and never frees
itself, so any other attempts to talk to the database seem to get
locked out. Killing off that process tends to fix things, but
mysqladmin processlist never shows anything of value/use.
However, today we did catch two interesting log items:
[Wed Feb 19 14:28:34 2003] [error]: RT::Ticket=HASH(0x1947dd90)
couldn’t set status to resolved.RT’s Database may be inconsistent.
[Wed Feb 19 15:19:09 2003] [err]: RT::Ticket=HASH(0x893bdf0) ->Create
couldn’t set EffectiveId: No value sent to _Set!
Are these known? Symptomatic, or unrelated?
The timings do not correspond with the outtage, however…
p.s. For what it’s worth, all the mysqladmin processlist ever shows is:
| 1 | rt_user | localhost | rt2 | Sleep | 0 | |
| 19 | root | localhost | | Query | 0 | | show