On 02.02.17 15:54, Tory M Blue wrote:
> I'm not seeing any issue but the error is rampant at this point > > 2017/02/02 10:58:59 kid1| /cache/07/49/003749FE > 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or > directory > 2017/02/02 10:59:00 kid1| /cache/05/3E/00053EA0 > 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or > directory > 2017/02/02 10:59:00 kid1| /cache/0D/EB/005DEB19 > 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such file or > directory > 2017/02/02 10:59:00 kid1| /cache/02/27/0002273A
Squid uses a journal file swap.state to store changes to the cache. On restart it is used to reconstruct the cache index fast. If you cause Squid to shutdown very fast (kill -9, systemd crashing it, or shutdown_lifetime too short) then it does not have time to fully update the journal entries.
These are systemctl stop squid and systemctl start squid, so nothing dramatic or nasty, should be shutting down cleanly
"should be" ... still depends on shutdown_lifetime and the systemd can still be instructed to kill squid, look at squid.service -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95 _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
