But that's a different issue, I don't see these errors - but the output of analog, awstats and webalizer should be suppressed, no need to receive an email from cron.daily about running the stats.That error will get resolved as part of case EA-9789 discussed here: In Progress - EA-9789 - NGINX Anacron Logrotate Error
Sounds great! Thanks for the update and we would definitely be interested in any advice the cPanel team might have.Thanks for all the great feedback. I've let our webserver team know about the caching issues so they are looking into some options to help with that, and they are keeping an eye on this thread.
Hi Rex! Unfortunately Im afraid I have to agree with RobinF28.@RobinF28 - what you're seeing is actually the intended behavior of the software. Nginx by default caches requests, which lowers the burden on Apache and speeds up results for customers. If you make an update to a site you'll need to either wait for the cache to time out, which can be up to an hour by default, or you'll need to manually clear it.
This of it as a basic sedan versus a sports car. The sedan gets you from point A to point B just fine, but the sports car needs more fine-tuning for that extra performance. Nginx is just another layer of fine-tuning.
|Thread starter||Similar threads||Forum||Replies||Date|
|C||Anyone using Linode.com?||Server Management||0|
|L||Anyone using Zenoss?||Server Management||3|
|J||NSIV (rfxnetwork) - anyone using it ?||Server Management||0|
|anyone using DRAMSystem for billing/hosting management?||Server Management||0|
|W||Anyone using TUX?||Server Management||1|