renta Posted January 25, 2014 Report Posted January 25, 2014 Hello one more time. Finally, I've solved the task of upgrading of my adserver. But there were some strange behaviour: after running the upgrade wizard on step 2 of "Performing the Upgrade" section this article http://www.revive-adserver.com/support/upgrading/ I saw this message: Detected Revive Adserver 3.0.2 Revive Adserver is up to date Your Revive Adserver database and file structure are both using the most recent version and therefore no upgrade is required at this time. Please click Continue to proceed to the administration panel. But this is very strange, because I got 2.8.10 and I should see some upgrade steps like in article. My actions were: 1) Backups. 2) Unpack revive-adserver-3.0.2.tar.gz and rename it to "ox_new" (2.8.10 is in "ox" directory). 3) Make new db and user for it. 4) Fill new db with backup of old one (2.8.10). My tables got prefixes "ox_". 5) Copy config file from 2.8.10 to 3.0.2 Changed db information in it (user, pass, db name). In other attempt I've also changed the [webpath] section (admin, delivery, deliverySSL) because after running the upgrade I was redirected to old "ox" folder. 6) Run url with .../ox_new in the end and see the message I've write above. Without any mistakes or stranges. Is this behaviour weird or normal? In the admin panel of upgraded adserver I see all my zones and banners, but there are no new stat for about 3 hours after the upgrade? How I could detect if my new server is broken? Quote
renta Posted January 25, 2014 Author Report Posted January 25, 2014 My install.log Why old OpenX are not detected? I tried to upgrade with old and new paths in [webpath] section of config. How does Revive server detect the old installations? ========================================================================= 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 OpenX installation... OpenX 3.0.2 detected This version is up to date. Starting file-check for plugins... Plugin: openXBannerTypes - Unable to locate XML files Plugin: openXDeliveryLimitations - Unable to locate XML files Plugin: openX3rdPartyServers - Unable to locate XML files Plugin: openXReports - Unable to locate XML files Plugin: openXDeliveryCacheStore - Unable to locate XML files Plugin: openXMaxMindGeoIP - Unable to locate XML files Plugin: openXInvocationTags - Unable to locate XML files Plugin: openXDeliveryLog - Unable to locate XML files Plugin: openXMarket - Unable to locate XML files Plugin: openXWorkflow - Unable to locate XML files Plugin: openXVideoAds - Unable to locate XML files Finished file-check for plugins Starting file-check for plugins... Plugin: openXBannerTypes - Unable to locate XML files Plugin: openXDeliveryLimitations - Unable to locate XML files Plugin: openX3rdPartyServers - Unable to locate XML files Plugin: openXReports - Unable to locate XML files Plugin: openXDeliveryCacheStore - Unable to locate XML files Plugin: openXMaxMindGeoIP - Unable to locate XML files Plugin: openXInvocationTags - Unable to locate XML files Plugin: openXDeliveryLog - Unable to locate XML files Plugin: openXMarket - Unable to locate XML files Plugin: openXWorkflow - Unable to locate XML files Plugin: openXVideoAds - Unable to locate XML files Finished file-check for plugins Starting file-check for plugins... Plugin: openXBannerTypes - Unable to locate XML files Plugin: openXDeliveryLimitations - Unable to locate XML files Plugin: openX3rdPartyServers - Unable to locate XML files Plugin: openXReports - Unable to locate XML files Plugin: openXDeliveryCacheStore - Unable to locate XML files Plugin: openXMaxMindGeoIP - Unable to locate XML files Plugin: openXInvocationTags - Unable to locate XML files Plugin: openXDeliveryLog - Unable to locate XML files Plugin: openXMarket - Unable to locate XML files Plugin: openXWorkflow - Unable to locate XML files Plugin: openXVideoAds - Unable to locate XML files Finished file-check for plugins Starting file-check for plugins... Plugin: openXBannerTypes - Unable to locate XML files Plugin: openXDeliveryLimitations - Unable to locate XML files Plugin: openX3rdPartyServers - Unable to locate XML files Plugin: openXReports - Unable to locate XML files Plugin: openXDeliveryCacheStore - Unable to locate XML files Plugin: openXMaxMindGeoIP - Unable to locate XML files Plugin: openXInvocationTags - Unable to locate XML files Plugin: openXDeliveryLog - Unable to locate XML files Plugin: openXMarket - Unable to locate XML files Plugin: openXWorkflow - Unable to locate XML files Plugin: openXVideoAds - Unable to locate XML files Finished file-check for plugins Quote
andrewatfornax Posted January 25, 2014 Report Posted January 25, 2014 My install.log Why old OpenX are not detected? I tried to upgrade with old and new paths in [webpath] section of config. How does Revive server detect the old installations? It goes through a process of looking for various options - so as you can see, it says that PAN (phpAdsNew) was not detected, then that MMM was not detected, etc. until it eventually says that it could find "OpenX" 3.0.2, which it "upgraded". However you did it, you must have upgraded the database to the new version at some point, and have then repeated the upgrade! Quote
renta Posted January 25, 2014 Author Report Posted January 25, 2014 However you did it, you must have upgraded the database to the new version at some point, and have then repeated the upgrade! But I started the upgrade when new database for 3.0.2 were filled with tables from old OpenX db. And now I can see all the banners and campaigns from OpenX in "upgraded" Revive admin. So, I suppose that db is upgraded now, but somehow Revive haven't found the OpenX installation. Quote
andrewatfornax Posted January 27, 2014 Report Posted January 27, 2014 Well, that's what you think you did, but the Revive log is saying something different - or perhaps you repeated the upgrade by accident - or someone else accessing the site did too, and if you look further back in the log file, you will see a different set of messages? Quote
renta Posted October 8, 2014 Author Report Posted October 8, 2014 Sorry for bumping such an old theme, but I think, that I've realised the reason of my problem. Today I've upgraded Revive to 3.0.5 and one time had the problem: new version had not seen the old one. The problem was with config file. It's name is like "www.example.com.conf.php" and I've started to upgrade in "http://example.com/revive_new". So, seemed that Adserver don't find the config file with "www". andrewatfornax 1 Quote
andrewatfornax Posted February 8, 2016 Report Posted February 8, 2016 Good point, @renta. It's important that you use the correct domain that works with the Revive Adserver setup.Reading http://documentation.revive-adserver.com/display/DOCS/Managing+Configuration+Files may help understand how things work. Erik Geurts 1 Quote
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.