Menu

#919 changes in listen-address require restart not just config rewrite

version 3.0.25
closed
None
5
2019-08-26
2019-06-14
No

privoxy does reconfigure itself once the config gets updated, however changes in listen-address (new entries) do not seem to work here

I am running version 3.0.26 and if a append a new listen-address line to the config, the deamon will fail to start listening on that new address, a restart will be required

As far as i tested also removing listen-addresses or chaning existing ones is not applied without a restart.

Related

Bugs: #919

Discussion

  • Fabian Keil

    Fabian Keil - 2019-08-26
    • status: open --> closed
    • assigned_to: Fabian Keil
     
  • Fabian Keil

    Fabian Keil - 2019-08-26

    Thanks for the report.

    I can not reproduce this with Privoxy 3.0.28 (but the relevant code should be the same as in 3.0.26).

    Please reopen if you can reproduce this with a more recent Privoxy version.

     
  • Henning Schild

    Henning Schild - 2019-08-26

    Privoxy 3.0.28 has the same issue. One simple way to reproduce on Linux:

    Put this into your config

    listen-address 127.0.0.1:8118
    listen-address [::1]:8118

    Start privoxy and use netstat to look at where is listens.

    netstat -putan | grep privoxy
    tcp 0 0 127.0.0.1:8118 0.0.0.0: LISTEN 5293/privoxy
    tcp6 0 0 ::1:8118 :::
    LISTEN 5293/privoxy

    Change config and remove the IPv6 entry. This config file change should stop the listen without a restart ... but it does not.
    Similarly adding a new listen-address entry i.e. 192.168.1.10:8118 to listen in a LAN does not apply without a restart.

     
    • Lee

      Lee - 2019-08-26

      On 8/26/19, Henning Schild hensch@users.sourceforge.net wrote:

      Privoxy 3.0.28 has the same issue. One simple way to reproduce on Linux:

      Put this into your config

      listen-address 127.0.0.1:8118
      listen-address [::1]:8118

      Start privoxy and use netstat to look at where is listens.

      netstat -putan | grep privoxy
      tcp 0 0 127.0.0.1:8118 0.0.0.0: LISTEN
      5293/privoxy
      tcp6 0 0 ::1:8118 :::
      LISTEN
      5293/privoxy

      Change config and remove the IPv6 entry. This config file change should stop
      the listen without a restart ... but it does not.
      Similarly adding a new listen-address entry i.e. 192.168.1.10:8118 to listen
      in a LAN does not apply without a restart.

      Where did you get privoxy from, which flavour of linux are you using
      and did you check
      http://config.privoxy.org/show-status
      to make sure privoxy has read the new config file?

      It works for me on windows (which you don't care about - i know) & debian:

      $ sudo netstat -putan | grep privoxy
      [sudo] password for lee:
      tcp 0 0 127.0.0.1:8118 0.0.0.0:*
      LISTEN 421/privoxy

      $ !sudo
      sudo netstat -putan | grep privoxy
      tcp 0 0 127.0.0.1:8118 0.0.0.0:
      LISTEN 421/privoxy
      tcp6 0 0 ::1:8118 :::

      LISTEN 421/privoxy

      $ !sudo
      sudo netstat -putan | grep privoxy
      tcp 0 0 127.0.0.1:8118 0.0.0.0:*
      LISTEN 421/privoxy

      Lee


      ** [bugs:#919] changes in listen-address require restart not just config
      rewrite**

      Status: closed
      Group: version 3.0.25
      Created: Fri Jun 14, 2019 08:30 PM UTC by Henning Schild
      Last Updated: Mon Aug 26, 2019 12:04 PM UTC
      Owner: Fabian Keil

      privoxy does reconfigure itself once the config gets updated, however
      changes in listen-address (new entries) do not seem to work here

      I am running version 3.0.26 and if a append a new listen-address line to the
      config, the deamon will fail to start listening on that new address, a
      restart will be required

      As far as i tested also removing listen-addresses or chaning existing ones
      is not applied without a restart.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/ijbswa/bugs/919/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #919

  • Henning Schild

    Henning Schild - 2019-08-26

    In fact i could not really reproduce it myself now. Still puzzled how i ran into this in the first place. I guess that can stay closed. Thanks!

     
    • Lee

      Lee - 2019-08-26

      On 8/26/19, Henning Schild hensch@users.sourceforge.net wrote:

      In fact i could not really reproduce it myself now. Still puzzled how i ran
      into this in the first place.

      Probably because you didn't force privoxy to re-read the config file
      after it was edited. Even something simple like
      curl --proxy 127.0.0.1:8118 --referer http://p.p/ http://p.p/show-status
      would be enough.

      Lee

      I guess that can stay closed. Thanks!


      ** [bugs:#919] changes in listen-address require restart not just config
      rewrite**

      Status: closed
      Group: version 3.0.25
      Created: Fri Jun 14, 2019 08:30 PM UTC by Henning Schild
      Last Updated: Mon Aug 26, 2019 01:24 PM UTC
      Owner: Fabian Keil

      privoxy does reconfigure itself once the config gets updated, however
      changes in listen-address (new entries) do not seem to work here

      I am running version 3.0.26 and if a append a new listen-address line to the
      config, the deamon will fail to start listening on that new address, a
      restart will be required

      As far as i tested also removing listen-addresses or chaning existing ones
      is not applied without a restart.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/ijbswa/bugs/919/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #919


Log in to post a comment.

MongoDB Logo MongoDB