Sorry, List: I’ve read the various docs and worked on this a few days, but…
I’ve installed rt4 next to my rt3, and specified use of the rt3 database, with the same username and password. However, going to rt.domain.com now shows me the “Hey congrats, you’ve a new RT install! Let’s set up the database!”
On the commandline, the rt_user can connect to mysql with the password I’ve specified. I’ve checked the config files and the correct username and mysql password are there. I’ve followed, I thought, the updated apache instructions (and I do seem to be hitting /opt/rt4/ and not /opt/rt3/). I’m stumped. Is this a symptom of a common mistake, or I have done something strange?
Thanks…
Rob Munsch
IT Administrator
PhillyCarShare
215-495-1040 x131
www.phillycarshare.org
Our Vision: A Philadelphia in which non-profit car sharing exceeds the convenience, flexibility, and affordability of car ownership.
You know there’s a bunch of schema changes between 4 and 3, right? 
If you pointed RT4 software at the RT3 database, the upgrade process
changes the schema.On Wed, 2011-05-11 at 10:29 -0400, Rob Munsch wrote:
Sorry, List: I’ve read the various docs and worked on this a few days,
but…
I’ve installed rt4 next to my rt3, and specified use of the rt3
database, with the same username and password. However, going to
rt.domain.com now shows me the “Hey congrats, you’ve a new RT install!
Let’s set up the database!”
On the commandline, the rt_user can connect to mysql with the password
I’ve specified. I’ve checked the config files and the correct
username and mysql password are there. I’ve followed, I thought, the
updated apache instructions (and I do seem to be hitting /opt/rt4/ and
not /opt/rt3/). I’m stumped. Is this a symptom of a common mistake,
or I have done something strange?
Thanks…
Rob Munsch
IT Administrator
PhillyCarShare
215-495-1040 x131
www.phillycarshare.org
Our Vision: A Philadelphia in which non-profit car sharing exceeds the
convenience, flexibility, and affordability of car ownership.
Joshua Knarr
knarrj@gsicommerce.com
Desk: 610-491-7110
Mobi: 484-636-7371
The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.
You know there’s a bunch of schema changes between 4 and 3, right? 
If you pointed RT4 software at the RT3 database, the upgrade process changes the schema.
Well, yes; part of the process is running the upgrade scripts on the database, which was done, and seemed to complete successfully. Essentially it was a new install of RT4 into its own directory, as per instructions, giving it the rt3 db name, user, and password; the upgrade script was run against the RT3 database; then the Apache conf of the site was altered to make the RT hostname point to the rt4 docroot instead of rt3. This seems to match the docs, yet going to the site gets a 4.0.0 web page with “Hi! No database! Tee hee.”
Oh, I misread that as “I’m trying to run these in parallel”.
What version are you upgrading from?On Wed, 2011-05-11 at 11:57 -0400, Rob Munsch wrote:
You know there's a bunch of schema changes between 4 and 3,
right? :)
If you pointed RT4 software at the RT3 database, the upgrade
process changes the schema.
Well, yes; part of the process is running the upgrade scripts on the
database, which was done, and seemed to complete
successfully. Essentially it was a new install of RT4 into its own
directory, as per instructions, giving it the rt3 db name, user, and
password; the upgrade script was run against the RT3 database; then
the Apache conf of the site was altered to make the RT hostname point
to the rt4 docroot instead of rt3. This seems to match the docs, yet
going to the site gets a 4.0.0 web page with “Hi! No database! Tee
hee.”
Joshua Knarr
knarrj@gsicommerce.com
Desk: 610-491-7110
Mobi: 484-636-7371
The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.
Oh, I misread that as “I’m trying to run these in parallel”.
What version are you upgrading from?
Oh, gotcha. It was 3.8.8. I dumped the old DB (and I guess if all else fails can restore that and go back using the 3.8 install), ran the upgrade script, and watched it tell me about 3.8.9, 3.9, etc, as they were applied.On Wed, 2011-05-11 at 11:57 -0400, Rob Munsch wrote:
You know there's a bunch of schema changes between 4 and 3, right? :)
If you pointed RT4 software at the RT3 database, the upgrade process changes the schema.
Well, yes; part of the process is running the upgrade scripts on the database, which was done, and seemed to complete successfully. Essentially it was a new install of RT4 into its own directory, as per instructions, giving it the rt3 db name, user, and password; the upgrade script was run against the RT3 database; then the Apache conf of the site was altered to make the RT hostname point to the rt4 docroot instead of rt3. This seems to match the docs, yet going to the site gets a 4.0.0 web page with "Hi! No database! Tee hee."
Did any of these throw errors or warnings?On Wed, 2011-05-11 at 12:22 -0400, Rob Munsch wrote:
______________________________________________________________
From: Joshua Knarr [mailto:knarrj@gsicommerce.com]
Oh, I misread that as "I'm trying to run these in parallel".
What version are you upgrading from?
Oh, gotcha. It was 3.8.8. I dumped the old DB (and I guess if all
else fails can restore that and go back using the 3.8 install), ran
the upgrade script, and watched it tell me about 3.8.9, 3.9, etc, as
they were applied.
On Wed, 2011-05-11 at 11:57 -0400, Rob Munsch wrote:
>
>
>
>
> You know there's a bunch of schema changes between 4
> and 3, right? :)
>
> If you pointed RT4 software at the RT3 database, the
> upgrade process changes the schema.
>
>
> Well, yes; part of the process is running the upgrade
> scripts on the database, which was done, and seemed to
> complete successfully. Essentially it was a new install of
> RT4 into its own directory, as per instructions, giving it
> the rt3 db name, user, and password; the upgrade script was
> run against the RT3 database; then the Apache conf of the
> site was altered to make the RT hostname point to the rt4
> docroot instead of rt3. This seems to match the docs, yet
> going to the site gets a 4.0.0 web page with "Hi! No
> database! Tee hee."
Joshua Knarr
knarrj@gsicommerce.com
Desk: 610-491-7110
Mobi: 484-636-7371
The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.
Not that I saw.From: Joshua Knarr [mailto:knarrj@gsicommerce.com]
Sent: Wednesday, May 11, 2011 12:29 PM
To: Rob Munsch
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] Can’t connect to old DB
Did any of these throw errors or warnings?
Hi,
Logs should contain more precise error messages. Also, it may be
difference in Database* options. However, you say that schema upgrade
went well, so it sure connects to some DB.
Use mysql client, check list of DBs, check tables, for example rt4
comes with articles table that was not in RT3.8, check rights in
mysql.On Wed, May 11, 2011 at 6:29 PM, Rob Munsch Munsch@phillycarshare.org wrote:
Sorry, List: I’ve read the various docs and worked on this a few days, but…
I’ve installed rt4 next to my rt3, and specified use of the rt3 database,
with the same username and password. However, going to rt.domain.com now
shows me the “Hey congrats, you’ve a new RT install! Let’s set up the
database!”
On the commandline, the rt_user can connect to mysql with the password I’ve
specified. I’ve checked the config files and the correct username and mysql
password are there. I’ve followed, I thought, the updated apache
instructions (and I do seem to be hitting /opt/rt4/ and not /opt/rt3/). I’m
stumped. Is this a symptom of a common mistake, or I have done something
strange?
Thanks…
Rob Munsch
IT Administrator
PhillyCarShare
215-495-1040 x131
www.phillycarshare.org
Our Vision: A Philadelphia in which non-profit car sharing exceeds the
convenience, flexibility, and affordability of car ownership.
Best regards, Ruslan.
Thanks, Ruslan: check all that, I couldn’t find any errors with rt or the database, so I looked looked at my apache2 config again. Replaced it with the stock example in the docs, which I perhaps should have done before getting hung up on the idea it was a DB communication issue. It’s working now (and also seems a great deal faster than 3.8!).