Apt-Get Update Error (111 Connection Refused)

[TeddyB]

Hello;

I administer multiple computers running Debian Etch for myself and my fience. One of the systems has come up with an error when trying to update apt, it refuses to pull any headers from servers, exiting with the error (111 Connection Refused)

Here is my sources.list file, Though this very same list of sources is working in my other systems

deb http://ftp.debian.org/debian/ etch main contrib non-free
deb-src http://ftp.debian.org/debian/ etch main contrib non-free

deb http://security.debian.org/ etch/updates main contrib non-free
deb-src http://security.debian.org/ etch/updates main contrib non-free

The computer doesn't seem to be haveing any other connection issues, it browses the net, runs samba both client and daemon mode, streams audio from the net, etc. I don't know of any major system changes although my fience is a fiddler and may have unknowingly done something to it.

the last major system modification was resizeing of the hard drives partions. I don't know if apt has functioned since then, but I think we have used it, and I'm certian such things are unrelated.

I don't think she has messed with them, but are their Keyring settings for the main debian repositories? if so That would be my first guess as to why it is malfuntioning...

Thanks;
Teddy B

[TeddyB]

No Fair, Seems like every time I post a question on a forum, I never see a response. Are my problems really that hard?? oh well I tend to find the answers on my own eventually

Anyway, I found that the Keyring for Debian's Official repositories is a package called debian-archive-keyring

I like an idiot Apt-get removed this package hoping I could reinstall it without affecting the rest of the configuration, well since apt is more user friendly as far as dependencies go, it proceeded to remove apt as well given that apt is dependent upon the keyring.

Maybe if I had downloaded the deb itself for the keyring from debian's site. and then dpkg --remove and then dpkg --install that may have worked.

anyway I did manage to reinstall apt via the .deb file and dpkg. Now apt is up again... but still having the same issue with the sources....

I guess it wasn't the keyring.....

Any suggestions would be appreciated. Thanks;
Teddy B

[TeddyB]

ok, I found it, I wasn't paying attention to the entire error apt was posting, It said

Could not connect to localhost:4001 (111 Connection Refused)

When I noticed that it was trying to connect to itself I went looking and found this useful thread on the debian.net's forum

Debian User Forums :: View topic - apt-get: Could not connect to localhost:4001 (127.0.0.1)

It turns out that somewhere in there we triggered Anon-proxy and it was reconfiguring the http_proxy variable (/etc/enviroment) to the following...

# +ANON_MARK+ Don't change this while anon-proxy manages this variable.
# +ANON_MARK+ To take back control of it run dpkg-reconfigure and tell
# +ANON_MARK+ debconf not to set this variable for you.
HTTP_PROXY=http://localhost:4001 # +ANON_MARK+
http_proxy=http://localhost:4001 # +ANON_MARK+

I chose the suggestion to simply reconfigure anon to leave /etc alone

dpkg-reconfigure anon-proxy

I then removed the values set to http_proxy and entered the configuration via grep

As root, just do 'grep -r http_proxy /etc', and as your user yourself, do 'grep -r http_proxy $HOME/.*', that will simply search on both the system-wide config area (/etc) and your user-specific stuff to this setting.

A quick reboot and there you have it.... Problem solved.

There you have it...
TeddyB

[SpiritIsReality]

TeddyB ... thanks