[rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-16 Thread Barron, Josh
Ok I've been fighting this forever and its really starting to get to me. I'm trying to upgrade RT and I'm at the step where I'm supposed to upgrade the database to a certain point before applying a schema. The command to run is: /opt/rt3/sbin/rt-setup-database --prompt-for-dba-password --

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-16 Thread Barron, Josh
mailto:t...@bitstatement.net] Sent: Monday, November 16, 2009 5:25 PM To: Barron, Josh Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 > Connect Failed Access denied for user 'rt_user'@'localhost' (using > password:

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-16 Thread Tom Lahti
> Connect Failed Access denied for user 'rt_user'@'localhost' (using > password: YES) > So basically, it appears that my password is incorrect, HOWEVER, I can > connect to mysql using the exact user and password. Its almost like the > perl script is NOT taking the prompts. Connecting at loc

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-16 Thread Tom Lahti
Try> Yes I tried connecting to mysql directly from localhost and that worked: > > [jbar...@help01 ~]$ mysql -u rt_u...@localhost -p > Enter password: > ERROR 1045 (28000): Access denied for user > 'rt_u...@localhos'@'localhost' (using password: YES) > [jbar...@help01 ~]$ mysql -u rt_user -p

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-17 Thread Barron, Josh
Lahti [mailto:t...@bitstatement.net] Sent: Monday, November 16, 2009 5:38 PM To: Barron, Josh Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 Try> Yes I tried connecting to mysql directly from localhost and that worked: > > [jbar...@help01 ~]$

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6

2009-11-17 Thread Tom Lahti
> Hi Tom, > > There is only one my.cnf and it doesn't contain those sections with that > line. From what I can determine mysql is set to listen to any address. > When I forced a localhost connection, I was able to connect as both root > and rt_user. > > -Josh Huh. So you did: > mysql -h local

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE:mason_data directory

2009-11-17 Thread Barron, Josh
: rt-users@lists.bestpractical.com Subject: RE: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE:mason_data directory > -Original Message- > From: Barron, Josh > > That file does not exist in the new RT directory, nor is any file by > that name in use anywhere from

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Barron, Josh
s@lists.bestpractical.com Subject: Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 Hi Tom, There is only one my.cnf and it doesn't contain those sections with that line. From what I can determine mysql is set to listen to any address. When I forced a localhost connection, I was ab

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Tom Lahti
> [Tue Nov 17 16:24:02 2009] [error] [client 216.222.31.30] Could not > create '/opt/rt3/var/mason_data/obj/.__obj_create_marker': Permission > denied\nStack:\n You need to look specifically at the permissions on /opt/rt3/var/mason_data/obj and verify that the user the web server runs as can wri

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Barron, Josh
2:47 PM To: Barron, Josh Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory > [Tue Nov 17 16:24:02 2009] [error] [client 216.222.31.30] Could not > create '/opt/rt3/var/mason_data/obj/.__obj_create_marker&

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Tom Lahti
>> [Tue Nov 17 16:24:02 2009] [error] [client 216.222.31.30] Could not >> create '/opt/rt3/var/mason_data/obj/.__obj_create_marker': Permission Does the *file* .__obj_create_marker already exist in that location, with some un-overwritable permissions perhaps? Or perhaps its in use? lsof | grep

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Barron, Josh
users@lists.bestpractical.com Subject: Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory >> [Tue Nov 17 16:24:02 2009] [error] [client 216.222.31.30] Could not >> create '/opt/rt3/var/mason_data/obj/.__obj_create_marker': Permission Does the

Re: [rt-users] RT Upgrade failing from 3.6.6 to 3.8.6 UPDATE: mason_data directory

2009-11-17 Thread Stuart Browne
> -Original Message- > From: Barron, Josh > > That file does not exist in the new RT directory, nor is any file by > that name in use anywhere from what I can see. > > I'm really baffled by this. SELinux isn't turned on by any chance is it? getenforce ausearch -m avc -ts