Joshua,
I missed a step in the upgrade process.
I figured this out while looking at another thread dealing with
attachment corruption.
The upgrade process is:
- Upgrade to 3.8.0
- perl etc/upgrade/schema.mysql-4.0-4.1.pl db user passwd > sql.queries
mysql -u root -p rt3 < sql.queries
- Upg
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 <[EMAIL PROTECTED]>
Subject: Re: [rt-users] Upgrade to 3.8.1 Out of Memory Errors
To: rt-users@lists.bestpractica
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
I also ran across this.
I added local mods back into the local tree after trying out 3.8.0. It
worked fine across apache restarts.
When I upgraded to 3.8.1 I got the "Out of memory! Callback called
exit." error every time I tried to load RT in my browser. Figuring that
one of my local mods h
The increase in blob size should be transparent. Smaller blobs can
still be contained in the larger type and they are functionally
equivalent. If this is the problem, this is the only answer unless
you feel like doing heavy RT coding to reduce the size of a session.
This is definitely the easiest w
I upgraded from 3.8.0 to 3.8.1 and added graphviz support in the wee
hours of last night. All seemed fine. I was able to graph ticket
relationships and I worked until about lunch before I encountered a
problem where each webpage is blank. I am definitely connecting to the
web server, but nothing
