Re: [Apt-proxy-users] Connection failed all of a sudden

[Jay S. <me...@he...>]

I apologize for the "hellllooooo" comment.  I didn't realize my original 
post was on a weekend, and it wasn't the timing.

I do not have a /var/log/apt-proxy.log file

when I try to connect I get a bunch of these in my /var/log/daemon.log file:

Jul 11 22:39:31 localhost apt-proxy[2554]: connect from 192.168.5.26 
(192.168.5.26)
Jul 11 22:39:31 localhost apt-proxy[2556]: connect from 192.168.5.26 
(192.168.5.26)
Jul 11 22:39:31 localhost apt-proxy[2558]: connect from 192.168.5.26 
(192.168.5.26)
Jul 11 22:39:31 localhost apt-proxy[2560]: connect from 192.168.5.26 
(192.168.5.26)
Jul 11 22:39:31 localhost apt-proxy[2562]: connect from 192.168.5.26 
(192.168.5.26)

I did /etc/init.d/inetd restart, but it did not effect the above error. 
  Like I said, it used to work, I changed _NOTHING_ and now it doesn't work

Thanks
Jay


Chris Halls wrote:
> On Mon, Jul 11, 2005 at 12:38:04AM -0500, Jay Strauss wrote:
> 
>>Helloooooo out there, anyone still on this list?
> 
> 
> Yes, but debconf is on this week and I'm not checking all mailing lists
> regularly.
> 
> Please post the output in /var/log/apt-proxy.log.  If there is none, try
> following this advice in the README:
> 
> Q: A connection cannot be established with apt-proxy on a remote machine.
>    Nothing appears in the apt-proxy.log file.
> 
> 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>
> 
>    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.
> 
> If that doesn't help, double check that your inetd really is running.
> 
> Hope that helps
> Chris
> 
>