Bug 862252 - [PATCH] Squid doesn't reload on VPN up/down, or network down
Summary: [PATCH] Squid doesn't reload on VPN up/down, or network down
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Luscon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-02 13:02 UTC by Matthew Booth
Modified: 2012-12-01 08:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-14 11:34:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fix network manager dispatcher (582 bytes, patch)
2012-10-02 13:02 UTC, Matthew Booth
no flags Details | Diff

Description Matthew Booth 2012-10-02 13:02:52 UTC
Created attachment 620276 [details]
Fix network manager dispatcher

Description of problem:
I use squid to reverse proxy some sites for a local network, some of which are only available over a VPN. If I start squid first, then the VPN, in that order, squid will not be able to access sites over the VPN. However, if I then cause squid to reconfigure it can access sites over the VPN. I assume squid is doing something with DNS caching, but haven't investigated.

I notice squid already has a network manager dispatcher script, but it appears a little unloved. Firstly it still uses /sbin/service. Secondly it only reloads on the "up" event.

The following works for me:

case "$2" in
        up|down|vpn-up|vpn-down)
                /bin/systemctl reload squid.service || :
                ;;
esac

I've attached a patched against rawhide git. This bug is applicable at least to F17, F18 and rawhide.

Version-Release number of selected component (if applicable):
squid-3.2.0.16-1.fc17.x86_64

Comment 1 Michal Luscon 2012-10-03 07:59:05 UTC
Thank you for your report and patch Matthew.

Comment 2 Fedora Update System 2012-10-26 15:15:48 UTC
squid-3.2.3-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc18

Comment 3 Fedora Update System 2012-10-26 19:42:30 UTC
Package squid-3.2.3-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.3-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16962/squid-3.2.3-2.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-11-20 13:18:37 UTC
squid-3.2.3-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc17

Comment 5 Fedora Update System 2012-11-20 15:28:53 UTC
squid-3.2.3-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc16

Comment 6 Fedora Update System 2012-12-01 08:31:36 UTC
squid-3.2.3-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2012-12-01 08:42:56 UTC
squid-3.2.3-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.