Snoork Hosting

It looks like something related with your GeoIP country database. Make sure you have GeoIP installed in the server, have the latest MaxMind GeoIP country database loaded, and your patch is set correctly to the GeoIP country database.

The maintenance script is trying to utilize 135 MB of memory, but it's failing due to the PHP memory limit being too low. You need to increase the PHP memory limit at the server level and restart Apache for the changes to apply. Some hosting providers don't allow you to add your own custom php.ini and make changes to it, so you may need to contact your hosting provider and have them increase the limit for you if you are hosting your revive on shared hosting.

Revive Adserver does not run the maintenance in real-time, as it would result in a huge performance impact. It runs it on the scheduled maintenance you set. Make sure you either have the maintenance inside Revive enabled or have a cron job setup with the maintenance.

I'm afraid not, as AdBlock will even block Google Adsense ads.

Do you have the latest GeoIP country database loaded?

Which 3rd party ad providers do you need integration with?

Hi, For Revive you want the full dedicated performance of storage and CPU. With DigitalOcean you have shared storage and virtual CPU, which is alright for serving small amount of impressions, but for anything larger you will start seeing performance issues and instability. I would recommend checking this topic http://forum.revive-adserver.com/topic/565-traffic-overload-on-database-server/ for more information. The user was hosting his Revive Adserver on Amazon Web Services, which is almost identical to DigitalOcean, but since DigitalOcean uses KVM instead of Xen virtualization, the performance with DigitalOcean will be even lower than compared to Amazon Web Services. I personally do not recommend using Cloud Servers for Revive Adserver due to lack of performance and instability. For Revive Adserver you want a fully dedicated environment where Revive Adserver can take the full potential of the hardware. Thank you.

Hi, I do not believe having SEO friendly URL for ad delivery is really going to make any difference, as it's more of an internal system rather than publicly accessible pages. Also I would not recommend making changes to the URL of ad delivery as in the future if you would want to upgrade to a new version of Revive, there may be complications in the long run. Adding an SSL (https://) to your URL of ad serving may be something that you can look into instead. This will give you and your customers an extra layer of secure connection.

Correct, this is not a bug but an issue with the server being overloaded. I would recommend to contact your hosting provider.

Everything looks fine from the running maintenance. Is there a possibility a user could be abusing your ad tags? Try replacing your files again and see if that makes any difference.

Check your debug.log file and see if the maintenance is running or if there are any errors. I recommend setting up the maintenance through a cron job.

Can you check your debug.log file and see if there are any errors.

We have ran benchmark tests to find the perfect combination in order to allow our customers serve the most impressions from a single server and APC wasn't that great. For instance you can get much better performance and serve much greater amount of impressions more smoothly by using Memcache.

I'm glad everything is working out for you fine. Thank you for the update

How many impressions do you want to serve per day/month? In most cases load balancing is not needed, as you can serve a very large amount of impressions off a single server with no issues.

If you are getting too many MySQL queries you need to optimize your MySQL server and utilize fast disk storage such as SSD or SAS 15K. If you are running your Revive Adserver on a NAS storage such was Amazon Web Services, you will be getting performance issues especially with MySQL queries. With properly server hardware, setup, and optimizations you can server over 20 million impressions per day. We have performed stress tests and benchmarks on very high traffic Revive Adserver setups and Memcached actually resulted in performance degradation when you compare it to using SSD or SAS storage.

If you serve a large quantity of impressions, I would highly recommend setting up the maintenance through a cron job. Running the maintenance through the automated system from Revive Adserver control panel may sometimes fail if you have low PHP configuration values set such as PHP memory, times, execution times, etc...

It does not affect the statistics, but I would not recommend using APC, as you can get a much better performance if you do a combination of PHP eAccelerator, Nginx, and Memcached.

I'm not sure how your load balancing is setup to be exact, but if you are load balancing between 2 nodes, you should have everything going to a single master database. The 2 slaves should just record the data and transfer it over to the master database. Keep in mind that you may be seeing a much larger increase in impressions in your Revive Adserver than compared to Google if you do not have any protection against bots, fraudulent traffic, etc... How much impressions do you see in Google and in Revive?

The delivery engineer is pretty accurate as Erik mentioned above. I myself haven't had any issues with it and all ads get delivered as set.

Haven't came across such problem. Double check to make sure your database has full privileges and check file/folder permissions (CHMOD). Also if you are running Mod Security on your hosting, that can trigger certain functions of scripts to be blocked. When you click save, do you get a successful messages or any errors?

Revive Adserver is pretty secure by itself if you are running the latest version. If your Revive Adserver continues to get hacked/compromised, you may want to check the security of your hosting service.

What error message are you getting? You may need to increase your PHP memory size and timeout, as they can sometimes limit your exports.

The reason why I asked if you could install clean Revive on your new server would be to check and see if it will be working. This would be just for testing purposes. That way we can roll out any server side issues. Also when transferring Revive, your data files do not change, so there should be no reason for Revive to not work on the new server, unless the new server is not properly configured.

Try installing a fresh Revive Adserver on your domain name and see if it will function properly.