Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
approx in debian 12
132 views
Skip to first unread message
Russell L. Harris
Nov 15, 2023, 8:50:06 PM11/15/23
to
I installed approx in a Debian 12 system, but when I attempt to
restart it the error message appears "Unit approx.service not loaded."
The approx man page (dated May 2011) says that approx is invoked by
inetd, but I think that in Debian 12 approx is invoked by systemctl or
systemd.
synaptic indicates that systemctl is available, but not installed.
RLH
restart it the error message appears "Unit approx.service not loaded."
The approx man page (dated May 2011) says that approx is invoked by
inetd, but I think that in Debian 12 approx is invoked by systemctl or
systemd.
synaptic indicates that systemctl is available, but not installed.
RLH
Charles Curley
Nov 15, 2023, 9:50:06 PM11/15/23
to
On Thu, 16 Nov 2023 01:39:32 +0000
"Russell L. Harris" <rus...@rlharris.org> wrote:
> I installed approx in a Debian 12 system, but when I attempt to
> restart it the error message appears "Unit approx.service not loaded."
Please show us a complete copy and paste of the transaction, from the
"Russell L. Harris" <rus...@rlharris.org> wrote:
> I installed approx in a Debian 12 system, but when I attempt to
> restart it the error message appears "Unit approx.service not loaded."
initial prompt and the command you entered, through to the following
prompt, inclusive.
Then, similarly for "systemctl status approx".
You may need to run "systemctl daemon-reload".
>
> The approx man page (dated May 2011) says that approx is invoked by
> inetd, but I think that in Debian 12 approx is invoked by systemctl or
> systemd.
systemd. systemctl is a user tool for managing systemd.
>
> synaptic indicates that systemctl is available, but not installed.
systemctl package conflicts with systemd. The systemctl package says, in
part,
Description: daemonless "systemctl" command to manage services
without systemd "systemctl" is a replacement command to control
system daemons without systemd. "systemctl" is useful in
application containers where systemd is not available to start/stop
services.
So if you have systemd installed, you don't want the systemctl package.
>
> RLH
>
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Russell L. Harris
Nov 15, 2023, 11:20:05 PM11/15/23
to
On Wed, Nov 15, 2023 at 07:41:03PM -0700, Charles Curley wrote:
>On Thu, 16 Nov 2023 01:39:32 +0000
>"Russell L. Harris" <rus...@rlharris.org> wrote:
>
>> I installed approx in a Debian 12 system, but when I attempt to
>> restart it the error message appears "Unit approx.service not loaded."
>
>Please show us a complete copy and paste of the transaction, from the
>initial prompt and the command you entered, through to the following
>prompt, inclusive.
>
>Then, similarly for "systemctl status approx".
>
>You may need to run "systemctl daemon-reload".
>
root@mollydew:/home/rlh# systemctl daemon-reload
>On Thu, 16 Nov 2023 01:39:32 +0000
>"Russell L. Harris" <rus...@rlharris.org> wrote:
>
>> I installed approx in a Debian 12 system, but when I attempt to
>> restart it the error message appears "Unit approx.service not loaded."
>
>Please show us a complete copy and paste of the transaction, from the
>initial prompt and the command you entered, through to the following
>prompt, inclusive.
>
>Then, similarly for "systemctl status approx".
>
>You may need to run "systemctl daemon-reload".
>
root@mollydew:/home/rlh# systemctl restart approx
Failed to restart approx.service: Unit approx.service not found.
root@mollydew:/home/rlh# systemctl status approx
Unit approx.service could not be found.
root@mollydew:/home/rlh#
Charles Curley
Nov 16, 2023, 12:20:06 AM11/16/23
to
On Thu, 16 Nov 2023 04:11:37 +0000
"Russell L. Harris" <rus...@rlharris.org> wrote:
> root@mollydew:/home/rlh# systemctl daemon-reload
> root@mollydew:/home/rlh# systemctl restart approx
> Failed to restart approx.service: Unit approx.service not found.
> root@mollydew:/home/rlh# systemctl status approx
> Unit approx.service could not be found.
> root@mollydew:/home/rlh#
Well, that's weird. I installed approx on a Debian 12 machine, and got
"Russell L. Harris" <rus...@rlharris.org> wrote:
> root@mollydew:/home/rlh# systemctl daemon-reload
> root@mollydew:/home/rlh# systemctl restart approx
> Failed to restart approx.service: Unit approx.service not found.
> root@mollydew:/home/rlh# systemctl status approx
> Unit approx.service could not be found.
> root@mollydew:/home/rlh#
the same results you did. However:
root@tsalmoth:~# ll /lib/systemd/system/approx*
-rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service'
-rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket
root@tsalmoth:~# systemctl status approx.service
Unit approx.service could not be found.
root@tsalmoth:~# systemctl status approx.socket
● approx.socket - caching proxy server for Debian archive files
Loaded: loaded (/lib/systemd/system/approx.socket; enabled; preset: enabled)
Active: active (listening) since Wed 2023-11-15 21:48:27 MST; 1min 47s ago
Docs: man:approx(8)
Listen: [::]:9999 (Stream)
Accepted: 0; Connected: 0;
Tasks: 0 (limit: 4469)
Memory: 8.0K
CPU: 642us
CGroup: /system.slice/approx.socket
Nov 15 21:48:27 tsalmoth systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
root@tsalmoth:~#
So it seems to be running.
I made a minimal effort get get it to work with no success. You may
have better luck than I.
One thing I didn't like is that approx appears to require fiddling with
sources.list. apt-cacher-ng simply requires setting a proxy value, in
its own file in /etc/apt/apt.conf.d. E.g.:
root@hawk:/etc/apt/apt.conf.d# cat /etc/apt/apt.conf.d/02proxy
Acquire::http::Proxy "http://aptcacher.localdomain:3142";
root@hawk:/etc/apt/apt.conf.d#
Charles Curley
Nov 16, 2023, 12:30:06 AM11/16/23
to
On Wed, 15 Nov 2023 22:18:09 -0700
Charles Curley <charle...@charlescurley.com> wrote:
> One thing I didn't like is that approx appears to require fiddling
> with sources.list. apt-cacher-ng simply requires setting a proxy
> value, in its own file in /etc/apt/apt.conf.d. E.g.:
>
> root@hawk:/etc/apt/apt.conf.d# cat /etc/apt/apt.conf.d/02proxy
> Acquire::http::Proxy "http://aptcacher.localdomain:3142";
> root@hawk:/etc/apt/apt.conf.d#
Or, even simpler, install auto-apt-proxy on your clients and let them
Charles Curley <charle...@charlescurley.com> wrote:
> One thing I didn't like is that approx appears to require fiddling
> with sources.list. apt-cacher-ng simply requires setting a proxy
> value, in its own file in /etc/apt/apt.conf.d. E.g.:
>
> root@hawk:/etc/apt/apt.conf.d# cat /etc/apt/apt.conf.d/02proxy
> Acquire::http::Proxy "http://aptcacher.localdomain:3142";
> root@hawk:/etc/apt/apt.conf.d#
find your proxy. The package description says it works for approx. And
that worked!
Russell L. Harris
Nov 16, 2023, 12:50:06 AM11/16/23
to
on it until tomorrow evening. However, can auto-apt-proxy be
specified during mirror selection with a netinstall? That is my
primary need and use for approx.
A friend gave me his old Windows XP machine. I installed on it Debian
12 with XFCE desktop. I intend to use it to replace an old machine on
which is installed Debian 9, running a mail server (getmail) and an
approx server.
RLH
Anssi Saari
Nov 16, 2023, 12:50:06 AM11/16/23
to
"Russell L. Harris" <rus...@rlharris.org> writes:
> root@mollydew:/home/rlh# systemctl daemon-reload
> root@mollydew:/home/rlh# systemctl restart approx
> Failed to restart approx.service: Unit approx.service not found.
> root@mollydew:/home/rlh# systemctl status approx
> Unit approx.service could not be found.
> root@mollydew:/home/rlh#
Looks like there's a cron job and a socket for it in the package. So are
> root@mollydew:/home/rlh# systemctl daemon-reload
> root@mollydew:/home/rlh# systemctl restart approx
> Failed to restart approx.service: Unit approx.service not found.
> root@mollydew:/home/rlh# systemctl status approx
> Unit approx.service could not be found.
> root@mollydew:/home/rlh#
you sure you're even supposed to run it as a service? They do include an
approx@.service so you could run it as whichever user you want but it
makes me think that's not the idea here.
Maybe the documents in /usr/share/doc/approx give more information about
the intended usage. I've only taken a quick peek at the file list.
Charles Curley
Nov 16, 2023, 1:00:07 AM11/16/23
to
On Thu, 16 Nov 2023 05:42:57 +0000
should be able to specify the approx server during the installation (or
preseed it). That will result in a "Acquire::http::Proxy" line in
/etc/apt/apt.conf similar to what I showed you earlier.
> That is my
> primary need and use for approx.
>
> A friend gave me his old Windows XP machine. I installed on it Debian
> 12 with XFCE desktop. I intend to use it to replace an old machine on
> which is installed Debian 9, running a mail server (getmail) and an
> approx server.
Do you really need approx if you have only the one machine?
> Thanks for checking, Charles. My schedule does not allow me to work
> on it until tomorrow evening. However, can auto-apt-proxy be
> specified during mirror selection with a netinstall?
That I do not know. But the default port for approx is 9999 so you
> on it until tomorrow evening. However, can auto-apt-proxy be
> specified during mirror selection with a netinstall?
should be able to specify the approx server during the installation (or
preseed it). That will result in a "Acquire::http::Proxy" line in
/etc/apt/apt.conf similar to what I showed you earlier.
> That is my
> primary need and use for approx.
>
> A friend gave me his old Windows XP machine. I installed on it Debian
> 12 with XFCE desktop. I intend to use it to replace an old machine on
> which is installed Debian 9, running a mail server (getmail) and an
> approx server.
Kamil Jońca
Nov 16, 2023, 1:10:06 AM11/16/23
to
Charles Curley <charle...@charlescurley.com> writes:
> On Thu, 16 Nov 2023 04:11:37 +0000
(ie. service which can have multiple instances)
KJ
> On Thu, 16 Nov 2023 04:11:37 +0000
>> root@mollydew:/home/rlh# systemctl daemon-reload
>> root@mollydew:/home/rlh# systemctl restart approx
>> Failed to restart approx.service: Unit approx.service not found.
>> root@mollydew:/home/rlh# systemctl status approx
>> Unit approx.service could not be found.
>> root@mollydew:/home/rlh#
>
>> root@mollydew:/home/rlh# systemctl restart approx
>> Failed to restart approx.service: Unit approx.service not found.
>> root@mollydew:/home/rlh# systemctl status approx
>> Unit approx.service could not be found.
>> root@mollydew:/home/rlh#
>
> Well, that's weird. I installed approx on a Debian 12 machine, and got
> the same results you did. However:
>
> root@tsalmoth:~# ll /lib/systemd/system/approx*
> -rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service'
> -rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket
> root@tsalmoth:~# systemctl status approx.service
> the same results you did. However:
>
> root@tsalmoth:~# ll /lib/systemd/system/approx*
> -rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service'
> -rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket
> root@tsalmoth:~# systemctl status approx.service
> Unit approx.service could not be found.
But here I cannot see approx.service, only approx@.service
(ie. service which can have multiple instances)
KJ
Russell L. Harris
Nov 16, 2023, 1:20:06 AM11/16/23
to
On Wed, Nov 15, 2023 at 10:55:51PM -0700, Charles Curley wrote:
>Do you really need approx if you have only the one machine?
I install Debian for friends. They are amazed at how fast their old
>Do you really need approx if you have only the one machine?
Windows machines run with Debian. And approx has been a time saver
for me.
In the network mirror configuration step, all I have to type in is:
192.168.1.40:9999
I have not touched the approx server for a couple of years.
RLH
Russell L. Harris
Nov 16, 2023, 1:30:07 AM11/16/23
to
I have not touched the approx server (running Debian 9) for a couple
of years or more. It "just runs". I have used the server without
change to the configuration files for netinstalls since Debian 8 or 9,
and the latest was to install Debian 12.
In the mirror selection of netinstall, I only have to type in the host
ip address and port: "192.168.1.40:9999".
RLH
Kamil Jońca
Nov 16, 2023, 1:40:07 AM11/16/23
to
Kamil Jońca <kjo...@o2.pl> writes:
> Charles Curley <charle...@charlescurley.com> writes:
>
>> On Thu, 16 Nov 2023 04:11:37 +0000
>> "Russell L. Harris" <rus...@rlharris.org> wrote:
>>
> Charles Curley <charle...@charlescurley.com> writes:
>
>> On Thu, 16 Nov 2023 04:11:37 +0000
>> "Russell L. Harris" <rus...@rlharris.org> wrote:
>>
>>> root@mollydew:/home/rlh# systemctl daemon-reload
>>> root@mollydew:/home/rlh# systemctl restart approx
>>> Failed to restart approx.service: Unit approx.service not found.
>>> root@mollydew:/home/rlh# systemctl status approx
>>> Unit approx.service could not be found.
>>> root@mollydew:/home/rlh#
>>
>>> root@mollydew:/home/rlh# systemctl restart approx
>>> Failed to restart approx.service: Unit approx.service not found.
>>> root@mollydew:/home/rlh# systemctl status approx
>>> Unit approx.service could not be found.
>>> root@mollydew:/home/rlh#
>>
>> Well, that's weird. I installed approx on a Debian 12 machine, and got
>> the same results you did. However:
>>
>> root@tsalmoth:~# ll /lib/systemd/system/approx*
>> -rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service'
>> -rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket
>> root@tsalmoth:~# systemctl status approx.service
>> the same results you did. However:
>>
>> root@tsalmoth:~# ll /lib/systemd/system/approx*
>> -rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service'
>> -rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket
>> root@tsalmoth:~# systemctl status approx.service
>> Unit approx.service could not be found.
>
>
> But here I cannot see approx.service, only approx@.service
> (ie. service which can have multiple instances)
What if you issue:
> (ie. service which can have multiple instances)
systemctl status "approx@*.service"
KJ
Russell L. Harris
Nov 16, 2023, 2:10:06 AM11/16/23
to
But I am in not in familiar territory.
RLH
Reco
Nov 16, 2023, 5:30:06 AM11/16/23
to
Hi.
On Thu, Nov 16, 2023 at 07:02:39AM +0000, Russell L. Harris wrote:
> On Thu, Nov 16, 2023 at 07:14:04AM +0100, Kamil Jo?ca wrote:
> > Kamil Jo?ca <kjo...@o2.pl> writes:
> >
> > > Charles Curley <charle...@charlescurley.com> writes:
> > >
> > > > On Thu, 16 Nov 2023 04:11:37 +0000
> > > > "Russell L. Harris" <rus...@rlharris.org> wrote:
> > > >
> > > > > root@mollydew:/home/rlh# systemctl daemon-reload
> > > > > root@mollydew:/home/rlh# systemctl restart approx
> > > > > Failed to restart approx.service: Unit approx.service not found.
> > > > > root@mollydew:/home/rlh# systemctl status approx
> > > > > Unit approx.service could not be found.
It's expected, see below.
> > What if you issue:
> > systemctl status "approx@*.service"
>
> It appears to run; no error message is produced, but no output, either.
>
> But I am in not in familiar territory.
What you have is approx.socket unit, which causes systemd to listen on
tcp:9999.
On each incoming connection
"approx@<local-ip>:<local-port>-<remote-ip>:<remote-port>.service" is
started. That service is only used to serve that particular connection,
and is terminated after.
Thus, there's nothing to restart. You just edit /etc/approx/approx.conf,
and try your changes immediately.
Reco
On Thu, Nov 16, 2023 at 07:02:39AM +0000, Russell L. Harris wrote:
> On Thu, Nov 16, 2023 at 07:14:04AM +0100, Kamil Jo?ca wrote:
> > Kamil Jo?ca <kjo...@o2.pl> writes:
> >
> > > Charles Curley <charle...@charlescurley.com> writes:
> > >
> > > > On Thu, 16 Nov 2023 04:11:37 +0000
> > > > "Russell L. Harris" <rus...@rlharris.org> wrote:
> > > >
> > > > > root@mollydew:/home/rlh# systemctl daemon-reload
> > > > > root@mollydew:/home/rlh# systemctl restart approx
> > > > > Failed to restart approx.service: Unit approx.service not found.
> > > > > root@mollydew:/home/rlh# systemctl status approx
> > > > > Unit approx.service could not be found.
> > What if you issue:
> > systemctl status "approx@*.service"
>
> It appears to run; no error message is produced, but no output, either.
>
> But I am in not in familiar territory.
tcp:9999.
On each incoming connection
"approx@<local-ip>:<local-port>-<remote-ip>:<remote-port>.service" is
started. That service is only used to serve that particular connection,
and is terminated after.
Thus, there's nothing to restart. You just edit /etc/approx/approx.conf,
and try your changes immediately.
Reco
David
Nov 16, 2023, 6:40:06 AM11/16/23
to
systemd unit named neither 'approx' nor 'approx.service'.
systemd assumes '.service' for unit names that dont have any
type specified, see 'man 1 systemd'.
The name of the systemd unit is 'approx.socket'. So you need to use
that complete name all commands. If you put that complete name in
the above commands, then they will have a chance to succeed.
Examples:
[root@kablamm ~]# systemctl list-sockets | grep -E 'LISTEN|approx' -
LISTEN UNIT ACTIVATES
[::]:9999 approx.socket -
[root@kablamm ~]# systemctl status approx.socket
● approx.socket - caching proxy server for Debian archive files
Loaded: loaded (/lib/systemd/system/approx.socket; enabled;
vendor preset: enabled)
Loaded: loaded (/lib/systemd/system/approx.socket; enabled;
Active: active (listening) since Thu 2023-11-16 22:20:21 AEDT; 11min ago
Docs: man:approx(8)
Listen: [::]:9999 (Stream)
Accepted: 0; Connected: 0;
Tasks: 0 (limit: 19049)
Listen: [::]:9999 (Stream)
Accepted: 0; Connected: 0;
Memory: 4.0K
CPU: 780us
CGroup: /system.slice/approx.socket
Nov 16 22:20:21 kablamm systemd[1]: Listening on caching proxy server
for Debian archive files.
[root@kablamm ~]# cat /lib/systemd/system/approx.socket
[Unit]
Description=caching proxy server for Debian archive files
Documentation=man:approx(8)
[Socket]
ListenStream=9999
Accept=yes
[Install]
WantedBy=sockets.target
Charles Curley
Nov 16, 2023, 12:30:08 PM11/16/23
to
On Thu, 16 Nov 2023 06:53:16 +0100
Kamil Jońca <kjo...@o2.pl> wrote:
> Charles Curley <charle...@charlescurley.com> writes:
>
> [...]
> [...]
On my test machine, while approx is enabled, I have no instances
actually running, which leads me to think that systemd launches an
instance of approx when a client knocks on its port, much like inetd.
And that could easily lead to multiple instances.
Kamil Jońca <kjo...@o2.pl> wrote:
> Charles Curley <charle...@charlescurley.com> writes:
>
> [...]
> [...]
> >
> > Well, that's weird. I installed approx on a Debian 12 machine, and
> > got the same results you did. However:
> >
> > root@tsalmoth:~# ll /lib/systemd/system/approx*
> > -rw-r--r-- 1 root root 165 Feb 12 2023
> > '/lib/systemd/system/approx@.service' -rw-r--r-- 1 root root 167
> > Feb 12 2023 /lib/systemd/system/approx.socket root@tsalmoth:~#
> > systemctl status approx.service Unit approx.service could not be
> > found.
>
> But here I cannot see approx.service, only approx@.service
> (ie. service which can have multiple instances)
Multiple instances, eh? That's a part of systemd I know nothing about.
> > Well, that's weird. I installed approx on a Debian 12 machine, and
> > got the same results you did. However:
> >
> > root@tsalmoth:~# ll /lib/systemd/system/approx*
> > -rw-r--r-- 1 root root 165 Feb 12 2023
> > '/lib/systemd/system/approx@.service' -rw-r--r-- 1 root root 167
> > Feb 12 2023 /lib/systemd/system/approx.socket root@tsalmoth:~#
> > systemctl status approx.service Unit approx.service could not be
> > found.
>
> But here I cannot see approx.service, only approx@.service
> (ie. service which can have multiple instances)
On my test machine, while approx is enabled, I have no instances
actually running, which leads me to think that systemd launches an
instance of approx when a client knocks on its port, much like inetd.
And that could easily lead to multiple instances.
Greg Wooledge
Nov 16, 2023, 1:10:07 PM11/16/23
to
On Thu, Nov 16, 2023 at 10:26:48AM -0700, Charles Curley wrote:
> Multiple instances, eh? That's a part of systemd I know nothing about.
> On my test machine, while approx is enabled, I have no instances
> actually running, which leads me to think that systemd launches an
> instance of approx when a client knocks on its port, much like inetd.
> And that could easily lead to multiple instances.
Yes. That's precisely what "socket activation" is -- an inetd-like
> Multiple instances, eh? That's a part of systemd I know nothing about.
> On my test machine, while approx is enabled, I have no instances
> actually running, which leads me to think that systemd launches an
> instance of approx when a client knocks on its port, much like inetd.
> And that could easily lead to multiple instances.
feature built into systemd.
Russell L. Harris
Nov 17, 2023, 1:00:06 AM11/17/23
to
On Thu, Nov 16, 2023 at 01:08:50PM +0300, Reco wrote:
>What you have is approx.socket unit, which causes systemd to listen on
>tcp:9999.
>On each incoming connection
>"approx@<local-ip>:<local-port>-<remote-ip>:<remote-port>.service" is
>started. That service is only used to serve that particular connection,
>and is terminated after.
>
>Thus, there's nothing to restart. You just edit /etc/approx/approx.conf,
>and try your changes immediately.
I am trying to do another netinstall of Debian 12 on a Lenovo G570
>What you have is approx.socket unit, which causes systemd to listen on
>tcp:9999.
>On each incoming connection
>"approx@<local-ip>:<local-port>-<remote-ip>:<remote-port>.service" is
>started. That service is only used to serve that particular connection,
>and is terminated after.
>
>Thus, there's nothing to restart. You just edit /etc/approx/approx.conf,
>and try your changes immediately.
laptop.
Both the target machine (192.168.1.25) and the approx server
(192.168.1.30) are in my LAN. The approx server is a fresh install of
Debian 12.
The approx.conf file has only two lines uncommented (should I add "us"?):
debian http://fpt.debian.org/debian
security http://security.debian.org/debian-security
In netinstall, under CONFIGURE THE PACKAGE MANAGER, I have specified
the debian archive mirror hostname:
192.168.1.30:9999
and debian archive mirror directory:
/debian/
Scanning the archive mirror produces the "red screen of death" BAD
ARCHIVE MIRROR. Virtual console 4 says: "WARNING **: mirror does not
support the specified release"
RLH
Reco
Nov 17, 2023, 1:30:06 AM11/17/23
to
Hi.
On Fri, Nov 17, 2023 at 05:54:45AM +0000, Russell L. Harris wrote:
> Both the target machine (192.168.1.25) and the approx server
> (192.168.1.30) are in my LAN. The approx server is a fresh install of
> Debian 12.
>
> The approx.conf file has only two lines uncommented (should I add "us"?):
>
> debian http://fpt.debian.org/debian
Is this a typo? It should be (ftp, not fpt)
debian http://ftp.debian.org/debian
> Scanning the archive mirror produces the "red screen of death" BAD
> ARCHIVE MIRROR. Virtual console 4 says: "WARNING **: mirror does not
> support the specified release"
"journalctl | grep approx" on approx server should show something that's
related to the problem.
Reco
On Fri, Nov 17, 2023 at 05:54:45AM +0000, Russell L. Harris wrote:
> Both the target machine (192.168.1.25) and the approx server
> (192.168.1.30) are in my LAN. The approx server is a fresh install of
> Debian 12.
>
> The approx.conf file has only two lines uncommented (should I add "us"?):
>
> debian http://fpt.debian.org/debian
debian http://ftp.debian.org/debian
> Scanning the archive mirror produces the "red screen of death" BAD
> ARCHIVE MIRROR. Virtual console 4 says: "WARNING **: mirror does not
> support the specified release"
related to the problem.
Reco
Russell L. Harris
Nov 17, 2023, 1:50:07 AM11/17/23
to
Yes; a typo.
>"journalctl | grep approx" on approx server should show something that's
>related to the problem.
root@mollydew:/home/rlh# journalctl | grep approx
Nov 14 07:54:27 mollydew groupadd[4819]: group added to /etc/group: name=approx, GID=120
Nov 14 07:54:27 mollydew groupadd[4819]: group added to /etc/gshadow: name=approx
Nov 14 07:54:27 mollydew groupadd[4819]: new group: name=approx, GID=120
Nov 14 07:54:28 mollydew useradd[4825]: new user: name=approx, UID=111, GID=120, home=/var/cache/approx, shell=/usr/sbin/nologin, from=none
Nov 14 07:54:29 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 14 07:56:48 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 14 07:56:48 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 14 18:45:29 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 15 08:24:34 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 15 08:24:34 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 15 21:27:22 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 16 00:40:56 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 16 00:40:56 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 16 00:42:30 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 16 07:19:45 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 16 07:19:45 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 17 01:43:36 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 17 04:47:32 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 17 04:47:32 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 17 04:49:05 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
root@mollydew:/home/rlh#
>"journalctl | grep approx" on approx server should show something that's
>related to the problem.
Nov 14 07:54:27 mollydew groupadd[4819]: group added to /etc/group: name=approx, GID=120
Nov 14 07:54:27 mollydew groupadd[4819]: group added to /etc/gshadow: name=approx
Nov 14 07:54:27 mollydew groupadd[4819]: new group: name=approx, GID=120
Nov 14 07:54:28 mollydew useradd[4825]: new user: name=approx, UID=111, GID=120, home=/var/cache/approx, shell=/usr/sbin/nologin, from=none
Nov 14 07:54:29 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 14 07:56:48 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 14 07:56:48 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 14 18:45:29 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 15 08:24:34 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 15 08:24:34 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 15 21:27:22 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 16 00:40:56 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 16 00:40:56 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 16 00:42:30 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 16 07:19:45 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 16 07:19:45 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 17 01:43:36 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
Nov 17 04:47:32 mollydew systemd[1]: approx.socket: Deactivated successfully.
Nov 17 04:47:32 mollydew systemd[1]: Closed approx.socket - caching proxy server for Debian archive files.
Nov 17 04:49:05 mollydew systemd[1]: Listening on approx.socket - caching proxy server for Debian archive files.
root@mollydew:/home/rlh#
Reco
Nov 17, 2023, 2:20:06 AM11/17/23
to
On Fri, Nov 17, 2023 at 06:48:37AM +0000, Russell L. Harris wrote:
> > > debian http://fpt.debian.org/debian
> >
> > Is this a typo? It should be (ftp, not fpt)
> Yes; a typo.
OK. And what happens if you execute this on a approx server:
> > > debian http://fpt.debian.org/debian
> >
> > Is this a typo? It should be (ftp, not fpt)
> Yes; a typo.
curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
Reco
Russell L. Harris
Nov 17, 2023, 2:30:07 AM11/17/23
to
On Fri, Nov 17, 2023 at 09:56:07AM +0300, Reco wrote:
>OK. And what happens if you execute this on a approx server:
>
>curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
root@mollydew:/etc/approx# curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
>OK. And what happens if you execute this on a approx server:
>
>curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 127.0.0.1:9999...
* Connected to localhost (127.0.0.1) port 9999 (#0)
> GET http://ftp.debian.org/debian/dists/stable/Release HTTP/1.1
> Host: ftp.debian.org
> User-Agent: curl/7.88.1
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 OK
< Content-Type: text/plain
< Last-Modified: Sat, 07 Oct 2023 09:30:02 GMT
< Content-Length: 149228
< Date: Fri, 17 Nov 2023 07:21:42 GMT
< Server: approx/5.12 Ocamlnet/
<
{ [4096 bytes data]
100 145k 100 145k 0 0 193k 0 --:--:-- --:--:-- --:--:-- 193k
* Connection #0 to host localhost left intact
root@mollydew:/etc/approx#
Reco
Nov 17, 2023, 3:00:07 AM11/17/23
to
On Fri, Nov 17, 2023 at 07:25:23AM +0000, Russell L. Harris wrote:
> On Fri, Nov 17, 2023 at 09:56:07AM +0300, Reco wrote:
> > OK. And what happens if you execute this on a approx server:
> >
> > curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
>
> root@mollydew:/etc/approx# curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 127.0.0.1:9999...
> * Connected to localhost (127.0.0.1) port 9999 (#0)
> > GET http://ftp.debian.org/debian/dists/stable/Release HTTP/1.1
> > Host: ftp.debian.org
> > User-Agent: curl/7.88.1
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 200 OK
Looks good. What about this one:
> On Fri, Nov 17, 2023 at 09:56:07AM +0300, Reco wrote:
> > OK. And what happens if you execute this on a approx server:
> >
> > curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
>
> root@mollydew:/etc/approx# curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 127.0.0.1:9999...
> * Connected to localhost (127.0.0.1) port 9999 (#0)
> > GET http://ftp.debian.org/debian/dists/stable/Release HTTP/1.1
> > Host: ftp.debian.org
> > User-Agent: curl/7.88.1
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 200 OK
apt update -o Acquire::http::Proxy=http://localhost:9999
Reco
Russell L. Harris
Nov 17, 2023, 3:10:06 AM11/17/23
to
On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:
>Looks good. What about this one:
>
>apt update -o Acquire::http::Proxy=http://localhost:9999
root@mollydew:/etc/approx# apt update -o Acquire::http::Proxy=http://localhost:9999
>Looks good. What about this one:
>
>apt update -o Acquire::http::Proxy=http://localhost:9999
Ign:1 http://security.debian.org/debian-security bookworm-security InRelease
Err:2 http://security.debian.org/debian-security bookworm-security Release
404 Not Found [IP: ::1 9999]
Hit:3 http://192.168.1.40:9999/debian bookworm InRelease
Get:4 http://192.168.1.40:9999/debian bookworm-updates InRelease [52.1 kB]
Reading package lists... Done
E: The repository 'http://security.debian.org/debian-security bookworm-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@mollydew:/etc/approx#
Reco
Nov 17, 2023, 4:20:07 AM11/17/23
to
Hi.
On Fri, Nov 17, 2023 at 08:03:15AM +0000, Russell L. Harris wrote:
> On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:
> > Looks good. What about this one:
> >
> > apt update -o Acquire::http::Proxy=http://localhost:9999
>
> root@mollydew:/etc/approx# apt update -o Acquire::http::Proxy=http://localhost:9999
> Ign:1 http://security.debian.org/debian-security bookworm-security InRelease
Hm. I have this in my approx.conf for debian-security:
debian-security http://deb.debian.org/debian-security
Try changing it, I guess.
Reco
On Fri, Nov 17, 2023 at 08:03:15AM +0000, Russell L. Harris wrote:
> On Fri, Nov 17, 2023 at 10:34:14AM +0300, Reco wrote:
> > Looks good. What about this one:
> >
> > apt update -o Acquire::http::Proxy=http://localhost:9999
>
> root@mollydew:/etc/approx# apt update -o Acquire::http::Proxy=http://localhost:9999
> Ign:1 http://security.debian.org/debian-security bookworm-security InRelease
debian-security http://deb.debian.org/debian-security
Try changing it, I guess.
Reco
Russell L. Harris
Nov 17, 2023, 12:20:05 PM11/17/23
to
Should we report an error regarding the approx man page which states:
USEAGE
approx is invoked by inetd(8)
RLH
Greg Wooledge
Nov 17, 2023, 2:10:07 PM11/17/23
to
On Fri, Nov 17, 2023 at 05:18:02PM +0000, Russell L. Harris wrote:
> Should we report an error regarding the approx man page which states:
>
> USEAGE
> approx is invoked by inetd(8)
I assume you're looking at the approx(8) man page as shown
> Should we report an error regarding the approx man page which states:
>
> USEAGE
> approx is invoked by inetd(8)
here: <https://manpages.debian.org/bookworm/approx/approx.8.en.html>
This is upstream's man page, dated May 2011. It's clearly not going
to be *literally* true on every system, as there are plenty of
alternatives to inetd (xinetd, systemd, and so on). One may read it
as meaning "inetd or something which fulfills the same role".
I would not bother filing any cosmetic bug reports against a 12-year-old
upstream man page.
Russell L. Harris
Nov 17, 2023, 3:30:07 PM11/17/23
to
On Fri, Nov 17, 2023 at 02:02:10PM -0500, Greg Wooledge wrote:
>On Fri, Nov 17, 2023 at 05:18:02PM +0000, Russell L. Harris wrote:
>> Should we report an error regarding the approx man page which states:
>
>On Fri, Nov 17, 2023 at 05:18:02PM +0000, Russell L. Harris wrote:
>> Should we report an error regarding the approx man page which states:
>
>I would not bother filing any cosmetic bug reports against a 12-year-old
>upstream man page.
Agreed on that point. But I suspect that the maintainer is going to
>upstream man page.
become involved to get approx working in Debian-12.
I searched for "Debian approx apt-cache" and found several users of
apt-cache and apt-cache-ng who reported the packages buggy and
several who expressed appreciation for the stability of approx.
Whatever release of approx I have running on the Debian-9 machine
works flawlessly, but I do hope to upgrade the Debian version on that
machine. I suppose I could reinstall on my planned replacement, and
see whether approx still works with Debian-11, or go back to
Debian-10, if necessary.
RLH
Andrew M.A. Cater
Nov 18, 2023, 5:50:07 AM11/18/23
to
On Fri, Nov 17, 2023 at 08:28:51PM +0000, Russell L. Harris wrote:
> On Fri, Nov 17, 2023 at 02:02:10PM -0500, Greg Wooledge wrote:
> > On Fri, Nov 17, 2023 at 05:18:02PM +0000, Russell L. Harris wrote:
> > > Should we report an error regarding the approx man page which states:
> >
>
> On Fri, Nov 17, 2023 at 02:02:10PM -0500, Greg Wooledge wrote:
> > On Fri, Nov 17, 2023 at 05:18:02PM +0000, Russell L. Harris wrote:
> > > Should we report an error regarding the approx man page which states:
> >
>
> Whatever release of approx I have running on the Debian-9 machine
> works flawlessly, but I do hope to upgrade the Debian version on that
> machine. I suppose I could reinstall on my planned replacement, and
> see whether approx still works with Debian-11, or go back to
> Debian-10, if necessary.
>
Just on this: please _don't_ go backwards in release version unless this
> works flawlessly, but I do hope to upgrade the Debian version on that
> machine. I suppose I could reinstall on my planned replacement, and
> see whether approx still works with Debian-11, or go back to
> Debian-10, if necessary.
>
is an isolated machine that's never going to connect to anything else -
Debian _should_ improve with each version and certainly there are
security updates and bug fixes with each point release.
Debian 9 is out of main security support and even out of LTS - https://wiki.debian.org/LTS .
In order to update that, you'd need to update to 10 then 11, then 12.
Potentially, build a replacement machine with 12 and work on it, then
perhaps decommission the 9 and reformat to 12?
All the very best, as ever,
Andy Cater
> RLH
>
0 new messages