Installation stuck at 60%

M

mattb

New Member
May 27, 2022
7
0
1
Hi,
i'm trying to install Proxmox-VE the manual way on a fresh Debian 11.

Code: 
root@pve-test:/etc/network# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

To connect to the server I'm using SSH.

Code: 
echo "deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
curl -#o /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg http://download.proxmox.com/debian/proxmox-release-bullseye.gpg
apt update
apt upgrade -y
apt dist-upgrade -y
apt install proxmox-ve -y

The installation runs up to the following output:


Code: 
...
Creating config file /etc/samba/smb.conf with new version
Setting up libjemalloc2:amd64 (5.2.1-3) ...
Setting up libnet1:amd64 (1.1.6+dfsg-3.1) ...
Setting up libfdt1:amd64 (1.6.0-1) ...
Setting up libusbredirparser1:amd64 (0.8.0-1+b1) ...
Setting up libopts25:amd64 (1:5.18.16-4) ...
Setting up libunwind8:amd64 (1.3.2-2) ...
Setting up proxmox-mini-journalreader (1.3-1) ...
Setting up proxmox-archive-keyring (2.1) ...
Setting up libsnappy1v5:amd64 (1.1.8-1) ...
Setting up libflac8:amd64 (1.3.3-2+deb11u1) ...
Setting up libjs-extjs (7.0.0-1) ...
Setting up ifupdown2 (3.1.0-1+pmx3) ...
Installing new version of config file /etc/default/networking ...

network config changes have been detected for ifupdown2 compatibility.
Saved in /etc/network/interfaces.new for hot-apply or next reboot.

Reloading network config on first install
warning: duplicate interface lo found
Killed old client process

Progress: [ 60%] [##########################################################........................................]

At this point the installation freezes, but i still can create a new SSH session.
I don't know if this is the reason, but based on the warning of the duplicate interface i looked into /etc/network/.


Code: 
root@pve-test:/etc/network# ls -l
total 32
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-down.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-post-down.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-pre-up.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-up.d
drwxr-xr-x 3 root root 4096 Nov 25 08:10 ifupdown2
-rw-r--r-- 1 root root  289 Aug 29 07:52 interfaces
drwxr-xr-x 2 root root 4096 Nov 25 08:04 interfaces.d
-rw-r--r-- 1 root root  550 Nov 25 08:10 interfaces.new

Content of /etc/network/interfaces:
Code: 
root@pve-test:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5)

# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

Content of /etc/network/interfaces.net:
Code: 
root@pve-test:/etc/network# cat interfaces.new
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eth0 inet manual

Here's also the output of ip a:
Code: 
root@pve-test:/etc/network# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 96:00:01:b0:be:cb brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    altname ens3
    inet aaa.bbb.ccc.ddd/32 brd aaa.bbb.ccc.ddd scope global dynamic eth0
       valid_lft 85253sec preferred_lft 85253sec
    inet6 aaaa:bbbb:cccc:dddd:eeee:ffff/64 scope link
       valid_lft forever preferred_lft forever


Any ideas?
Thanks!
 
mattb said:
Hi,
i'm trying to install Proxmox-VE the manual way on a fresh Debian 11.

Code: 
root@pve-test:/etc/network# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

To connect to the server I'm using SSH.

Code: 
echo "deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
curl -#o /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg http://download.proxmox.com/debian/proxmox-release-bullseye.gpg
apt update
apt upgrade -y
apt dist-upgrade -y
apt install proxmox-ve -y

The installation runs up to the following output:


Code: 
...
Creating config file /etc/samba/smb.conf with new version
Setting up libjemalloc2:amd64 (5.2.1-3) ...
Setting up libnet1:amd64 (1.1.6+dfsg-3.1) ...
Setting up libfdt1:amd64 (1.6.0-1) ...
Setting up libusbredirparser1:amd64 (0.8.0-1+b1) ...
Setting up libopts25:amd64 (1:5.18.16-4) ...
Setting up libunwind8:amd64 (1.3.2-2) ...
Setting up proxmox-mini-journalreader (1.3-1) ...
Setting up proxmox-archive-keyring (2.1) ...
Setting up libsnappy1v5:amd64 (1.1.8-1) ...
Setting up libflac8:amd64 (1.3.3-2+deb11u1) ...
Setting up libjs-extjs (7.0.0-1) ...
Setting up ifupdown2 (3.1.0-1+pmx3) ...
Installing new version of config file /etc/default/networking ...

network config changes have been detected for ifupdown2 compatibility.
Saved in /etc/network/interfaces.new for hot-apply or next reboot.

Reloading network config on first install
warning: duplicate interface lo found
Killed old client process

Progress: [ 60%] [##########################################################........................................]

At this point the installation freezes, but i still can create a new SSH session.
I don't know if this is the reason, but based on the warning of the duplicate interface i looked into /etc/network/.


Code: 
root@pve-test:/etc/network# ls -l
total 32
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-down.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-post-down.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-pre-up.d
drwxr-xr-x 2 root root 4096 Nov 25 08:10 if-up.d
drwxr-xr-x 3 root root 4096 Nov 25 08:10 ifupdown2
-rw-r--r-- 1 root root  289 Aug 29 07:52 interfaces
drwxr-xr-x 2 root root 4096 Nov 25 08:04 interfaces.d
-rw-r--r-- 1 root root  550 Nov 25 08:10 interfaces.new

Content of /etc/network/interfaces:
Code: 
root@pve-test:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5)

# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

Content of /etc/network/interfaces.net:
Code: 
root@pve-test:/etc/network# cat interfaces.new
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eth0 inet manual

Here's also the output of ip a:
Code: 
root@pve-test:/etc/network# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 96:00:01:b0:be:cb brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    altname ens3
    inet aaa.bbb.ccc.ddd/32 brd aaa.bbb.ccc.ddd scope global dynamic eth0
       valid_lft 85253sec preferred_lft 85253sec
    inet6 aaaa:bbbb:cccc:dddd:eeee:ffff/64 scope link
       valid_lft forever preferred_lft forever


Any ideas?
Thanks!
Click to expand...

UPDATE: same result when following this guide: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
 
Does the installation actually freeze, or is it maybe just that your connection gets dropped and the installation continues?
You could try running it inside tmux or screen, that way you can continue from a new ssh session
 
One thing i have missed to tell: the server I'm using is a vServer in the Hetzner Cloud.

I set the server back to have a fresh Debian 11 again and started the install command on the server console that can be access directly in the Hetzner Cloud dashboard.

unfortunately, same result.
 
Since I couldn't get PVE installed on the described way I asked the Hetzner support to provide the ISO image of PVE in the Cloud Console.
So I was able to mount the ISO and start the normal installation which worked just fine and PVE is running now.
But the issue, when installing it based on an already installed Debian, is still present.
 
I just followed the same page instructions on a very vanilla Debian Bullseye install on an Ivy-Bridge era Intel NUC.
I hit exactly the same problem. Config of ifupdown2 fails/hangs and that failure cascades to the dependent packages including proxmox-ve.
No, the connection wasn't lost, and I could still login in another window and could see the stuck (sleeping) processes.
There was an initial issue with the /etc/network/interfaces where ifupdown2 failed to parse the (completely acceptable to vanilla ifupdown) line 'iface eno1 inet6 auto'. I followed the instructions at error in ifreload -a · Issue #70 · CumulusNetworks/ifupdown2 · GitHub to work around that. But subsequently, the install, or an attempt to force config via `dpkg --configure -a` simply hangs.
I rebooted the box, and now, although it's on the network, I can't ssh in. Will hook up a console tomorrow, and figure out what's wrong, but to confirm other reports, this is not working correctly currently.
 
Quick followup. The issue is ifupdown2 and ipv6. If you have an entry like
Code: 
iface eno1 inet6
then ifup will hang with dhclient asleep in the background.
This does not happen with the regular ifupdown code, so I'd argue that it's a bug in ifupdown2.
Simply commenting out that line, but leaving the "auto <interface>" line avoids the problem and SLAAC still seems to give the interface an ipv6 address.
 
  • Like
Reactions: Ghost_Toni and _gabriel
Im not sure if this Helps maybe but, Hetzner has this https://docs.hetzner.com/de/cloud/servers/static-configuration/
This helps so deactivate the cloudinit-config from Hetzner-Cloud.

At first I removed the /etc/network/interfaces file, then i replaced it by moving the /etc/network/interfaces.new to /etc/network/interfaces - also I removed the cfg file from interfaces.d.

Then I followed the Hetzner-guide and put eth0 how described. After that I runned ifup eth0 - at this point we are connected to the internet again. Then I can access the Proxmox Webpanel - reach the Server via SSH and so on. But when I reboot the Server it is broken again and i need to run ifup eth0 over the VNC again...

Im not used to Proxmox - so Im new into that, but I think when I boot the Server proxmox loads another interfaces-config before... not sure which one yet. But maybe sb else can help into that topic.
 
noxomix said:
Im not sure if this Helps maybe but, Hetzner has this https://docs.hetzner.com/de/cloud/servers/static-configuration/
This helps so deactivate the cloudinit-config from Hetzner-Cloud.

At first I removed the /etc/network/interfaces file, then i replaced it by moving the /etc/network/interfaces.new to /etc/network/interfaces - also I removed the cfg file from interfaces.d.

Then I followed the Hetzner-guide and put eth0 how described. After that I runned ifup eth0 - at this point we are connected to the internet again. Then I can access the Proxmox Webpanel - reach the Server via SSH and so on. But when I reboot the Server it is broken again and i need to run ifup eth0 over the VNC again...

Im not used to Proxmox - so Im new into that, but I think when I boot the Server proxmox loads another interfaces-config before... not sure which one yet. But maybe sb else can help into that topic.
Click to expand...
Make sure you also add disable-network-config one: https://docs.hetzner.com/cloud/servers/static-configuration/#disable-cloud-init-network-changes
 
I'm struggling with the same issue using a vServer on Hetzner Cloud, also getting stuck at 60%.

On a fresh Debian 11, I did the following (after installing vim):

* Create a new file at `/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg`, with the contents: `network: {config: disabled}`
* Copy contents of `/etc/network/interfaces.d/50-cloud-init` to `/etc/network/interfaces`
* `rm /etc/network/interfaces.d/50-cloud-init`
* Comment out the IPv6 lines

So `/etc/network/interfaces` looks like this:

```
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5)

# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# control-alias eth0
#iface eth0 inet6 static
# address 2a01:4ff:f0:829d::1/64
# dns-nameservers 2a01:4ff:ff00::add:2 2a01:4ff:ff00::add:1
# gateway fe80::1
```

Then ran: `service networking restart`

Then I was able to run all the instructions here to install Proxmox, and it didn't get stuck: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
 
You must log in or register to reply here.
Top Bottom