It is just a minor debug message that accidently was left at a too
high debug level.
The reason why you are now receiving these is most likely a slight
change in the workload your Squid receives, now triggering the
aioCancel action. This is when Squid aborts a disk I/O operation,
most likely because the client is no longer there (aborted the
request).
In src/fs/aufs/async_io.c, just change the debug(0,0) on line 173 to
debug(32, 2) and you will get rid of the message, or upgrade to
Squid-2.5.
Regards
Henrik
On Saturday 23 February 2002 00:55, Web server manager wrote:
> I've just switched some of our cache systems to 2.4.STABLE4 (were
> on STABLE2 plus a couple of patches), and am seeing a fair number
> (every few minutes, sometimes several almost at the same time) of
> messages "this be aioCancel" in cache.log. I don't recall seeing
> this before, even though on checking the source code I find it
> *was* in STABLE2 so it's not just a newly-added message.
-- MARA Systems AB, Giving you basic free Squid support Customized solutions, packaged solutions and priority support available on requestReceived on Fri Feb 22 2002 - 18:46:20 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:06:31 MST