On 25 Aug 2008, at 7:37 am, Peter Nikolaidis wrote:
> Ruslan Zakirov wrote:
>>
>> Most of RT's table MUST use InnoDB engine to work correctly. I'm not
>> sure what's going on but I have feeling that you've disabled innodb
>> and mysql went wild after that.
>>
> Hi Ruslan,
>
> To my knowledge, we'
Ruslan Zakirov wrote:
>
> Most of RT's table MUST use InnoDB engine to work correctly. I'm not
> sure what's going on but I have feeling that you've disabled innodb
> and mysql went wild after that.
>
Hi Ruslan,
To my knowledge, we've never used InnoDB on this system. We upgraded to
3.6.6 months a
Most of RT's table MUST use InnoDB engine to work correctly. I'm not
sure what's going on but I have feeling that you've disabled innodb
and mysql went wild after that.
On Mon, Aug 25, 2008 at 6:40 AM, Peter Nikolaidis
<[EMAIL PROTECTED]> wrote:
> Additional info:
>
> After a short while, I obser
Additional info:
After a short while, I observed the rt.log file was growing at an
astounding rate, and quickly grew to fill up the entire available space.
Every second or faster, it was filling up with the lines below. Inspired
by the first line, I ran another myisamchck against the Attributes.MY
On Friday afternoon, for no apparent reason, while I was the only user
on my RT 3.8.0 system, after clicking a link, I was presented with the
logon prompt.
Puzzled, I entered my username and password and logged back in.
Everything seemed normal, and the ticket I was trying to edit was there.
I con
