andrewatfornax reacted to Ravi Patel in Installation failed to create the core tables
Very late here to answer this,
I also got into this same error, And Here are my findings for this error :
I was selecting "MyIsam" in Table type Instead of InnoDB.
Check the below screenshots :
First Click : "See More Database Details"
Then Select "InnoDB" from Table Type.
And Done 😄
andrewatfornax reacted to AngryWarrior in Serve only to a language country? [Not working/bug??]
i think I actually managed to solve this issue. :-)
I deactivated and then deleted the Geo targeting plugin. Downloaded a fresh installation package of Revive Unzipped the package locally on my pc. I then uploading the geo targeting plugin zip file from the folder etc/plugins/reviveMaxMindGeoIP2.zip
Then as administrator head to plugins in the administrator dashboard e.g. https://yourdomain.com//www/admin/plugin-index.php?selection=plugins and upload the zip package and enable it. (it should happen automatically):
Then in that interface "plugins" chose the geo targeting plugin and click "Details" --> Settings --> License key. Go to Maxmind and generate a new license key https://www.maxmind.com/en/account/login
and then enter that new license key in the license field and hit "save".
Ok so next thing we need to do is to force Revive to initiate the download of the Maxmind database. So what yu need to do is to go back to the admin interface as admin and go to "plugins" e.g. https://yourdomain.com/www/admin/plugin-index.php.
The way this is done is simple by clicking "disable" then wait a minute and then re-enable the plugin again by clicking "Activate". This will force Revive to start downloading the database from Maxmind.
After the former step is done, then go to your Maxmind account and see if Revive has used your new key (confirms that it is working), result:
As you can see in my case Revive has now done a data query for the Maxmind database and used the license key. :-)
Ok so the final step is to see that it is finally working and that Geo targeting is working and added to your drop down list in banner settings click your Banner --> Deliver options --> Add deliver rule dropdown. Final Result:
So the whole problem I guess lies in the Revive never have downloaded the Maxmind database and thus it will therefor e not display the Geo targeting options in the Banner setting delivery options drop down for that reason. The solution is to follow the steps I provided above. I hope this might help others that may encounter the same issue as I have and be a helpful solution. :-)
andrewatfornax reacted to lunaraurora in 5.0.5 upgrade but can not change database password
thanks, that's useful .. i will look into it
andrewatfornax reacted to Ryan G in Statistics Will Not Show No Matter What, Help Sought
Thanks for this documentation @andrewatfornax - I was able to address this issue on my end. Was related to my plugins issue: https://forum.revive-adserver.com/topic/5683-upgrade-error-unable-to-locate-one-or-more-plugin-files/?tab=comments#comment-14335
andrewatfornax got a reaction from Ryan G in Statistics Will Not Show No Matter What, Help Sought
In addition to the above, @Turbo212, I notice that your oxcd_data_bkt_m table is MyISAM.
This table type only supports table level locking.
If you're under high load, it's possible that the table will be locked by delivery processes queued up to write their data when the hourly maintenance process wants to lock the table to make updates. Are you sure that's not happening? Your MySQL logs might give you more information on this.
andrewatfornax got a reaction from Ryan G in Upgrade Error: Unable to locate one or more plugin files
Just to round out the thread and confirm, when you upgrade, the upgrade wizard will ask you where the old installation is located, so that it can find the previous installation's plugin files, and copy them over (so that any 3rd party plugins are retained) and upgrade them (if they are core Revive Adserver plugins and need to be updated).
andrewatfornax reacted to bobdobs in HTML5 banner: Impression count too low v5.0.5
andrewatfornax reacted to adus in Extra redundancy
Thanks for the speedy reply!
Yeah we make heavy use of AWS and RDS so sadly cant put the code on the DB server but I always meant to double check for scaling purposes if the task could lock as most of the php nodes would just be exact mirrors.
I may spin a low end box up to handle the tasks but if I at least know it works as a mirrored then I can get under way with scaling anyway.
andrewatfornax got a reaction from adus in Extra redundancy
The maintenance process does have locking in place, to ensure that only once instance is triggered at a time, but personally, whenever I was managing a setup like that, I would put the Revive Adserver code on the central DB server too (even though it would not serve ads from there), and then run maintenance on that machine, so that there's no need for network traffic off-server to run maintenance.
Every millisecond counts, right? 🙂
andrewatfornax reacted to Artistan in Insecure Cookies Warnings - Non-SSL Cookies
Our load balancer forwards requests to the web servers via port 80 (insecure on the local network)
due to that, the web server + Revive does not automatically know that is should be serving secure links and cookies.
In order to resolve this we had to add a forwarded header to the load balancer that tells the server + Revive code that the connection is secure from the users browser.
search for `function setupConfigVariables` in the code to see what i am talking about, there are many different server settings to allow `$GLOBALS['_MAX']['SSL_REQUEST'] = true;`
andrewatfornax reacted to mitchems in Administrator Login loop on upgrade
I figured it out. I was installing the upgrade on a new AWS instance so that I wouldn't interrupt the old one. I found that it was still requiring HTTPS but I didn't have a cert on that server. By going into the host.domain,conf.php and changing requireSSL=1 to =0, that fixed my issue.
andrewatfornax reacted to stapel_eliz in error messages since update to v4.2.1
The problem turned out to be that my server host hadn't actually updated PHP from version 5-point-somthing, despite my request that they do so (and assurances that they had). When Revive did the update (via cPanel's Softaculous), it asked if it could update the version of PHP but, though I'd said "yes", the update didn't apparently go through.
The solution was to do the update myself.