I upgraded mysql to 3.23.54 a couple of weeks ago, then session data
seems broken. Several other modules were upgraded together, so I’m
not sure what cause this problem.
After logging in RT, it’s ok to see, modify, and create tickets. But
if I click a queue link to see what tickets are in it, the error
message ‘Out of memory’ will appear in Apache’s log. After this, RT
is unable to serve any further requests.
I traced the code, and seems this is not RT’s fault. The only way to
resolve is use files to store session data. In
share/html/Elements/SetupSessionCookie, change the line:
my $session_class = $backends{$RT::DatabaseType} ||
‘Apache::Session::File’;
I upgraded mysql to 3.23.54 a couple of weeks ago, then session data
seems broken. Several other modules were upgraded together, so I’m
not sure what cause this problem.
After logging in RT, it’s ok to see, modify, and create tickets. But
if I click a queue link to see what tickets are in it, the error
message ‘Out of memory’ will appear in Apache’s log. After this, RT
is unable to serve any further requests.
I traced the code, and seems this is not RT’s fault. The only way to
resolve is use files to store session data. In
share/html/Elements/SetupSessionCookie, change the line:
my $session_class = $backends{$RT::DatabaseType} ||
‘Apache::Session::File’;
into
my $session_class = ‘Apache::Session::File’;
So far, I don’t encounter any problem.
I upgraded my MySQL to 3.23.54 (from 3.23.51) three days ago. It did onstall
some modules also because I installed from the ports. But I have not seen
any misbehaviour so far with rt-2.0.15.
cheers
- wash
Odhiambo Washington, wash@wananchi.com . WANANCHI ONLINE LTD (Nairobi, KE) | http://ns2.wananchi.com/~wash/ . 1ere Etage, Loita Hse, Loita St., |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
“Oh My God! They killed init! You Bastards!”
–from a /. post