Upgrade issue 3.1.0 > 3.2.4

[Kevin P]

Hi,

I've followed the upgrade instructions totally three times and three times the upgrade has failed. Hence this post.

I expected to see a page saying I was upgrading but instead I am presented with a page saying I am installing Revive - maybe this is an improvement that could be made?

I expected the upgrade to ask for my login details but it didn't - It asked me to input my new DB details which I did.  On pressing continue I am presented with the following error message.

"Your database contains an old OpenX configuration table: rv_preferences. If you are trying to upgrade this database, please copy your existing configuration file into the var folder of this install. If you wish to proceed with a fresh installation, please either choose a new Table Prefix or a new Database.
Database Settings"

I can confirm that the domain.tld.conf.php does in fact exist in adserver_new/var and that the appropriate folder / files permissions have been made writeable.

Apache 2.4.23
MySQL 5.5.31
Php 5.5.38

Is this a bug?

[Erik Geurts]

If you see a page that you're about to install even when it's really an attempt to upgrade, it means the upgrade wizard can't connect to your database, therefore can't find the existing tables and thus considers it a new install.

Most often this is a MySQL permissions problem, and not anything in the application itself. Instead of proceeding with the process, it's best to first make sure that the database can be connected to.

[Kevin P]

I have triple checked the db user has full permissions to access the new db '_revive324' and that the user/pass is correct. The same details allow me to access the db via phpmyadmin.  (the same user can connect to the old db and only the db name has changed).

I have also tried wrapping the username and db name in inverted commas like the pw and removing the inverted commas - where the original has just the password in inverted commas

username=username
password="password"
name=db_revive324

I still see the installation screen.

Edit: To test the db-user has perms to reach the db I search Google and found this https://gist.github.com/chales/11359952

I copied the details from the conf file and sure enough the db is reachable from the var folder and everywhere else I tried it

What's next to look at?

thanks

 

Edited September 8, 2016 by Kevin P
added test file for db access check

[andrewatfornax]

Sounds to me more likely that Revive Adserver is not reading your existing configuration file, that you copied into the new Revive Adserver code base.

1. Are the permissions correct?

2. Are you using the same domain name as your original installation to access the upgrade, and which the configuration file is named using?

[Kevin P]

8 hours ago, andrewatfornax said:

Sounds to me more likely that Revive Adserver is not reading your existing configuration file, that you copied into the new Revive Adserver code base.

1. Are the permissions correct?

2. Are you using the same domain name as your original installation to access the upgrade, and which the configuration file is named using?

Hi Andrew.

1) Permissions are correct - I have triple checked.

2) yes it's the same domain.

The only thing that I should correct is that the actual version being run (that I'm trying to upgrade) is 3.0.5 (not 3.1 as I said in the title) - Maybe this has an effect.

I was looking at the previous files I'd downloaded and had put off an upgrade for the same reason.

 

[andrewatfornax]

So I appreciate you may not want to say here, but:

1. What is the URL you are using to initiate the update process?

2. What are the names of all of the *.conf.php files that you have copied from the old installation's /var directory into the new installation's /var directory?

[Kevin P]

Hi Andrew,

Thanks for that.  One little word was all it took.

Following the upgrade instructions I only copied the domain.tld.conf.php file in to the var folder.

Once I copied the default.conf.php file in to new var folder the upgrade worked.

I'll leave it to you smart people to work out if the upgrade documentation needs a tweak to state that the deault conf file needs to be copied over as well or if some testing needs to be added to check for the existence of a default.conf.php during the process.

Based on my experience {if} this error message is displayed:

"Your database contains an old OpenX configuration table: rv_preferences. If you are trying to upgrade this database, please copy your existing configuration file into the var folder of this install.

maybe the simple addition of words to the effect of:

please copy your existing default and domain configuration file(s) into the var folder

will assist others who may find themselves in my predicament.

Many thanks again one and all.

[Erik Geurts]

This is probably not a generic solution. Normally, a config file won't rely on the existence of default. So in your case there must be something special and non-standard.

[Kevin P]

While it may not probably be a generic solution, it did work.

{else} "Your database contains an old OpenX configuration table: rv_preferences. If you are trying to upgrade this database, please copy your existing configuration file into the var folder of this install. If your domain.conf file is in the var folder and the permissions allow writing please copy your default.conf file to var as well.

I'm glad we got to the bottom of this but as is so often the case, help messages that give real help are helpful. And with updates to operating systems, *sql, php* etc every little helps when time is short and people would like to help themselves.

Thanks again all.

[Erik Geurts]

Your suggestion only really applies if your own config file is referring back to the default config file, or the other way around, for some odd reason. Normally, that won't be the case.