Re: [squid-users] squid-3.5.0.2-20141031-r13657 crashes

2014-12-04 Thread James Harper
> > It's possible that at one point I might have started 2 instances of > > squid running at once... could that cause corruption? > > Yes, very likely. More so the longer they were both running. > > I see you mention segfaults below, that can also cause it for any > objects in use at the time of

Re: [squid-users] 2.7.STABLE9 & Error with option deny_info from local requests

2014-12-04 Thread Mark Riede
That was the fix. I´ve removed the line ' http_access allow localhost'. Thank you. -Ursprüngliche Nachricht- Von: Amos Jeffries [mailto:squ...@treenet.co.nz] Gesendet: Mittwoch, 3. Dezember 2014 16:39 An: Mark Riede; 'squid-users@lists.squid-cache.org' Betreff: Re: AW: [squid-users] 2.7.S

[squid-users] SQUID 3.1.20 TunnelStateData::Connection::error read/write failure: (32) Broken pipe

2014-12-04 Thread LANGLOIS Nicolas
Hi, im using squid On a debian server as simple proxy/cache and sometimes some clients get a connection error, i can't reproduce the problem and don' t really know where it can come from Here is a Squid cache.log output : 2014/12/04 14:46:14| TunnelStateData::Connection::error: FD 232: read/

Re: [squid-users] SQUID 3.1.20 TunnelStateData::Connection::error read/write failure: (32) Broken pipe

2014-12-04 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/12/2014 3:19 a.m., LANGLOIS Nicolas wrote: > Hi, im using squid On a debian server as simple proxy/cache and > sometimes some clients get a connection error, i can't reproduce > the problem and don' t really know where it can come from > > Here

[squid-users] sslcrtvalidator_program

2014-12-04 Thread WorkingMan
Spam detection software, running on the system "master.squid-cache.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content p

[squid-users] Parent proxy login details

2014-12-04 Thread Ivan Brazza
Hi everybody, Currently using squid 2.7 on Windows Server 2008 to forward all requests that come in through our corporate proxy to allow applications that don't support this to access the outside world (essentially doing what cntlm does). Now I was able to get this to work by using cache_peer's lo

Re: [squid-users] Parent proxy login details

2014-12-04 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/12/2014 5:17 a.m., Ivan Brazza wrote: > Hi everybody, > > Currently using squid 2.7 on Windows Server 2008 to forward all > requests that come in through our corporate proxy to allow > applications that don't support this to access the outside wo

[squid-users] odd wccp issue affecting only some web servers

2014-12-04 Thread Jason Haar
Hi there We have CentOS-6 squid-3.1.10-29 servers that are configured for WCCP. They are working - for some web sites. eg "www.slashdot.org" works (216.34.181.48), but "slashdot.org" doesn't (216.34.181.45). Those are both on the same Class-C subnet. What I see is the SYN packet being forwarded f

[squid-users] Squid config question

2014-12-04 Thread JeffDK
Hi, I have domain with about 20 servers. Server A and B need full internet access and ssh access to one offsite server and the rest of the servers (domainX) have internet access limited to about 10 sites. I've added these lines and I beleive the rest is default. acl ServerA src “Server A IP” ac

Re: [squid-users] Squid config question

2014-12-04 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/12/2014 10:17 a.m., JeffDK wrote: > Hi, > > I have domain with about 20 servers. Server A and B need full > internet access and ssh access to one offsite server and the rest > of the servers (domainX) have internet access limited to about 10 > s

Re: [squid-users] odd wccp issue affecting only some web servers

2014-12-04 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/12/2014 6:58 a.m., Jason Haar wrote: > Hi there > > We have CentOS-6 squid-3.1.10-29 servers that are configured for > WCCP. They are working - for some web sites. eg "www.slashdot.org" > works (216.34.181.48), but "slashdot.org" doesn't (216.34.