I ran GRANT ALL ON rt_database.* to 'rt_user'@'rt_server' IDENTIFIED BY 'rt_password' when I first migrated it. It didn't work. I then actually went through the process of installing RT on the database server in order to utilize `make initialize-database`. This didn't work either.
Keep up with me and what I'm up to: http://theillien.blogspot.com Roy El-Hames wrote: > Matthew; > It sounds to me you forgot to : > > GRANT SELECT,INSERT,CREATE,INDEX,UPDATE,DELETE ON ${RT::DatabaseName}.* > TO ${RT::DatabaseUser}\@'${RT::DatabaseRTHost}' IDENTIFIED BY > '${RT::DatabasePassword}' > ;"); > > Roy > > > Mathew Snyder wrote: >> I figured out that I need to use the session file instead of the >> database. I >> linked the error together with what I found in RT_SiteConfig.pm. >> >> Now I can get the login screen but can't login. I'm guessing that the >> remote >> database isn't being located/connected to. >> >> Keep up with me and what I'm up to: http://theillien.blogspot.com >> >> >> Mathew Snyder wrote: >> >>> 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 >>> >>> >>> >> _______________________________________________ >> 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 >> >> > > _______________________________________________ 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
