OK here is my theory about the "ad infinitum" problems in your 'main server' --
your server is receiving sufficient traffic that Apache shuts down & restarts
child processes regularly. Each new process separately recognizes the
cache.flush file (even though it hasn't changed) and "acknowledges" that with
the warning.
I think I'd like to keep the warning, but avoid printing it more than once per
server each time the file is touched.
Original comment by jmara...@google.com on 13 Nov 2012 at 1:50
Server #1, physical server, 200+ websites and a lot of traffic. Still
repeating "Cache Flush 0" with ~1k log entries per hour.
Server #2, virtual server, 1 website, minimal traffic. "Cache Flush" value
incrementing each time - counter now approaching 100.
Server #3, virtual server, 1 website, little or no traffic. No "Cache Flush"
reported in error.log.
Original comment by dun...@chirp.com.au on 13 Nov 2012 at 1:59
Original issue reported on code.google.com by
jmara...@google.com
on 13 Nov 2012 at 1:47The text was updated successfully, but these errors were encountered: