HBK wrote: > > Hi > > I'm getting following error messages in cache.log > > ----------------------------------------------------------------------- > 2003/02/25 10:16:10| storeAufsOpenDone: (2) No such file or directory > 2003/02/25 10:16:10| /cache/0F/6A/000F6A8F > 2003/02/25 10:16:16| storeAufsOpenDone: (2) No such file or directory > 2003/02/25 10:16:16| /cache/0F/6A/000F6A7A > 2003/02/25 10:16:40| storeAufsOpenDone: (2) No such file or directory > 2003/02/25 10:16:40| /cache/0F/6A/000F6AAE > 2003/02/25 10:16:42| storeAufsOpenDone: (2) No such file or directory > 2003/02/25 10:16:42| /cache/0F/6A/000F6AB6 > 2003/02/25 10:16:43| storeAufsOpenDone: (2) No such file or directory > 2003/02/25 10:16:43| /cache/0F/6A/000F6AB9 > ------------------------------------------------------------------------ > > Using following Version > Squid Cache: Version 2.5.STABLE1-20030205 > configure options: --prefix=/usr/local/squid --enable-async-io --enable-snmp > > Can any one explain why I'm getting this and how to fix it
I am getting those too regularly, (in 2.5S1). It's not a real bug , I think and following discussions in the past more due to the nature of the aio mechanisms ,following subtle issues where a file can be deleted which is needed for opening or reading in another thread. Maybe one could state that aio is not 'cache safe', but the thing is that squid will fetch the object again from the remote webserver. The intend of course being that these messages should be rather infrequent. M. > > Thanks -- 'Time is a consequence of Matter thus General Relativity is a direct consequence of QM (M.E. Mar 2002)
