scott001 Posted October 5, 2019 Report Share Posted October 5, 2019 I just upgraded to 5.0, ran the upgrade wizard, all seemed to go fine, but was expecting after it ran that when I went to my acp I would be prompted to update my database...I was not. When I go now to the Product Updates area I see: You are currently using Revive Adserver v5.0.0 (warning: database is stamped as v4.2.1) running on Apache, PHP 7.3.10 and MySQL 5.5.5-10.3.18-MariaDB. So was my database supposed to upgrade with 5.0? Now that it didn't happen, how can I upgrade it? Quote Link to comment Share on other sites More sharing options...
scott001 Posted October 5, 2019 Author Report Share Posted October 5, 2019 PS - I did follow your upgrade process perfectly, copied over the new files, etc. I've been running this for over 10 years now, so know how to upgrade. I think you have a bug in your updater this time. I reverted my copy back to 4.2.1. Quote Link to comment Share on other sites More sharing options...
manuel Posted October 9, 2019 Report Share Posted October 9, 2019 Hi Scott! We have the same issue. Refer to Forum entry: Seems to be the same issue and a general issue for all installations that run since a few years. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted October 11, 2019 Report Share Posted October 11, 2019 Related? https://github.com/revive-adserver/revive-adserver/issues/1103 Quote Link to comment Share on other sites More sharing options...
scott001 Posted October 15, 2019 Author Report Share Posted October 15, 2019 Still no fix for this issue?? Quote Link to comment Share on other sites More sharing options...
manuel Posted October 18, 2019 Report Share Posted October 18, 2019 We have deleted old campaigns through the interface, eliminatiing potential old targeting rules and reducing the database from 34gb to 20gb. upgrade tasks performed quicker but we still get the same warning as before: "Sie nutzen derzeit Revive Adserver v5.0.0 (warning: database is stamped as v4.2.1)" no matter what we do, we are still not able to fully upgrade our revive instance. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted October 20, 2019 Report Share Posted October 20, 2019 The GitHub ticket above has been closed now; you could try again with the changes from the ticket manually merged into the 5.0.0 release? Quote Link to comment Share on other sites More sharing options...
scott001 Posted November 1, 2019 Author Report Share Posted November 1, 2019 I still have not tried to upgrade again. If you have made no changes to the 5.0 release, the same thing will happen, and I won't be able to upgrade. Were there any changes made to the software since I had this issue? Quote Link to comment Share on other sites More sharing options...
lunaraurora Posted November 4, 2019 Report Share Posted November 4, 2019 It's possible that by doing an upgrade but keeping the old database, it also show the old version of revive adserver. Edit database inside table: rv_application_variable and table name: oa_version change from 4.2.1 to 5.0.0 it should do the trick Quote Link to comment Share on other sites More sharing options...
manuel Posted November 21, 2019 Report Share Posted November 21, 2019 We have updated from RV 4.2.1 now to 5.0.2 (upgrading to 5.0 was not working due to the bugs already described). The upgrade to 5.0.2 worked fine now (no Errors) however, the data base ist still stamped to v4.2.1 "Sie nutzen derzeit Revive Adserver v5.0.2 (warning: database is stamped as v4.2.1) laufend auf nginx 1.10.3, PHP 7.0.33-0ubuntu0.16.04.7 und MySQL 5.7.28-0ubuntu0.16.04.2".  In the mainatainance wizard the interface asks to upgrade to Version 5.0.2 because we do not have the latest Version ... In the install log of previous Version we receive this:                                openads_upgrade_5.0.0-beta-rc1.xml 4.2.1 5.0.0-beta-rc1   2019-11-21 17:12:53   Restbestandteil: 1 Logfiles: openads_upgrade_5.0.0-beta-rc1_2019_11_21_05_12_53.log   upgrade_openX3rdPartyServers 1.3.1 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:06   Restbestandteil: 1 Logfiles: plugins.log   ox3rdPartyServers_version_stamp_1.5.0 1.3.1 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:06   Restbestandteil: 1 Logfiles: ox3rdPartyServers_upgrade.log   upgrade_openXVideoAds 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: plugins.log   vastInlineBannerTypeHtml_version_stamp_1.12.0 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: vastInlineBannerTypeHtml_upgrade.log   vastOverlayBannerTypeHtml_version_stamp_1.12.0 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: vastOverlayBannerTypeHtml_upgrade.log   oxLogVast_version_stamp_1.12.0 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: oxLogVast_upgrade.log   vastServeVideoPlayer_version_stamp_1.12.0 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: vastServeVideoPlayer_upgrade.log   videoReport_version_stamp_1.12.0 1.11.9 1.12.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:09   Restbestandteil: 1 Logfiles: videoReport_upgrade.log   upgrade_openXReports 1.5.5 1.6.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:13   Restbestandteil: 1 Logfiles: plugins.log   oxReportsStandard_version_stamp_1.6.0 1.5.5 1.6.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:12   Restbestandteil: 1 Logfiles: oxReportsStandard_upgrade.log   oxReportsAdmin_version_stamp_1.6.0 1.5.4 1.6.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:12   Restbestandteil: 1 Logfiles: oxReportsAdmin_upgrade.log   uninstall_openXMaxMindGeoIP 1.3.10 ---   2019-11-21 16:13:15   Restbestandteil: 1 Logfiles: plugins.log   uninstall_oxMaxMindGeoIP 1.3.10 ---   2019-11-21 16:13:15   Restbestandteil: 1 Logfiles: plugins.log   upgrade_openXInvocationTags 1.4.7 1.5.1 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:18   Restbestandteil: 1 Logfiles: plugins.log   oxInvocationTags_version_stamp_1.5.1 1.4.7 1.5.1 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:18   Restbestandteil: 1 Logfiles: oxInvocationTags_upgrade.log   upgrade_openXDeliveryLog 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: plugins.log   oxDeliveryDataPrepare_version_stamp_1.5.0 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: oxDeliveryDataPrepare_upgrade.log   oxLogClick_version_stamp_1.5.0 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: oxLogClick_upgrade.log   oxLogConversion_version_stamp_1.5.0 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: oxLogConversion_upgrade.log   oxLogImpression_version_stamp_1.5.0 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: oxLogImpression_upgrade.log   oxLogRequest_version_stamp_1.5.0 1.1.2 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:22   Restbestandteil: 1 Logfiles: oxLogRequest_upgrade.log   upgrade_openXDeliveryLimitations 2.2.1 5.0.3 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:26   Restbestandteil: 1 Logfiles: plugins.log   Client_version_stamp_5.0.3 2.2.1 5.0.3 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:26   Restbestandteil: 1 Logfiles: Client_upgrade.log   Geo_version_stamp_5.0.3 2.2.1 5.0.3 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:26   Restbestandteil: 1 Logfiles: Geo_upgrade.log   Site_version_stamp_5.0.3 2.2.1 5.0.3 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:26   Restbestandteil: 1 Logfiles: Site_upgrade.log   Time_version_stamp_5.0.3 2.2.1 5.0.3 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:26   Restbestandteil: 1 Logfiles: Time_upgrade.log   upgrade_openXDeliveryCacheStore 1.2.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:29   Restbestandteil: 1 Logfiles: plugins.log   oxCacheFile_version_stamp_1.5.0 1.2.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:29   Restbestandteil: 1 Logfiles: oxCacheFile_upgrade.log   oxMemcached_version_stamp_1.5.0 1.2.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:29   Restbestandteil: 1 Logfiles: oxMemcached_upgrade.log   upgrade_openXBannerTypes 1.3.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:32   Restbestandteil: 1 Logfiles: plugins.log   oxHtml_version_stamp_1.5.0 1.3.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:32   Restbestandteil: 1 Logfiles: oxHtml_upgrade.log   oxText_version_stamp_1.5.0 1.3.0 1.5.0 UPGRADE ABGESCHLOSSEN  2019-11-21 16:13:32   Restbestandteil: 1 Logfiles: oxText_upgrade.log   install_reviveMaxMindGeoIP2 --- 1.0.4   2019-11-21 16:13:41   Restbestandteil: 1 Logfiles: plugins.log   install_rvMaxMindGeoIP2 --- 1.0.4   2019-11-21 16:13:41   Restbestandteil: 1 Logfiles: plugins.log   install_rvMaxMindGeoIP2Maintenance --- 1.0.4   2019-11-21 16:13:41   Restbestandteil: 1 Logfiles: plugins.log  Despite my initial thought that the update worked fine and just the DB Version was not stamped correctly, I have no realized that no Banners work anymore: all banners got the "last update" timestamp "01.01.2000 00:00:01"; clicking on the banner details page in the admin interface opens a white page. seems, interface is not able to load banner details. we have rolled back now to 4.2.1 version again.  Quote Link to comment Share on other sites More sharing options...
scott001 Posted November 26, 2019 Author Report Share Posted November 26, 2019 Still no solution? Nobody can upgrade? Quote Link to comment Share on other sites More sharing options...
manuel Posted December 29, 2019 Report Share Posted December 29, 2019 (edited) @scott001 same here. No chance to update. We have tried several times, also with tweaking it manually. We tried to reproduce it with a sequence of old installations. same as with our working Installation. Not working. @andrewatfornax If any of the coders want to reproduce that issue on a working enviroiment, feel free to get in touch with me. Hope we can jointly sort that bug. Edited December 29, 2019 by manuel Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted December 31, 2019 Report Share Posted December 31, 2019 Apologies, I lost track of the issue here. So what's the issue? I can see that @manuel, it looks like you reported that you can upgrade, and it completes, but the DB version isn't updated. Is that the only outstanding issue? Is there a GitHub ticket for that? Quote Link to comment Share on other sites More sharing options...
manuel Posted January 6, 2020 Report Share Posted January 6, 2020 Update is still not working. After upgrading we faced these issues: - Database stamp still on old version (no changes made to database) - In the mainatainance wizard the interface still asked to upgrade to Version 5.0.2 (although upgraded) - All campaigns received new start and campaign dates "0000-00-00" - All targeting rules totally broken or dissapperard We are now still working on 4.2.1; no Chance to get 5.0.2 running with old data. We are using revive since 12 years. We did some upgrade Trials with other old installations as well. Some issues seam to apply since v3 in below. Manuel Quote Link to comment Share on other sites More sharing options...
scott001 Posted January 13, 2020 Author Report Share Posted January 13, 2020 I still can't upgrade for the reasons listed above. It would be nice if they could look into this. I too have an old installation...I've been running it since it was PHPAdsNew, so way over 10 years. Quote Link to comment Share on other sites More sharing options...
kal Posted January 22, 2020 Report Share Posted January 22, 2020 Same here. I udated version 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 and every time: You are currently using Revive Adserver v5.0.4 (warning: database is stamped as v4.2.1) running on Apache 2.4.41, PHP 7.3.11 and MySQL 5.7.27-30. Quote Link to comment Share on other sites More sharing options...
scott001 Posted January 22, 2020 Author Report Share Posted January 22, 2020 I am still stuck on v4.2.1 and nobody at Revive seems to notice this thread... Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted January 28, 2020 Report Share Posted January 28, 2020 I notice, but that doesn't always unfortunately equate to having time to do anything about it. Detailed bug reports highlighting a step through with an IDE that provides us the parts of the code that are failing, and a PR to fix the issue, are always welcomed ? Otherwise, I am hoping to be able to resume more active work on the project from next week. @manuel, you still have an environment that doesn't upgrade, and willing to share your install code base and DB backup?  Quote Link to comment Share on other sites More sharing options...
scott001 Posted February 3, 2020 Author Report Share Posted February 3, 2020 (edited) Please ignore the post I made...got my forum's confused! I still haven't attempted an upgrade due to the database issue. Is there any news? Edited February 3, 2020 by scott001 Posted in wrong forum... Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted February 5, 2020 Report Share Posted February 5, 2020 Hi @scott001, No news, but I'll ask the same question of you as I asked above - are you willing to share your installed code base and a DB backup, so that I can take a look? Quote Link to comment Share on other sites More sharing options...
scott001 Posted February 5, 2020 Author Report Share Posted February 5, 2020 yes, but is it possible for me to flush out most of the subscribers beforehand? Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted February 10, 2020 Report Share Posted February 10, 2020 Sure, no worries at all - happy to have a stripped down DB, if you could please verify that the upgrade issue still exists after sanitising the data. Quote Link to comment Share on other sites More sharing options...
scott001 Posted February 11, 2020 Author Report Share Posted February 11, 2020 Ok, it might take me a week or so, but I'll get it together... andrewatfornax 1 Quote Link to comment Share on other sites More sharing options...
manuel Posted February 24, 2020 Report Share Posted February 24, 2020 @andrewatfornax sorry, had been on holiday. upgrade issue still exists. we are still not able to upgrade to RS 5. What info would you need to look at it? I'll ask our admin to provide all relevant info for you or would be fine to give Access for you as well. what would you prefer? text a pm. manuel  Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted February 27, 2020 Report Share Posted February 27, 2020 Hi @manuel, The idea situation for me would be access to a zip or tar file, containing a backup of your database, and a full copy of your Revive Adserver directory code. This will allow me to set things up as you have it, and then run through the upgrade process to check what is happening. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.