RE: [squid-users] squid ceasing to function when interface goes down

----------------------------------------
> Date: Sun, 6 Dec 2009 00:27:23 +1300
> From: squid3_at_treenet.co.nz
> To: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] squid ceasing to function when interface goes down
>
> tyler_at_marieval.com wrote:
>> I'm using squid with a parent that's over a VPN. This VPN occasionally
>> times out or goes down; I'm having difficulty deducing which, but
>> theoretically my scripts should reboot it whenever the VPN goes up so I
>> suspect the former.
>>
>> The end result is that my downstream squid occasionally decides to
>> return nothing but 404's ever again until manually restarted. I'm
>> having to watch it like a hawk and can't keep that up all Christmas. If
>> it would just reopen the interface on its own, all would be well. Is
>> there any way to make it deal with this condition gracefully instead of
>> flipping out?
>>
>
> The normal way to handle these things is to use a) reliable network
> connections, or b) multiple interfaces.
>
> What Squid is this?
>
> Things should go back to normal when the interface actually comes back
> up again.

On my debian install, which I am making up as a I go along and so may not
be a robust example of anything, I had a similiar issue and had to use squid -k
to restart. Ihave two interfaces, a LAN card and a wireless card using ndiswrapper
with ipmasq. ( Eventually I want to attach all my local computers in this room
to a router and use the wireless interface to reach WAN via wireless router on cable modem,
giving me just one wireless connection and some way to monitor the packets from all machines and eventually install a wireless modem etc )
In any case, when I boot if I start the browsers before connecting to WLAN it
doesn't work ( duh) but even after connecting I had to restart squid.

>
> If the interface is up, the parent proxy contactable and Squid still
> sending out the error pages you need to take a good look at those error
> pages and see *why* Squid thinks they are still valid. Probably turn
> negative_ttl down to an HTTP compliant 0 seconds as well.

Do you have a faq page or link on how the peering is handled? I stumbled
onto something regarding the config for it, but wasn't clear quite how all
these things work together in a fault tolerant way. Thanks.

>
> Amos
> --
> Please be using
> Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
> Current Beta Squid 3.1.0.15
                                               
_________________________________________________________________
Windows 7: Unclutter your desktop. Learn more.
http://www.microsoft.com/windows/windows-7/videos-tours.aspx?h=7sec&slideid=1&media=aero-shake-7second&listid=1&stop=1&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_7secdemo:122009
Received on Sat Dec 05 2009 - 12:06:28 MST