Thanks Amos for pointing me the right direction. BR Farooq -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: Wednesday, May 28, 2014 2:02 PM To: squid-users@xxxxxxxxxxxxxxx Subject: Re: store.cc crashing the squid child On 28/05/2014 8:46 p.m., Farooq Bhatti wrote: > Hi there, > > I am looking forward for your help, please. > > Further I tried to get the access log on the same time and I found this: > > Tue May 27 06:33:20 2014 0 TCP_MISS/503 3797 POST > http://xdz.no-ip.org:9091/is-ready - HIER_DIRECT/0.0.0.0 text/html It would be worth your while enabling the to_localhost access checks. Look for the below line in squid.conf and remove the #: #http_access deny to_localhost You can maybe also configure the DNS resolver used by Squid not to return 0.0.0.0 as an IP address. It is invalid. > > > And the Store.cc line 915 is saying this > > /* Append incoming data from a primary server to an entry. */ void > StoreEntry::append(char const *buf, int len) { > assert(mem_obj != NULL); > assert(len >= 0); > assert(store_status == STORE_PENDING); > Yes What the developers will need is to know what store_status actually contains, since it is clearly not the value STORE_PENDING. http://wiki.squid-cache.org/SquidFaq/BugReporting has details. Note also how the top of the page starts with the location of where to send bug reports (squid-users is not the right place, particularly if this is a security vulnerability). Amos --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
