Installation fails on Debian 11

Hi Folks
Thoughts on nethserver 8 install on debian please - ive managed to build a flakey cluster on debian 11 when i include debian desktop environment/gnome in the build but when i excluded these items i get the result below - this is a bare debian 11 install (only updates are to /etc/hosts /etc/hostname /etc/network/interfaces and installed net-tools). This is a proxmox vm btw
Cheers
Alex

alex@70neth56:~$ su -
Password:
root@70neth56:~#
root@70neth56:~#
root@70neth56:~#
root@70neth56:~# ping google.com
PING google.com (142.250.187.238) 56(84) bytes of data.
64 bytes from lhr25s34-in-f14.1e100.net (142.250.187.238): icmp_seq=1 ttl=56 time=9.37 ms
64 bytes from lhr25s34-in-f14.1e100.net (142.250.187.238): icmp_seq=2 ttl=56 time=9.40 ms
^C
— google.com ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 9.373/9.384/9.396/0.011 ms
root@70neth56:~# apt-get update && apt-get upgrade -y && apt-get install -y curl
Hit:1 Index of /debian-security bullseye-security InRelease
Hit:2 Index of /debian bullseye InRelease
Hit:3 Index of /debian bullseye-updates InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
libcurl4
The following NEW packages will be installed:
curl libcurl4
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 617 kB of archives.
After this operation, 1,198 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main amd64 libcurl4 amd64 7.74.0-1.3+deb11u7 [346 kB]
Get:2 Index of /debian bullseye/main amd64 curl amd64 7.74.0-1.3+deb11u7 [270 kB]
Fetched 617 kB in 0s (4,744 kB/s)
Selecting previously unselected package libcurl4:amd64.
(Reading database … 32671 files and directories currently installed.)
Preparing to unpack …/libcurl4_7.74.0-1.3+deb11u7_amd64.deb …
Unpacking libcurl4:amd64 (7.74.0-1.3+deb11u7) …
Selecting previously unselected package curl.
Preparing to unpack …/curl_7.74.0-1.3+deb11u7_amd64.deb …
Unpacking curl (7.74.0-1.3+deb11u7) …
Setting up libcurl4:amd64 (7.74.0-1.3+deb11u7) …
Setting up curl (7.74.0-1.3+deb11u7) …
Processing triggers for man-db (2.9.4-2) …
Processing triggers for libc-bin (2.31-13+deb11u6) …
root@70neth56:~# curl https://raw.githubusercontent.com/NethServer/ns8-core/main/core/install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3109 100 3109 0 0 6410 0 --:–:-- --:–:-- --:–:-- 6423
Checking machine hostname
Checking port 80 and 443 are not already in use
Restart journald:
Install dependencies:
System not supported
root@70neth56:~#

Try

curl https://raw.githubusercontent.com/NethServer/ns8-core/1.1.1/core/install.sh | bash
1 Like

so far so good, thank you Davide

1 Like

It’s a temporary workaround to the Debian 12 exclusive support for new installations that was merged today and will be soon released.

I don’t know if we can fix the URL for the future /cc @giacomo

1 Like

another thing ive noticed is that adding nodes to the cluster is flakey - TLS check doesnt work, node seems to add without it checked but the node is marked as offline by the cluster manager. ive added hosts file entries just in case its a name resolution thing but its not playing so far…

is it worth building on debian 12 instead of 11 now?

This seem a different issue. If a worker node does not connect there could be a wrong parameter or something in the network blocking the connection.

Please describe the issue in a separate thread.

For now on, to install NS8 on a supported distro this is the command

curl https://raw.githubusercontent.com/NethServer/ns8-core/ns8-stable/core/install.sh | bash

The admin’s manual has been fixed accordingly – Installation — NS8 documentation

4 Likes

This topic was automatically closed after 3 days. New replies are no longer allowed.