be too slow or disrupted for about 7.00s; rescued 1 out of 1 I/Os
2017/03/15 20:57:09 kid2| WARNING: communication with /cache2/rock may
be too slow or disrupted for about 7.00s; rescued 1 out of 1 I/Os
2017/03/15 20:58:44 kid1| WARNING: communication with /cache2/rock may
be too slow or disrupted fo
cache_dir rock /cache4 11 min-size=262145 max-swap-rate=150
swap-timeout=500
Still don't know how /cache3 stopped and /cache4 is still active, even
with all those warnings and errors.. :/
--
Atenciosamente / Best Regards,
Heiler Bemerguy
Network Manag
| assertion failed: client_side_reply.cc:1167:
"http->storeEntry()->objectLen() >= headers_sz"
Maybe this explains why I have a lot of "SIZE MISMATCH" messages while
rebuilding rockstore cache?
--
Best Regards,
Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev
The "atop" tool may be useful for
collecting everything in one place. You will probably want to restart
Squid for a clean experiment/collection.
Trying to figure out how to use atop information...
--
Best Regards,
Heiler Bemerguy
Network Manager - CINBESA
55 91
Em 07/03/2017 13:14, Alex Rousskov escreveu:
On 03/07/2017 08:40 AM, Heiler Bemerguy wrote:
I'm using squid 4.0.18
And noticed something: (iostat -x 5)
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s
avgrq-sz avgqu-sz await r_await w_await svctm %util
sda
