[Bug 1041606] New: Privoxy needs to be restarted after every boot when using wlan

newer
[Bug 1191585] Peculiar audacity...

older
[Bug 1190982] GRUB2: "extent not...

bugzilla_noreply＠novell.com

30 May 2017 30 May '17

09:05

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 Bug ID: 1041606 Summary: Privoxy needs to be restarted after every boot when using wlan Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: siebertjonathan@aim.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After installing privoxy and enabling the privoxy.service in systemd, the service is automatically started at boot but when only a wlan connection is setup by NetworkManager, privoxy needs to be restarted once before it can be used (verified in Firefox only, so far). This is similar to #977944 but in this case I do not get any error messages in journalctl about privoxy entering 'failed' state. Also `systemctl status privoxy.service` shows that privoxy is up and running. When a wired connection is present at boot, everything works nicely, even if the wired connection is removed and one switches to wlan. The necessity to restart the privoxy service makes using privoxy as a daemon rather painful. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 2.8 KB)

Show replies by date

bugzilla_noreply＠novell.com

30 May 30 May

09:18

New subject: [Bug 1041606] Privoxy needs to be restarted after every boot when using wlan

bugzilla_noreply＠novell.com

21 Jun 21 Jun

10:51

New subject: [Bug 1041606] Privoxy needs to be restarted after every boot when using wlan

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 http://bugzilla.opensuse.org/show_bug.cgi?id=1041606#c3 Hyde Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hydejoe5@gmail.com Version|Leap 42.3 |Leap 15.0 --- Comment #3 from Hyde Zhou --- Same problem in Leap 15.0 -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:18

New subject: [Bug 1041606] Privoxy needs to be restarted after every boot when using wlan

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 http://bugzilla.opensuse.org/show_bug.cgi?id=1041606#c4 --- Comment #4 from Hyde Zhou --- The problem is related to files '/usr/lib/systemd/system/privoxy.service' and '/etc/NetworkManager/dispatcher.d/privoxyd' Leap 42.3 and Leap 15.0 have same 'privoxy.service' and 'privoxyd' ## /usr/lib/systemd/system/privoxy.service ''' [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target [Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target ''' According to the file 'privoxy.service', a copy of 'resolv.conf' is created before privoxy starts, and privoxy uses the copy instead of '/etc/resolv.conf'. ## /etc/NetworkManager/dispatcher.d/privoxyd ''' case "$2" in up) /usr/bin/systemctl restart privoxy ;; down) /usr/bin/systemctl restart privoxy ;; *) exit 0 ;; esac ''' According to the file 'privoxyd', privoxy will be reloaded either a connection is up or down. The point is, if privoxy starts when the system's network is still offline, the copy from '/etc/resolv.conf' contains no nameserver. In this situation, later connection changes will only cause privoxy reload, and the copy of '/etc/resolv.conf' still contains no nameserver. Thus, 503(URL Cannot be resolved) happened. ## Solution My temporary solution is to modify the file 'privoxyd', changing '/usr/bin/systemctl reload privoxy' into '/usr/bin/systemctl restart privoxy' The solution may not be perfect but it at least works. If there is any confusing expression, please let me know. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14 Aug 14 Aug

11:42

New subject: [Bug 1041606] Privoxy needs to be restarted after every boot when using wlan

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 http://bugzilla.opensuse.org/show_bug.cgi?id=1041606#c5 --- Comment #5 from Hyde Zhou --- (In reply to Hyde Zhou from comment #4)

...

The problem is related to files '/usr/lib/systemd/system/privoxy.service' and '/etc/NetworkManager/dispatcher.d/privoxyd'

Leap 42.3 and Leap 15.0 have same 'privoxy.service' and 'privoxyd'

## /usr/lib/systemd/system/privoxy.service ''' [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target

[Service] Type=forking PIDFile=/run/privoxy.pid ExecStartPre=-/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ ExecStartPre=-/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config ExecReload=/bin/kill -HUP $MAINPID

[Install] WantedBy=multi-user.target '''

According to the file 'privoxy.service', a copy of 'resolv.conf' is created before privoxy starts, and privoxy uses the copy instead of '/etc/resolv.conf'.

## /etc/NetworkManager/dispatcher.d/privoxyd ''' case "$2" in up) /usr/bin/systemctl restart privoxy ;; down) /usr/bin/systemctl restart privoxy ;; *) exit 0 ;; esac '''

According to the file 'privoxyd', privoxy will be reloaded either a connection is up or down.

The point is, if privoxy starts when the system's network is still offline, the copy from '/etc/resolv.conf' contains no nameserver. In this situation, later connection changes will only cause privoxy reload, and the copy of '/etc/resolv.conf' still contains no nameserver. Thus, 503(URL Cannot be resolved) happened.

## Solution

My temporary solution is to modify the file 'privoxyd', changing

'/usr/bin/systemctl reload privoxy' into

'/usr/bin/systemctl restart privoxy'

The solution may not be perfect but it at least works.

If there is any confusing expression, please let me know.

Sorry for the misleading comment, the original file '/etc/NetworkManager/dispatcher.d/privoxyd' is ''' case "$2" in up) /usr/bin/systemctl reload privoxy ;; down) /usr/bin/systemctl reload privoxy ;; *) exit 0 ;; esac ''' And I fix the bug by modifying it into ''' case "$2" in up) /usr/bin/systemctl restart privoxy ;; down) /usr/bin/systemctl restart privoxy ;; *) exit 0 ;; esac ''' -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠suse.com

16 Oct 16 Oct

08:08

New subject: [Bug 1041606] Privoxy needs to be restarted after every boot when using wlan

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 http://bugzilla.opensuse.org/show_bug.cgi?id=1041606#c7 Peter Chambers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter@peterchambers.me.uk --- Comment #7 from Peter Chambers --- This issue and the work-around are observed to be the same in 15.3. Without the work-around manually doing "rcprivoxy restart" is required at the su CLI. With it that is no longer necessary. -- You are receiving this mail because: You are on the CC list for the bug.

991

Age (days ago)

2591

Last active (days ago)

List overview

Download

5 comments

2 participants

participants (2)

bugzilla_noreply＠novell.com
bugzilla_noreply＠suse.com