<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA256 <br>
<br>
Don't think so.<br>
<br>
This messages floods all time?<br>
<br>
26.02.16 0:17, Heiler Bemerguy пишет:<br>
<span style="white-space: pre;">><br>
> I waited squid -z to finish.. did a "ps auxw |grep squid" a
dozen times to check.. THEN I started it.<br>
> It may have tried to serve something, as lots of users we're
already conecting to it right after it started, but I'm still
seeing a flood of warnings on error.log:<br>
><br>
><br>
> /2016/02/25 15:06:38 kid1| WARNING: swapfile header
inconsistent with available data//<br>
> //2016/02/25 15:06:38 kid1| WARNING: swapfile header
inconsistent with available data//<br>
> //2016/02/25 15:06:38 kid1| WARNING: swapfile header
inconsistent with available data//<br>
> //2016/02/25 15:06:39 kid1| WARNING: swapfile header
inconsistent with available data/<br>
><br>
> It's curious that with only one cache_dir (the first one), I
didn't receive any of these errors...<br>
> Maybe the non-rounded "4097" value is causing an issue?<br>
><br>
> Best Regards,<br>
><br>
> -- <br>
> Heiler Bemerguy - (91) 98151-4894<br>
> Assessor Técnico - CINBESA (91) 3184-1751<br>
><br>
><br>
> Em 25/02/2016 14:18, Amos Jeffries escreveu:<br>
>> On 26/02/2016 5:58 a.m., Heiler Bemerguy wrote:<br>
>>> Hi Alex, Eliezer, Yuri, Amos..<br>
>>><br>
>>> So, to start from the start, after seeing squid was
totally stable and<br>
>>> fast, running with NO cache_dirs, I tried to add only
2 rockstore<br>
>>> cache_dirs to test.<br>
>>><br>
>>> conf:<br>
>>> /cache_dir rock /cache2/rock1 20000 min-size=0
max-size=4096<br>
>>> slot-size=2048//<br>
>>> //cache_dir rock /cache2/rock2 30000 min-size=4097
max-size=16384<br>
>>> slot-size=4096/<br>
>>> (ps.: I know it would be nice to use one store PER
partition/disk/lun<br>
>>> whatever.. but I'm trying to lessen disk wasting by
using small<br>
>>> slot-sizes for small files.. am I wrong?)<br>
>>><br>
>>> Then squid -z:<br>
>>> /2016/02/25 13:42:00 kid2| Creating Rock db:
/cache2/rock1/rock//<br>
>>> //2016/02/25 13:42:00 kid3| Creating Rock db:
/cache2/rock2/rock/<br>
>>><br>
>>> Then running squid for the first time with these
newly created rock<br>
>>> stores....<br>
>>><br>
>>> /2016/02/25 13:42:09 kid3| Loading cache_dir #1 from
/cache2/rock2/rock//<br>
>>> //2016/02/25 13:42:09 kid2| Loading cache_dir #0 from
/cache2/rock1/rock//<br>
>>> //2016/02/25 13:42:09 kid3| Store rebuilding is 0.01%
complete//<br>
>>> //2016/02/25 13:42:09 kid2| Store rebuilding is 0.01%
complete/<br>
>>><br>
>>> Rebuilding what? just creating the huge files I
think...<br>
>> The cache index for those rock DB.<br>
>><br>
>> Unlike UFS which stores a swap.state file, rock rebuilds
its index on<br>
>> each startup.<br>
>><br>
>>> Then:<br>
>>> /2016/02/25 13:42:19 kid1| WARNING: swapfile header
inconsistent with<br>
>>> available data<br>
>>> 2016/02/25 13:42:21 kid2| WARNING: cache_dir[0]:
Ignoring malformed<br>
>>> cache entry meta data at 6943832064<br>
>> <snip repeats><br>
>>> 2016/02/25 13:42:40 kid1| ctx: enter level 0:<br>
>>>
'<a class="moz-txt-link-freetext" href="http://static.bn-static.com/pg/0plcB0QjJpBbwN7rMMDjKKO5Z63Nhu3zfPw==.gif">http://static.bn-static.com/pg/0plcB0QjJpBbwN7rMMDjKKO5Z63Nhu3zfPw==.gif</a>'<br>
>>> 2016/02/25 13:42:40 kid1| WARNING: swapfile header
inconsistent with<br>
>>> available data<br>
>>> 2016/02/25 13:42:40 kid2| WARNING: cache_dir[0]:
Ignoring malformed<br>
>>> cache entry meta data at 19581075456<br>
>>> 2016/02/25 13:42:41 kid2| WARNING: cache_dir[0]:
Ignoring malformed<br>
>>> cache entry meta data at 19757760512<br>
>>> 2016/02/25 13:42:43 kid2| Finished rebuilding storage
from disk.<br>
>>> 2016/02/25 13:42:43 kid2| 10239992 Entries scanned<br>
>>> 2016/02/25 13:42:43 kid2| 14 Invalid
entries.///<br>
>>><br>
>>> What entry? why malformed? Wasn't it just a empty
store?! it just<br>
>>> created it.......<br>
>>><br>
>><br>
>> Did you wait for the -z background processes to finish
creating the 50GB<br>
>> of disk allocation before starting the main Squid process
?<br>
>><br>
>> Are your workers trying to serve up traffic to or from
the cache before<br>
>> the rebuild has completed?<br>
>><br>
>><br>
>> As you can see from the log timestamps on startup it will
take ~30-60<br>
>> sec for the rock caches of that size to be loaded in your
system.<br>
>><br>
>><br>
>> Amos<br>
>><br>
>> _______________________________________________<br>
>> squid-users mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> squid-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a></span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br>
iQEcBAEBCAAGBQJWz0ioAAoJENNXIZxhPexGqv0H/iumDpA03D6UDC7Px+Scdrgm
<br>
+u/Bnf7MbXRX4UptkoYZ0WdXfBUgaeGfQvajZRpegktqzdmf+tn85uS+JZ5tjtAN
<br>
/MBQLTFQiYzjiYEma3wH2GrhHdOHGAQytlO6vyP+KJXkj+XEZlKapfDxMe9jfe0P
<br>
PJ/6Q+zy+3LgGT4BnZzBN50YZ42RtQ5eF72W2t6y+XLDs6behYf2xqrtq0CGiOY8
<br>
KwtE3SsN601VAgbd4eZqbZT0tp8DO8/qAWHqnsu2goiTkjIyrBHWXO8Rx4fm9DCt
<br>
rUwuqzOncu/mWMXVrNlZdPSp39T05u3Wdi/eQU4E0F1OppPBMVp3+OrBIEvcHLE=
<br>
=LI6z
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>