[squid-users] kid1| WARNING: 1 swapin MD5 mismatches 3.5

2015-06-16 Thread Tory M Blue
So appears I have some corruption? I can hit this server with tests just
fine, but if I put it into production I get these errors.


I've got no debug statements active, so this has me a bit concerned


Tory


2015/06/16 15:26:08 kid1| WARNING: 1 swapin MD5 mismatches

2015/06/16 15:26:08 kid1| Could not parse headers from on disk object

2015/06/16 15:26:08 kid1| BUG 3279: HTTP reply without Date:

2015/06/16 15:26:08 kid1| StoreEntry-key: 5993A2A07D185EA408F308BB6F4664C9

2015/06/16 15:26:08 kid1| StoreEntry-next: 0x1c603fd8

2015/06/16 15:26:08 kid1| StoreEntry-mem_obj: 0x2d72b00

2015/06/16 15:26:08 kid1| StoreEntry-timestamp: -1

2015/06/16 15:26:08 kid1| StoreEntry-lastref: 1434493568

2015/06/16 15:26:08 kid1| StoreEntry-expires: -1

2015/06/16 15:26:08 kid1| StoreEntry-lastmod: -1

2015/06/16 15:26:08 kid1| StoreEntry-swap_file_sz: 0

2015/06/16 15:26:08 kid1| StoreEntry-refcount: 1

2015/06/16 15:26:08 kid1| StoreEntry-flags: PRIVATE,FWD_HDR_WAIT,VALIDATED

2015/06/16 15:26:08 kid1| StoreEntry-swap_dirn: -1

2015/06/16 15:26:08 kid1| StoreEntry-swap_filen: -1

2015/06/16 15:26:08 kid1| StoreEntry-lock_count: 2

2015/06/16 15:26:08 kid1| StoreEntry-mem_status: 0

2015/06/16 15:26:08 kid1| StoreEntry-ping_status: 2

2015/06/16 15:26:08 kid1| StoreEntry-store_status: 1

2015/06/16 15:26:08 kid1| StoreEntry-swap_status: 0

2015/06/16 15:26:12 kid1| Could not parse headers from on disk object

2015/06/16 15:26:12 kid1| BUG 3279: HTTP reply without Date:

2015/06/16 15:26:12 kid1| StoreEntry-key: 98378018F7E195D8DF490B34598A6E84

2015/06/16 15:26:12 kid1| StoreEntry-next: 0x1d1a6d98

2015/06/16 15:26:12 kid1| StoreEntry-mem_obj: 0x1d6e40e0

2015/06/16 15:26:12 kid1| StoreEntry-timestamp: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastref: 1434493572

2015/06/16 15:26:12 kid1| StoreEntry-expires: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastmod: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_file_sz: 0

2015/06/16 15:26:12 kid1| StoreEntry-refcount: 1

2015/06/16 15:26:12 kid1| StoreEntry-flags: PRIVATE,FWD_HDR_WAIT,VALIDATED

2015/06/16 15:26:12 kid1| StoreEntry-swap_dirn: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_filen: -1

2015/06/16 15:26:12 kid1| StoreEntry-lock_count: 2

2015/06/16 15:26:12 kid1| StoreEntry-mem_status: 0

2015/06/16 15:26:12 kid1| StoreEntry-ping_status: 2

2015/06/16 15:26:12 kid1| StoreEntry-store_status: 1

2015/06/16 15:26:12 kid1| StoreEntry-swap_status: 0

2015/06/16 15:26:12 kid1| Could not parse headers from on disk object

2015/06/16 15:26:12 kid1| BUG 3279: HTTP reply without Date:

2015/06/16 15:26:12 kid1| StoreEntry-key: D952451B47EF10EC480C043FD63BFB6D

2015/06/16 15:26:12 kid1| StoreEntry-next: 0x1c8b1c58

2015/06/16 15:26:12 kid1| StoreEntry-mem_obj: 0x1d6feff0

2015/06/16 15:26:12 kid1| StoreEntry-timestamp: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastref: 1434493572

2015/06/16 15:26:12 kid1| StoreEntry-expires: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastmod: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_file_sz: 0

2015/06/16 15:26:12 kid1| StoreEntry-refcount: 1

2015/06/16 15:26:12 kid1| StoreEntry-flags: PRIVATE,FWD_HDR_WAIT,VALIDATED

2015/06/16 15:26:12 kid1| StoreEntry-swap_dirn: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_filen: -1

2015/06/16 15:26:12 kid1| StoreEntry-lock_count: 2

2015/06/16 15:26:12 kid1| StoreEntry-mem_status: 0

2015/06/16 15:26:12 kid1| StoreEntry-ping_status: 2

2015/06/16 15:26:12 kid1| StoreEntry-store_status: 1

2015/06/16 15:26:12 kid1| StoreEntry-swap_status: 0

2015/06/16 15:26:12 kid1| Could not parse headers from on disk object

2015/06/16 15:26:12 kid1| BUG 3279: HTTP reply without Date:

2015/06/16 15:26:12 kid1| StoreEntry-key: C44DA9C9F8CC73F64D37EDA4FC074FE3

2015/06/16 15:26:12 kid1| StoreEntry-next: 0x1ad1a4f8

2015/06/16 15:26:12 kid1| StoreEntry-mem_obj: 0x1d6feff0

2015/06/16 15:26:12 kid1| StoreEntry-timestamp: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastref: 1434493572

2015/06/16 15:26:12 kid1| StoreEntry-expires: -1

2015/06/16 15:26:12 kid1| StoreEntry-lastmod: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_file_sz: 0

2015/06/16 15:26:12 kid1| StoreEntry-refcount: 1

2015/06/16 15:26:12 kid1| StoreEntry-flags: PRIVATE,FWD_HDR_WAIT,VALIDATED

2015/06/16 15:26:12 kid1| StoreEntry-swap_dirn: -1

2015/06/16 15:26:12 kid1| StoreEntry-swap_filen: -1

2015/06/16 15:26:12 kid1| StoreEntry-lock_count: 2

2015/06/16 15:26:12 kid1| StoreEntry-mem_status: 0

2015/06/16 15:26:12 kid1| StoreEntry-ping_status: 2

2015/06/16 15:26:12 kid1| StoreEntry-store_status: 1

2015/06/16 15:26:12 kid1| StoreEntry-swap_status: 0

2015/06/16 15:26:12 kid1| assertion failed: store.cc:1885: isEmpty()
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] kid1| WARNING: 1 swapin MD5 mismatches 3.5

2015-06-16 Thread Amos Jeffries
On 17/06/2015 10:28 a.m., Tory M Blue wrote:
 So appears I have some corruption? I can hit this server with tests just
 fine, but if I put it into production I get these errors.
 
 
 I've got no debug statements active, so this has me a bit concerned
 

This is almost always seen as a result of a previous crash which left
some object in the cache in a corrupted (incomplete write) state.

If you can track down which object it was and erase it (or drop the
whole cache and restart). It should disappear.

Although any assistance you are able to give in tracking down what the
root cause of that assert isEmpty() is would be welcome. So far we are
all unable to .

Amos

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] kid1| WARNING: 1 swapin MD5 mismatches 3.5

2015-06-16 Thread Tory M Blue
On Tue, Jun 16, 2015 at 4:29 PM, Amos Jeffries squ...@treenet.co.nz wrote:

 On 17/06/2015 10:28 a.m., Tory M Blue wrote:
  So appears I have some corruption? I can hit this server with tests just
  fine, but if I put it into production I get these errors.
 
 
  I've got no debug statements active, so this has me a bit concerned
 

 This is almost always seen as a result of a previous crash which left
 some object in the cache in a corrupted (incomplete write) state.

 If you can track down which object it was and erase it (or drop the
 whole cache and restart). It should disappear.

 Although any assistance you are able to give in tracking down what the
 root cause of that assert isEmpty() is would be welcome. So far we are
 all unable to .

 Amos

 ___
 squid-users mailing list
 squid-users@lists.squid-cache.org
 http://lists.squid-cache.org/listinfo/squid-users


Well I can run with 2 caches in prod without an issue, so if I can help
with debug or something on this box in the weird state, i'll be more than
happy too.

I believe the issue was i disabled ipv6 while squid was running and it hard
a hard time with that, so I stopped restarted, same error as soon as
traffic came in. I then moved my cache data to local disk (it runs in
memory), and rebooted , restored the data and same error (just wanted to
make sure squid was clean).

So let me know if I can help you track that down.

Tory
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users