[rt-users] Upgrade to 3.8.1 Out of Memory Errors

[Joshua Hunter]

Paul,

For my part I can tell you that it was in fact an upgrade and not a
clean install.

I'm not sure about what kind of system resources I was using prior as
I'd never had any qualms with the performance.  I am the only user of
the web interface and only receive 5-10 tickets or so per day.

Clearing the sessions table immediately restores my access ... for a
little while.

Joshua Hunter

Message: 5
Date: Thu, 21 Aug 2008 12:49:42 -0700 (PDT)
From: Paul Hirose <pthirose at ucdavis.edu>
Subject: Re: [rt-users] Upgrade to 3.8.1 Out of Memory Errors
To: rt-users at lists.bestpractical.com
Message-ID: <Pine.GSO.4.58.0808211241560.17404 at vici.ucdavis.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Earlier in this thread, it was mentioned in passing that a clean install
of 3.8.1 is fine, implying this problem only affects upgrades.  Is this
so?  If I can afford to do a clean install rather than an upgrade from
380, do I then not have to make this change to LONGBLOB type?  Does 381
already use LONGBLOB or is there something else occuring (or not
occuring) during the update process?

Is LONGBLOB'ing the a_session field going to be the recommended method,
or maybe even become part of the official update process when moving say
to 3.8.2?

I've not yet noticed this problem on our system, but ours is very very
small.  We have less than a dozen people using the web interface.  All
our ticket creators only know how to email our helpdesk@ address and we
don't tell them about the actual website, keeping the website itself
strictly for internal support staff.  And I'm guessing this issue is
related more to the number of sessions on the website, than the total
number of tickets in the RT database.

For those of you who have run into this issue, any idea how close you
used to be to maximum memory usage before updating to 381?  Was it just
"I was close at 380 and 381 just tipped me over" scenario?  Or was your
system only using up say 50% memory and going to 381 more than doubled
your memory footprint?

Thank you,
PH