He found the problem and writes ...

I never found why clear cache isn't working, I suspect because I didn't add it 
to my Path instead I called it with ./squid ?

Anyway, I found the cause of the original problem. I was missing the one Remote network range that I needed on the VPN router. You'll notice the 32.0.0.0 range missing. The IP of the new webpage starts with 50. So anything in the 32-64 range would have failed. The users probably blamed any previous failures on the proxy server. I thought since DNS translated the URL to an IP that the router was doing it's job:

should have done a tracer earlier. It is time to get a new router/gateway so that we can retire Squid, it's the systems the users see that get most of the attention ...
Yeah, yeah not to mention retiring the Nortel routers ;-)

Thanks guys,


On 12-02-13 12:24 AM, Gustin Johnson wrote:
If it is in /usr/local/ then it was probably locally built, who knows what flags it was compiled with. Is installing the version from the Debian repository an option here?

On Mon, Feb 13, 2012 at 12:23 AM, Gustin Johnson <gus...@meganerd.ca 
<mailto:gus...@meganerd.ca>> wrote:

    What version of squid and Debian are we talking about?

    On Fri, Feb 10, 2012 at 9:43 PM, caziz <ca...@cuug.ab.ca 
<mailto:ca...@cuug.ab.ca>> wrote:

        A buddy asked ...

            Hi guys,
            This is probably a simple question for someone with a little 
history in Squid. I'm trying to clear cache
            in an old version of Squid. Tried renaming the 
/usr/local/squid/cache directory and 'Squid -z' as well as
            rebooting. Neither prompts a clear or rebuild. The  '-z' parameter 
just seems to be ignored and squid
            seems to just start at the command line with errors usually seen in 
the logs. This version is too old for
            that I suspect. I'm initiating the command (./squid) from 
/usr/local/squid/sbin, the one place I found it.
            This system is almost retired so I've been getting away with just 
re-imaging to solve most problems. But
            that doesn't clear the unexpected 'page not found' the filters are 
causing this time.

            I'm tempted to just disable caching instead, but the instructions I 
found for that probably don't apply
            either ;-)

            Bin to all the usual Squid sites and Debian, not seeing much for 
this version.

            Any help appreciated, one of the branches can't get to the 
company's new website due to this nagging block ;-)

            Thanks,
            Ken


        _______________________________________________
        clug-talk mailing list
        clug-talk@clug.ca <mailto:clug-talk@clug.ca>
        http://clug.ca/mailman/listinfo/clug-talk_clug.ca
        Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
        **Please remove these lines when replying




_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

<<attachment: caziz.vcf>>

_______________________________________________
clug-talk mailing list
clug-talk@clug.ca
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to