Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #263579 > unrolled thread

Re: approx in debian 12

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: approx in debian 12 Kamil Jońca <kjonca@o2.pl> - 2023-11-16 07:40 +0100
    Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-16 08:10 +0100
      Re: approx in debian 12 Reco <recoverym4n@enotuniq.net> - 2023-11-16 11:30 +0100
        Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 07:00 +0100
          Re: approx in debian 12 Reco <recoverym4n@enotuniq.net> - 2023-11-17 07:30 +0100
            Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 07:50 +0100
              Re: approx in debian 12 Reco <recoverym4n@enotuniq.net> - 2023-11-17 08:20 +0100
                Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 08:30 +0100
                  Re: approx in debian 12 Reco <recoverym4n@enotuniq.net> - 2023-11-17 09:00 +0100
                    Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 09:10 +0100
                      Re: approx in debian 12 Reco <recoverym4n@enotuniq.net> - 2023-11-17 10:20 +0100
                        Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 18:20 +0100
                          Re: approx in debian 12 Greg Wooledge <greg@wooledge.org> - 2023-11-17 20:10 +0100
                            Re: approx in debian 12 "Russell L. Harris" <russell@rlharris.org> - 2023-11-17 21:30 +0100
                              Re: approx in debian 12 "Andrew M.A. Cater" <amacater@einval.com> - 2023-11-18 11:50 +0100

#263579 — Re: approx in debian 12

Kamil Jońca <kjonca@o2.pl> writes:

> Charles Curley <charlescurley@charlescurley.com> writes:
>
>> On Thu, 16 Nov 2023 04:11:37 +0000
>> "Russell L. Harris" <russell@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
>> 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:
systemctl status "approx@*.service"

KJ

[toc] | [next] | [standalone]

#263580

On Thu, Nov 16, 2023 at 07:14:04AM +0100, Kamil Jo?ca wrote:
>Kamil Jo?ca <kjonca@o2.pl> writes:
>
>> Charles Curley <charlescurley@charlescurley.com> writes:
>>
>>> On Thu, 16 Nov 2023 04:11:37 +0000
>>> "Russell L. Harris" <russell@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
>>> 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:
>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.

RLH

[toc] | [prev] | [next] | [standalone]

#263584

	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 <kjonca@o2.pl> writes:
> > 
> > > Charles Curley <charlescurley@charlescurley.com> writes:
> > > 
> > > > On Thu, 16 Nov 2023 04:11:37 +0000
> > > > "Russell L. Harris" <russell@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

[toc] | [prev] | [next] | [standalone]

#263614

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
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

[toc] | [prev] | [next] | [standalone]

#263615

	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

[toc] | [prev] | [next] | [standalone]

#263616

>> debian   http://fpt.debian.org/debian
>
>Is this a typo? It should be (ftp, not fpt)
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# 

[toc] | [prev] | [next] | [standalone]

#263617

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:

curl -x http://localhost:9999 -v http://ftp.debian.org/debian/dists/stable/Release >/dev/null

Reco

[toc] | [prev] | [next] | [standalone]

#263618

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
< 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# 

[toc] | [prev] | [next] | [standalone]

#263619

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:

apt update -o Acquire::http::Proxy=http://localhost:9999

Reco

[toc] | [prev] | [next] | [standalone]

#263620

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
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# 

[toc] | [prev] | [next] | [standalone]

#263621

	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

[toc] | [prev] | [next] | [standalone]

#263628

On Fri, Nov 17, 2023 at 11:57:44AM +0300, Reco wrote:
>	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.

The red screen still appears.

Should we report an error regarding the approx man page which states:

USEAGE
approx is invoked by inetd(8)

RLH

[toc] | [prev] | [next] | [standalone]

#263630

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
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.

[toc] | [prev] | [next] | [standalone]

#263633

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:
>
>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
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

[toc] | [prev] | [next] | [standalone]

#263641

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:
> > 
> 
> 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
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
> 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web