Re: apt-proxy problem - was -111 connection refused
Chris Halls wrote:
On Tue, Jun 18, 2002 at 01:22:12PM -0700, Paul Scott,,, wrote:
When I run apt-get update on the other machine I get 111 connection refused.
Do I need something in /etc/exports or /etc/hosts.allow?
A quote from the README:
Thanks. I had forgotten about this README since most README's in
/usr/share/doc don't seem to say much.
My first problem was having lines in the client sources.list that didn't
match. Having fixed that I may be here:
Q: A connection cannot be established with apt-proxy on a remote machine.
Nothing appears in the apt-proxy.log file.
This is now the case.
A: apt-proxy is run by tcpd, which may deny connections depending on how it is
set up. If a connection is denied by tcpd, you will find a log message in
/var/log/daemon.log such as:
apt-proxy[nnnn]: refused connect from <hostname>
I am now showing connections in /var/log/daemon.log. I guess that means
the following may not be a problem?
You should check /etc/hosts.allow and hosts.deny. For example, the standard
ALL: PARANOID in /etc/hosts.deny will deny acess to clients whose hostname
cannot be looked up.
I am getting connection timeouts on the client as my last symptom.
Also I am not quite sure about the back_end line for openoffice. Is
this close?
add_backend /openoffice/ \
$APT_PROXY_CACHE/openoffice/ \
ftp vpn-junkies.de::debian-openoffice
Thanks,
Paul
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: