Jump to content
gabrielt

Issue upgrading from 4.0.2 to 4.1.0

Recommended Posts

Hi there,

I am getting this error while trying to upgrade:

Errors were found when detecting previous installations of Revive Adserver
We have detected integrity issues with your database. This means that the layout of your database differs from what we expect it to be. This could be due to customization of your database.

The install.log shows that there are 107 errors. See below.

I haven't customized anything, and I don't know how to fix these issues.

Please advise.

Gabriel.

----

=========================================================================
Attempting to detect an existing Openads (aka. phpAdsNew) installation...
PAN not detected
Attempting to detect an existing Openads (aka. Max Media Manager 0.1) installation...
MMM v0.1 not detected
Attempting to detect an existing Openads (aka. Max Media Manager 0.3) installation...
MMM v0.3 not detected
Attempting to detect an existing Revive Adserver installation...
schema file found: [redacted]/etc/changes/schema_tables_core_621.xml
schema definition from cache TRUE
successfully parsed the schema
schema name: openads
schema version: 621
schema status: final
running integrity check
comparing database [redacted] with schema [redacted]/etc/changes/schema_tables_core_621.xml
column definition does not match: account_preference_assoc.account_id
column definition does not match: account_user_assoc.account_id
column definition does not match: account_user_permission_assoc.account_id
column definition does not match: ad_category_assoc.category_id
column definition does not match: affiliates.updated
column definition does not match: affiliates_extra.affiliateid
column definition does not match: agency.updated
column definition does not match: audit.actionid
column definition does not match: banners.acl_plugins
column definition does not match: campaigns.updated
[... snip ...]
checking field: phpads_zones updated
found field updated
#! database integrity check detected problems with the database
#! 107 fields to change
 

Edited by Matteo Beccati
Reduced post length for better readability

Share this post


Link to post
Share on other sites

I'm having the exact same issue.

I updated to 4.0.2 2 months ago, with no errors.

Trying to update to 4.3 I get the same exact error messages regarding DB integrity. 

 

=========================================================================

Attempting to detect an existing Openads (aka. phpAdsNew) installation...

PAN not detected

Attempting to detect an existing Openads (aka. Max Media Manager 0.1) installation...

MMM v0.1 not detected

Attempting to detect an existing Openads (aka. Max Media Manager 0.3) installation...

MMM v0.3 not detected

Attempting to detect an existing Revive Adserver installation...

schema file found: -----------/etc/changes/schema_tables_core_621.xml

schema definition from cache TRUE

successfully parsed the schema

schema name: openads

schema version: 621

schema status: final

running integrity check

comparing database ---------- with schema ----------/etc/changes/schema_tables_core_621.xml

column definition does not match: account_preference_assoc.account_id

[... similar info, see previous posts ...]

 

Edited by Matteo Beccati
Removed overlong details

Share this post


Link to post
Share on other sites

I noticed in the log that it does not acknowledge that it found a previous installation of Revive Ad server. Could this be part of the issue?

 

From the install.log file for 4.3 (failed attempt):

 

Attempting to detect an existing Revive Adserver installation...

schema file found: -----------/etc/changes/schema_tables_core_621.xml

 

From the install.log file for 4.0.2 (successful)

 

Attempting to detect an existing Revive Adserver installation...

Revive Adserver 4.0.1 detected

This version can be upgraded

Database settings and permissions are OK

Share this post


Link to post
Share on other sites

@gabrielt Oh yes, I saw the nice phpads_ prefix. Fond memories! Anyway, I see two possibilities at the moment:

  1. Hold off on the upgrade, until we figure out where the issue comes from and see if we can fix it.
  2. Remove the defaults from all the listed fields.

Option 1 could take some time, though.

We had tested upgrades from OpenX Source 2.8.11 and various Revive Adserver versions with both MySQL and Postgres and never hit this issue. I've also performed a fresh install on Percona with default settings, but the defaults weren't added.

Share this post


Link to post
Share on other sites
1 hour ago, Richard Cook said:

I noticed in the log that it does not acknowledge that it found a previous installation of Revive Ad server. Could this be part of the issue?

Attempting to detect an existing Revive Adserver installation...

Revive Adserver 4.0.1 detected

This version can be upgraded

 

Hi @Richard Cook,

Looks to me like it _does_ find your 4.0.1 installation and attempts to upgrade it. 

You would not be seeing this issue if it wasn't attempting an upgrade.

The issue appears to be that some databases do not have the expected database schema to match their version (and 4.1.0 fixes some issues to ensure that Revive Adserver now correctly detects those mismatches in expected database schema).

22 minutes ago, gabrielt said:

How do I do that?

Hi @gabrielt,

https://stackoverflow.com/questions/41810796/mysql-remove-default-value-for-datetime-field

Looks like that should work for other columns where the default is not expected. 

Share this post


Link to post
Share on other sites

Hi @andrewatfornax,

That log was from my 4.0.1 to 4.0.2 upgrade. 

 

The log after that, is from 4.0.2 to 4.1, which does not show the acknowledgement that it found 4.0.2.

 

From the install.log file for 4.1 (failed attempt):

Attempting to detect an existing Revive Adserver installation...

schema file found: -----------/etc/changes/schema_tables_core_621.xml

Share this post


Link to post
Share on other sites

I do have exactly same problem, when trying to upgrade from 4.0.2 to 4.1.0

Could this problem be related to the fact, that I have upgraded from MySQL 5.1 to 5.5 during the update from adserver 4.0.1 to 4.0.2.
Anyway, the update from adserver 4.0.1 to 4.0.2. went very smooth as always.

I hope that there is a solution to this issue soon.

Best regards

Michael

Edited by mibert

Share this post


Link to post
Share on other sites

Hello everyone!

Chances are that we won't be able to release a 4.1.1 final next week, but in the meantime it would be great if you could test on your staging environment this pre-release package that should fix the upgrade problems that you reported (along with the actual upgrade from phpAdsNew itself, which was broken since 3.2).

You can download the beta packages here:

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...