I recently upgraded an RT installation from 3.1.10 to 3.2.2, and the
web interface seems to be incredibly touchy now. Most page loads
require me to hit reload a couple of times before I actually get
content; I have to hit the “Login” button at least two or three
times before I actually get logged in, and occasionally when working
with tickets, I get some crazy Perl error which claims to be
about /opt/rt3/var/session_data not being writeable (which was changed
to 0777 just to be sure a little while ago when I first noticed these
problems), but whose traceback seems to indicate some kind of weird
When I get this error, the RT vhost becomes completely unresponsive,
and I have to bounce Apache to have anything work on it. I’ve attached
the error to this message.
The RT installation is getting its data from a MySQL 4 database, and
when I did the upgrade, it actually moved to a different box as well,
so there’s no lingering RT code from a previous release to get in
the way. The old box that 3.1.10 used to be on was a single-processor
box, and the new one is SMP (and the CPUs are a little bit slower than
the single-processor it had been on before), and since all of these
errors that I’m getting aren’t really repeatable every time, I’m
inclined to think that perhaps it’s a problem with the box being SMP.
The box RT’s been moved to serves up a bunch of other content too,
all of which is working fine, so I don’t think it’s a problem with
the actual box hardware. Also, the mailgate stuff seems to work fine;
I haven’t experienced any problems with that yet.
Thanks for any ideas!
rt-error.txt (4.69 KB)