privoxy won't start at boot

Bug #1870101 reported by lvm on 2020-04-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
privoxy (Ubuntu)
Undecided
Unassigned

Bug Description

Privoxy fails to bind to network address at boot time with

Fatal error: can't bind to 192.168.1.3:8118: Cannot assign requested address

Subsequent manual start works.

Similar bug #427625 exists but it is marked as fixed - which is obviously not the case, and it also deals with inability to bind to localhost, not to an external host address which is a static address assigned via dhcp, so I am filing a new bug.

5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

privoxy address is configured as 'listen-address 192.168.1.3:8118'

Roland Rosenfeld (roland) wrote :

According to https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ it may be a good idea to change
 After=network.target
in the /lib/systemd/system/privoxy.service to
 After=network-online.target

If you prefer an update safe mechanism, run
 systemctl edit privoxy.service
and write

[Unit]
After.network-online.target

into it.

I'll create an update to the privoxy package to fix this, soon.

Roland Rosenfeld (roland) wrote :

I just uploaded 3.0.28-3, where this should be fixed.

lvm (lvm-royal) wrote :

Yes, adding After=network-online.target to /lib/systemd/system/privoxy.service helped, and it is neater than the workaround I used - waiting until the address becomes available in privoxy.service. Thanks.

Roland Rosenfeld (roland) wrote :

Fix available in 3.0.28-3

Changed in privoxy (Ubuntu):
status: New → Fix Committed
Roland Rosenfeld (roland) wrote :

Fixed in 3.0.28-3 (available since groovy)

Changed in privoxy (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers