Jump to content

Ian

Administrators
  • Posts

    379
  • Joined

  • Last visited

Everything posted by Ian

  1. The 'only' thing you can do is tweaking the memcached settings in the configuration file, mine looks like this : PORT="11211" USER="memcached" MAXCONN="8192" CACHESIZE="16" OPTIONS=""
  2. Too vague of a question to give a proper answer. Anyway, it's as you said opensource .. so you could let something develop for your customised needs.
  3. If you use php7 i would recommend you to downgrade to php 5.6 for the time being.
  4. You can contact me via a PM, it's most likely an easy solve.
  5. Ian

    pick list

    Hmm, maybe you could explain a bit more thorough on what you are doing, and what you exactly want as result. I'm not sure anyone is able to help with the amount of information you have provided.
  6. @jnunez Jimmy T. gave a good tip there as well. To enable memcache (be sure to have memcached running, and to have the php module installed on all delivery boxes!!) : Go to Plugins --> Delivery cache store, click on "Details". Go to OXmemcached --> Settings--> OXmemcached configuration settings, in that "List of memcached server" it holds local ip address and port number (typically 127.0.0.1:11211 .... Just set the correct value and check to the working ---- Go to Configuration-->Global Settings --> Banner Delivery Settings --> Banner Delivery Cache Settings, Under this, there will be "Banner Delivery Cache Store Type", choose memcached. If you need more help, feel free to PM me!
  7. So is there an actual issue you encounter? Or you simply find it a lot? You could try implementing memcache ...
  8. Change hosting provider, or outsource the hosting of your adserver.
  9. You most likely have a cronjob running, with wget or so which automatically saves the file. you could add to your wget command the -O flag to specify the save location for the file, which you can point to /dev/null, and your issue is solved.
  10. It does not, do you encounter brute-force attacks ?
  11. Did you check your apache/nginx/php-fpm error logs ?
  12. I cannot tell you how they have gotten your password(s). Those JS-iframes can be vicious, but you should be fine if you applied your browser patches/updates. The ones I have seen are mostly targeted on older IE versions.
  13. Did you try changing your password ? I'm not aware of a recent exploit.
  14. That depends, if I recall correctly from 3.2.2 are no database changes made. Anything under I recommend restoring a backup, and doing the upgrade via the 'official' procedure :)
  15. Be sure to check if there is not a file outside of your Revive folder which infects it again. Or maybe even a cronjob (i've seen it happening) also be sure to htaccess your /www/api and change passwords from all users.
  16. I hope like every sane user who uses OpenX 2.8.7, he has upgraded to the latest Revive version...
  17. On your server, mostly located in .. /var/log/maillog
  18. http://dev.maxmind.com/geoip/legacy/geolite/ Try the 'Geolite Country' it is free by the way. Netspeed is unsupported.
  19. Because nobody paid for the development of it yet ! Are you interested?
×
×
  • Create New...