Apache2 and rt3 session issue

I’ve seen quite a bit of discussion about this, but very little mention of
folks using Apache 2 with RT3. I’m getting the “RT Couldn’t write to session
directory…” error that has been a recurring topic on the list for awhile
now.

To remedy this problem, all I need to do is restart the web server. I’ve
tried setting the permissions on the directory to 777 and I’ve looked to see
if there were non-world writable perl modules. The really odd part is that
this only happens after RT has been idle for awhile and then someone tries to
log back into the system. It’s almost as if there’s a timer in RT that says
it can only be available for X minutes before requiring a restart of Apache.

Details:

Apache 2.0.47 with ssl
Perl 5.8.0
FastCGI 2.4.0
Mason 1.2.1

I haven’t downgraded mason (yet) but I did notice some talk of this on the
list.

Suggestions?

Almost forgot. There is mention of DBD::mysql::st execut failed, just after
the session error.

Thanks,
–Robert

Almost forgot. There is mention of DBD::mysql::st execut failed, just after
the session error.

I think that’s the most critical part of all of this. What was the
failure?

Thanks,
–Robert


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Jesse Vincent jesse@bestpractical.com 07/24/03 10:26AM >>>

Almost forgot. There is mention of DBD::mysql::st execut failed, just after
the session error.

I think that’s the most critical part of all of this. What was the
failure?

DBD::mysql::st execute failed: MySQL server has gone away at /perl/path/MySQL.pm line 54.