Menu
▾
▴
apt-proxy-users
|
From: Jay S. <me...@he...> - 2005-07-09 17:34:58
|
Hi, all of a sudden I'm getting connection refused on my apt-proxy
server. I haven't made any changes. As an example of my error, I did
aptitude update on the box with the apt-proxy server running.
Any guidance would be greatly appreciated.
Please note that the host "iron" is IP 192.168.5.26
Thank you
Jay
iron:~# aptitude update
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Err http://192.168.5.26 sarge/main Packages
Connection failed
Err http://192.168.5.26 sarge/main Release
Connection failed
Err http://192.168.5.26 sarge/main Sources
Connection failed
Err http://192.168.5.26 sarge/main Release
Connection failed
Err http://192.168.5.26 sarge/updates/main Packages
Connection failed
Err http://192.168.5.26 sarge/updates/main Release
Connection failed
Err http://192.168.5.26 sarge/updates/contrib Packages
Connection failed
Err http://192.168.5.26 sarge/updates/contrib Release
Connection failed
Err http://192.168.5.26 sarge/updates/non-free Packages
Connection failed
Err http://192.168.5.26 sarge/updates/non-free Release
Connection failed
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Below are my config files:
iron:~# cat /etc/apt/sources.list
deb http://192.168.5.26:9999/debian sarge main
deb-src http://192.168.5.26:9999/debian sarge main
deb http://192.168.5.26:9999/security sarge/updates main contrib non-free
iron:~# cat /etc/apt-proxy/apt-proxy.conf | grep -v -e'^#'
APT_PROXY_CACHE=/var/cache/apt-proxy
add_backend /debian/ \
$APT_PROXY_CACHE/debian/ \
http://ftp.us.debian.org/debian/dists/ \
http://ftp.de.debian.org/debian/ \
http://ftp.uk.debian.org/debian/ \
+ftp.us.debian.org::debian/
add_backend /non-US/ \
$APT_PROXY_CACHE/non-US/ \
http://non-us.debian.org/ \
http://ftp.de.debian.org/debian-non-US/ \
http://ftp.uk.debian.org/debian-non-US/ \
+ftp.de.debian.org::debian-non-US/
add_backend /security/ \
$APT_PROXY_CACHE/security/ \
http://security.debian.org/
add_backend /java/ \
$APT_PROXY_CACHE/java/ \
ftp://ftp.tux.org/java/debian/
CLEANUP_DAYS=14
CLEAN_SWEEP=60
MAX_VERSIONS=2
BACKEND_FREQ=240
RSYNC_TIMEOUT=30
WGET_TIMEOUT=30
iron:~# cat /etc/inetd.conf | grep -v -e'^#'
ident stream tcp wait identd /usr/sbin/identd
identd
swat stream tcp nowait.400 root /usr/sbin/tcpd
/usr/sbin/swat
9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd
/usr/sbin/apt-proxy -l /var/log/apt-proxy.log
rsync stream tcp nowait root /usr/bin/rsync
rsyncd --daemon
|
|
From: Jay S. <me...@he...> - 2005-07-11 05:38:25
|
Helloooooo out there, anyone still on this list? Thanks Jay Jay Strauss wrote: > Hi, all of a sudden I'm getting connection refused on my apt-proxy > server. I haven't made any changes. As an example of my error, I did > aptitude update on the box with the apt-proxy server running. > > Any guidance would be greatly appreciated. > > Please note that the host "iron" is IP 192.168.5.26 > > Thank you > Jay > > iron:~# aptitude update > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > Err http://192.168.5.26 sarge/main Packages > Connection failed > Err http://192.168.5.26 sarge/main Release > Connection failed > Err http://192.168.5.26 sarge/main Sources > Connection failed > Err http://192.168.5.26 sarge/main Release > Connection failed > Err http://192.168.5.26 sarge/updates/main Packages > Connection failed > Err http://192.168.5.26 sarge/updates/main Release > Connection failed > Err http://192.168.5.26 sarge/updates/contrib Packages > Connection failed > Err http://192.168.5.26 sarge/updates/contrib Release > Connection failed > Err http://192.168.5.26 sarge/updates/non-free Packages > Connection failed > Err http://192.168.5.26 sarge/updates/non-free Release > Connection failed > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > > > Below are my config files: > > iron:~# cat /etc/apt/sources.list > deb http://192.168.5.26:9999/debian sarge main > deb-src http://192.168.5.26:9999/debian sarge main > deb http://192.168.5.26:9999/security sarge/updates main contrib non-free > > iron:~# cat /etc/apt-proxy/apt-proxy.conf | grep -v -e'^#' > > APT_PROXY_CACHE=/var/cache/apt-proxy > > add_backend /debian/ \ > $APT_PROXY_CACHE/debian/ \ > http://ftp.us.debian.org/debian/dists/ \ > http://ftp.de.debian.org/debian/ \ > http://ftp.uk.debian.org/debian/ \ > +ftp.us.debian.org::debian/ > > > add_backend /non-US/ \ > $APT_PROXY_CACHE/non-US/ \ > http://non-us.debian.org/ \ > http://ftp.de.debian.org/debian-non-US/ \ > http://ftp.uk.debian.org/debian-non-US/ \ > +ftp.de.debian.org::debian-non-US/ > > > add_backend /security/ \ > $APT_PROXY_CACHE/security/ \ > http://security.debian.org/ > > > add_backend /java/ \ > $APT_PROXY_CACHE/java/ \ > ftp://ftp.tux.org/java/debian/ > > CLEANUP_DAYS=14 > CLEAN_SWEEP=60 > MAX_VERSIONS=2 > BACKEND_FREQ=240 > RSYNC_TIMEOUT=30 > WGET_TIMEOUT=30 > > iron:~# cat /etc/inetd.conf | grep -v -e'^#' > > ident stream tcp wait identd /usr/sbin/identd identd > > swat stream tcp nowait.400 root /usr/sbin/tcpd > /usr/sbin/swat > 9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd > /usr/sbin/apt-proxy -l /var/log/apt-proxy.log > > rsync stream tcp nowait root /usr/bin/rsync > rsyncd --daemon > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by > HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Apt-proxy-users mailing list > Apt...@li... > https://lists.sourceforge.net/lists/listinfo/apt-proxy-users > > > |
|
From: Chris H. <ha...@de...> - 2005-07-12 00:18:00
|
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
|
|
From: Jay S. <me...@he...> - 2005-07-12 03:45:22
|
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 > > |
|
From: Chris H. <ha...@de...> - 2005-07-12 08:30:21
|
On Mon, Jul 11, 2005 at 10:45:05PM -0500, Jay Strauss wrote: > I do not have a /var/log/apt-proxy.log file That is a problem. apt-proxy does not run with enough priviledges to create a file in /var/log, so this file must always be present. It is created in apt-proxy's postinst and rotated by logrotate. You need to recreate it touch /var/log/apt-proxy.log chown aptproxy:adm /var/log/apt-proxy.log > 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 Great, that shows the problem I quoted hasn't occured for you. > > 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 Well the log file doesn't delete itself for no reason. If something stops working, its usually a reasonable assumption to guess that something changed, even if you didn't change it deliberately yourself. e.g. a file got deleted, you ran out of disk space, a configuration file got corrupted etc. Chris |
|
From: Jay S. <me...@he...> - 2005-07-12 10:25:50
|
Chris Halls wrote: > On Mon, Jul 11, 2005 at 10:45:05PM -0500, Jay Strauss wrote: > >>I do not have a /var/log/apt-proxy.log file > > > That is a problem. apt-proxy does not run with enough priviledges to > create a file in /var/log, so this file must always be present. It is > created in apt-proxy's postinst and rotated by logrotate. You need to > recreate it > > touch /var/log/apt-proxy.log > chown aptproxy:adm /var/log/apt-proxy.log Bingo, that was the problem. It's all working now. Is there something I should do to prevent this in the future? Or is this such a nothing that I should just fix it as needed? Thanks again Jay |
|
From: Chris H. <ha...@de...> - 2005-07-13 19:12:13
|
On Tue, Jul 12, 2005 at 05:25:28AM -0500, Jay Strauss wrote: > Chris Halls wrote: > >touch /var/log/apt-proxy.log > >chown aptproxy:adm /var/log/apt-proxy.log > > Bingo, that was the problem. It's all working now. Is there something > I should do to prevent this in the future? Or is this such a nothing > that I should just fix it as needed? Well, you wouldn't normally expect files in /var/log to be deleted instead of rotated. Whatever happened must be specific to your system. The logrotate script is configured to rotate the logfile once a week so it would have corrected itself eventually. > Thanks again You're welcome Chris |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X