Public bug reported:
If you want to bind an instance of squid-deb-proxy to a specific IP,
setting something like
http_port 10.1.1.50:8000
in the config file, the announced avahi port is set to "10.1.1.50:8000"
in /etc/avahi/services/squid-deb-proxy.service instead of "8000" leading
to an error during execution of apt-avahi-discover.
error: uncaptured python exception, closing channel <AptAvahiClient>
('10.1.1.50', 10): 9223372036854775807 (<class 'socket.error'>:[Errno
111] Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
The port announced via avahi is 10 where no service is listening.
As a workaround i changed the port extraction in /usr/share/squid-deb-
proxy/init-common.sh to handle http_port settings including an IP
address:
PORT=$(grep http_port /etc/squid-deb-proxy/squid-deb-proxy.conf|cut -d'
' -f2|cut -d':' -f1 --complement)
** Affects: squid-deb-proxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696092
Title:
squid-deb-proxy announces wrong port if http_port includes an IP
address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1696092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
