I'm guessing the problem here is that MySQL is trying to write the session data to this directory. However, with the database now on another server it clearly doesn't have access to it. Is this correct?
Keep up with me and what I'm up to: http://theillien.blogspot.com Mathew Snyder wrote: > I'm moving my devel database to a second server and separating it from the > server RT actually runs on. However, after doing so and updating the > RT_SiteConfig.pm I get the following: > > error: RT couldn't store your session. > This may mean that that the directory '/usr/local/rt3/var/session_data' isn't > writable or a database table is missing or corrupt. > > context: > ... > 86: }; > 87: undef $cookies{$cookiename}; > 88: } > 89: else { > 90: die loc("RT couldn't store your session.") . "\n" > 91: . loc( > 92: "This may mean that that the directory '[_1]' isn't writable or a > database > table is missing or corrupt.", > 93: $RT::MasonSessionDir > 94: ) > ... > code stack: /usr/local/rt3/local/html/Elements/SetupSessionCookie:90 > /usr/local/rt3/share/html/autohandler:120 > > I've verified the permissions and ownership for the directory. What else > might > I need to look at? > _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
