Hi
I recently had some software troubles crashed Dolphin big time and decided to upgraded the laptop (Aptosid 2010-03) to correct the issues that where occurring. I tried to re-establish my old approx setup and have an unusual case of thickness over coming me and I am here to ask for another set of eyes to look at my creation
First
etc/hosts
127.0.0.1 debian-main-proxy
127.0.0.1 aptosid-alt-proxy
127.0.0.1 aptosid-main-proxy
127.0.0.1 debian-multimedia-proxy
127.0.0.1 sogo-main-proxy

Next
/etc/apt/sources.list
# Unstable
deb debian-main-proxy:9999/debian-main unstable main contrib non-free
#deb-src debian-main-proxy:9999/debian-main unstable main contrib non-free

# Testing
#deb debian-main-proxy:9999/debian-main testing main contrib non-free
#deb-src debian-main-proxy:9999/debian-main testing main contrib non-free


# Aptosid Sources
deb aptosid-alt-proxy:9999/aptosid-alt sid main fix.main
deb aptosid-main-proxy:9999/aptosid-main sid main fix.main
# deb-src aptosid-main-proxy:9999/aptosid-main sid main fix.main

#SoGo Sources
deb sogo-main-proxy:9999/sogo-main/debian squeeze squeeze

# multimedia
deb debian-multimedia-proxy:9999/debian-multimedia sid main non-free

Third
/etc/approx/approx.conf

#debian ftp.debian.org/debian
#security security.debian.org/debian-security
#volatile volatile.debian.org/debian-volatile

debian-main ftp.uk.debian.org/debian

# an alternate Aptosid repo, should go first for Aptosid users
aptosid-alt ftp://ftp.spline.de/pub/aptosid/debian/
# the primary repo
aptosid-main aptosid.com/debian

debian-multimedia www.debian-multimedia.org

sogo-main inverse.ca/

# The following are the default parameter values, so there is
# no need to uncomment them unless you want a different value.
# See approx.conf(5) for details.

#$cache /var/cache/approx
#$max_rate unlimited
#$max_redirects 5
#$user approx
#$group approx
#$syslog daemon
#$pdiffs true
#$offline false
#$max_wait 10
#$verbose false
#$debug false

Next
update-inetd --enable approx

And I get
Err debian-main-proxy unstable Release.gpg
Connection failed
Err aptosid-alt-proxy sid Release.gpg
Connection failed
Err aptosid-main-proxy sid Release.gpg
Connection failed
Err debian-multimedia-proxy sid Release.gpg
Connection failed
Err sogo-main-proxy squeeze Release.gpg
Connection failed
Hit liquorix.net sid Release.gpg
Ign liquorix.net/debian/ sid/main Translation-en
Err debian-main-proxy/debian-main/ unstable/contrib Translation-en
Connection failed
Err aptosid-alt-proxy/aptosid-alt/ sid/fix.main Translation-en
Connection failed
Err aptosid-main-proxy/aptosid-main/ sid/fix.main Translation-en
Connection failed
Err sogo-main-proxy/sogo-main/debian/ squeeze/squeeze Translation-en
Connection failed
Err debian-multimedia-proxy/debian-multimedia/ sid/main Translation-en
Connection failed
Err aptosid-alt-proxy/aptosid-alt/ sid/fix.main Translation-en_US
Connection failed

So what have I done wrong?
When I do a direct connection it works fine.
# apt-cache policy approx
approx:
Installed: 4.5-1
Candidate: 4.5-1
Version table:
*** 4.5-1 0
100 /var/lib/dpkg/status

The link
There's a fine setup how-to for approx that should get you on your way.
in your manual no longer points to the site you had intended.

I have looked at the man pages for approx and approx.conf. More computer geek. Descriptive maybe, helpful - not to me

I see trying to use code boxes are another speciality I have not mastered and the "http://" has turned into [links]. interesting

Thanks
Geordie
Back to top

did you restart inetd?



That's the step I always forget, and that's the error you are getting.

By the way, you can make a space separated list in /etc/hosts, no need for one item per line for local host.

If you are using other machines on the network as well, then of course their /etc/hosts have to point to the main approx server's IP address in /etc/hosts

that's the only thing I can think of that might be going wrong, i know I always forget to restart networking and then approx doesn't work.

I don't remember doing that update-inetd step by the way.
Back to top

Hi I am back

This time when I ran into trouble, I tried reading the man pages. In etc/hosts it says
This file is a simple text file that associates IP addresses with
hostnames, one line per IP address. For each host a single line should be present with the following information:
I took it literally and the results show it did not help
I tried /etc/init.d/approx restart
And it did not work
Next
update-inetd --enable approx
This came from an archived Aptosid manual. Approx is not longer in the current manual. Maybe they were on to something
And then
# service networking restart
service networking restart
Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces ... (warning).
Reconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit www.isc.org/software/dhcp/
and
apt-get update
Err aptosid-alt-proxy sid Release.gpg
Connection failed
Err debian-main-proxy unstable Release.gpg
Connection failed
Err sogo-main-proxy squeeze Release.gpg
Connection failed
Err aptosid-main-proxy sid Release.gpg
Connection failed
Err debian-multimedia-proxy sid Release.gpg
Connection failed
Hit liquorix.net sid Release.gpg
I have restarted the computer several with the same results.
Also /var/cache/approx was not generated in this install.
I feeling a little depreciated.
The joys of being on the bleeding edge. I guess it is borked in sid.
Maybe I should try apt-cacher-ng?
Thanks for looking
Geordie
Back to top

no, approx works fine in sid.

There's something making it not start right, that's all.

Do: ps aux | grep approx
and see if it shows it running.
Back to top

ps aux | grep approx
root 5001 0.0 0.0 5048 720 pts/1 S+ 08:13 0:00 grep approx
Could I have a port conflict?
Geordie
Back to top

try this:

service openbsd-inetd restart

then:
apt-get update

approx doesn't appear as running service because it is run by another daemon, it's not networking sorry, I think it's openbsd-inetd

Then let me know.

The other steps you took may have messed up something because they are not actually required.

If you don't have openbsd-inetd installed that's the problem.

Almost all the approx online directions show: /etc/init.d/approx as present, but that is not the case with new approx in sid.

Sorry I forgot this, this always bites me too when I forget.

I of course also hope it goes without saying that you are not running any type of software firewall on the approx box... if you are of course you'd need to allow port 9999 incoming.
Back to top

I use approx with squeeze, no problems. Your configs are not like mine.

Here, /etc/hosts looks like this (only one approx line which I call deb-proxy):



custom lines in my /etc/approx/approx.conf:



and my sources.list (note each entry has deb-proxy:9999)



I put a backslash before each http hoping it displays properly rather than as "link". The backslash does not go in the config!

Somewhere on techpatterns site is a really good approx tutorial which helped me enormously. and there is an smxi proxy "switcher" function

You might need a reboot to get it going.
Back to top

Good Day
I did as suggested
service openbsd-inetd restart
Restarting internet superserver: inetd.
apt-get update
Err debian-main-proxy unstable Release.gpg
Connection failed

apt-cache policy openbsd-inetd
openbsd-inetd:
Installed: 0.20080125-6
Candidate: 0.20080125-6
Version table:
*** 0.20080125-6 0
100 /var/lib/dpkg/status
ps aux | grep approx
root 23897 0.0 0.0 5048 720 pts/1 S+ 10:34 0:00 grep approx
I have tried removing and reinstalling approx, but I an achieving the same results.
I am under the impression that something has really mucked things up. i.e. IBM (idiot behind the machine)
I really thank you for your assistance on this, but I am not sure were to go other than reinstalling the complete operating system.
Thanks
Geordie
Back to top

Both approx and openbsd-inetd are the same in squeeze and sid. They work.

In your /etc/hosts (as well as showing multiple lines for approx), I don't see localhost and your hostname in there as well, like in mine
Back to top

Hi dzz
etc/hosts
127.0.0.1 localhost localhost.localdomain
127.0.0.1 SatelliteA40
127.0.0.1 debian-main-proxy
127.0.0.1 aptosid-alt-proxy
127.0.0.1 aptosid-main-proxy
127.0.0.1 debian-multimedia-proxy
127.0.0.1 sogo-main-proxy


I used this as a guide
"http://smxi.org/docs/smxi-manual.htm"
Geordie
Back to top