Hi,
Squid restarted in a production environment with below error:
2012/07/11 09:28:25| FATAL: dying from an unhandled exception: virginConsumed
<= offset && offset <= end
2012/07/11 09:28:32| Starting Squid Cache version 3.1.19 for
sparc-sun-solaris2.10...
Is this a known issue for this releas
On 12.07.2012 12:37, Jack Black wrote:
I just tried the same squid configuration on Ubuntu Mini remix 11.04
x64, and Ubuntu Desktop 12.04 x64 live (I didn't even bother
installing it). They both work perfectly, just like CentOS. Whatever
the problem is, it appears to be specific to Ubuntu 12.04 S
Turns our I just needed the
never_direct allow all
in the right spot of course.
Cheers,
Ben
> well the answer is you other mail + the squid.conf
>
> "Without the cache_peer I can not get to any sties at all. All
> internet (well, http and https) traffic on our network must go through
> the paren
I just tried the same squid configuration on Ubuntu Mini remix 11.04
x64, and Ubuntu Desktop 12.04 x64 live (I didn't even bother
installing it). They both work perfectly, just like CentOS. Whatever
the problem is, it appears to be specific to Ubuntu 12.04 Server
edition for some reason, which just
On 7/12/2012 1:21 AM, Crawford, Ben wrote:
As requested, a more detailed squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl localnet src 10.161.128.0/20
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl
Sorry for double reply, sent that last one out a bit quicker than I should have.
On 12 July 2012 04:25, Eliezer Croitoru wrote:
> two things:
> post a more detailed squid.conf to see if there is something wrong there.
>
> i am using squid3.1.19 and 3.2.16-17 and it works like for many others.
> t
As requested, a more detailed squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl localnet src 10.161.128.0/20
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_p
I have made a video that proves that this is not just a case of some
other program getting the splash page, but it was too big for the
mailing lists, so I uploaded it here:
http://dxgameunit.webs.com/squid.ogv
What it basically shows is:
a) squid running in a CentOS VM, and access.log messages a
two things:
post a more detailed squid.conf to see if there is something wrong there.
i am using squid3.1.19 and 3.2.16-17 and it works like for many others.
this problem can be an issue about routing and not related to squid at all.
a 504 code is:
10.5.5 504 Gateway Timeout
The server, while a
On 11/07/2012 9:08 p.m., ml ml wrote:
Hello,
okay, this actually works:
acl DENY_ACCESS http_status 403
access_log /tmp/squid.deny.log squid DENY_ACCESS
Okay, but how can i now Debug which acl rule caused TCP_DENIED/403?
I only want to set my debug_options for the TCP_DENIED/403 requests...
See this:
http://wiki.squid-cache.org/KnowledgeBase/DebugSections
So you could use, for example:
debug_options ALL,2 28,4 82,4
That would log at level 4 for of access control and external acl
related things and level 2 for the rest.
On Wed, Jul 11, 2012 at 6:08 PM, ml ml wrote:
> Hello,
>
> oka
Hi All,
I have run into a problem with not being able to access a few specific
things on the web when running through our local proxy.
Some details:
* The current setup is a Linux box running squid 3.1.19.
* This is being run behind a pfsense box that is load balancing our
two internet connection
Hello,
okay, this actually works:
acl DENY_ACCESS http_status 403
access_log /tmp/squid.deny.log squid DENY_ACCESS
Okay, but how can i now Debug which acl rule caused TCP_DENIED/403?
I only want to set my debug_options for the TCP_DENIED/403 requests...
Thanks,
Mario
13 matches
Mail list logo
