Jump to content

manuel

Approved members
  • Content Count

    6
  • Joined

  • Last visited

  1. 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.
  2. I am confused about the new geopip feature from RV 5.0 and above and the required maxmind database. Example: We are primarily targeting European countries (Country Level e.g. Spain, Germany) occassionally targeting zip-Codes in Europe (Germany only) and very rarely countries outside Europe (USA only) Based on the example I am wondering … Do we need to buy the country AND city database or would it be enough to buy the city database only, assuming city level covers country level as well? Does the city database also cover European zip-Codes? At the Revive blog https://www.revive-adserver.com/blog/new-geotargeting-plugin-in-revive-adserver-v5-an-overview/ it quotes that zip targeting is available in the US/Canada area only, however, on MaxMind it says that the GeoIP2 City database covers postal codes worldwide: https://www.maxmind.com/en/geoip2-city - is there a mistake in the Revive blog, on MaxMind's Website or both are correct and Revive Adserver just does not support European zip-Code targeting? MaxMind offers a cheaper City database by (selected) continent only. Assuming we are only targeting European zip Codes and European countries, is that continent-limited City database also supported by Revive Adserver? Details: https://www.maxmind.com/en/geoip2-city-database-by-continent How does automatic database update work? Is there any documentation available? Do we need to enter username/password of our MaxMind account / subscription to Revive adserver (said this we obviously need to have a subscription at MaxMind) and the rest is done by the daily maintenance script? Manuel
  3. 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.
  4. 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.
  5. We are not able to upgrade our Revive Adserver to 5.0.0. After the update the delivery rule sets are completely broken and can't be fixed by the maintenance/repair function either. Else, the DB seems to stay always at 4.2.1 version. More in Detail: Running the upgrade process the "Recompile_Acls" task and it seems to stall for a couple minutes, eventually throwing "Error occurred when running installation task "Recompile_Acls": Request timed out" while apparently finishing the upgrade successfully. After logging in to the upgraded Revive Adserber, product updates show that it's running Revive v5.0.0 but adding "warning: database is stamped as v4.2.1" suggesting that the DB upgrade didn't complete. PHP/nginx timeouts and memory limits have already been adjusted as to not cause any timeouts: memory_limit = 4096M, max_execution_time = 18000 After that no errors show up in the PHP error log (512M memory was apparently to little to process our ~17 GB data + ~17 GB index = 34 GB total DB) According to the install.log everything seems to finish successfully though: [...] attempting to include file /var/www/html/revive-adserver-5.0.0/etc/changes/tasks/openads_upgrade_task_Recompile_Acls.php Recompiling Acls OK Starting Acls Recompilation Acls Recompilation: Complete executed file /var/www/html/revive-adserver-5.0.0/etc/changes/tasks/openads_upgrade_task_Recompile_Acls.php Starting file-check for plugins... Finished file-check for plugins Starting file-check for plugins... Finished file-check for plugins (END) Between every attempted update we did a complete filesystem rollback to make sure the DB is back to its "known-good" 4.2.1 state. Same result every time - DB seems to stay at 4.2.1 and after the update the delivery rule sets are completely broken and can't be fixed by the maintenance/repair function either.
  6. Hi Andrew! I am struggling with delivering a banner to all Desktop users from Germany. Using Version 4.0.0 Initially i thought: GEO Country Germany AND Operating System Version any Windows OR Operating System Version any OS X OR Operating System Version any Linux But in this case, it delivers also to any OS X users in any country. To cut it short: If I will target Desktop (or Mobile) users in a specific country I would need to setup a banner for each operating system and limit it to the country, right? There is no way to combine a set of limitations? Manuel
×
×
  • Create New...