[SOLVED] Proxmox Gui not started after apt-get upgrade with no subscription

[persapi]

Hi all,
I did a confguration change on my proxmox. I realize that at each netwroking change I have to reload proxmox but I discover that using ifupdown2 this should not need anymore.

I try to install the package but I receive an error due the subscription, for that reason I changed the repo with no-subsription

deb http://download.proxmox.com/debian/pve buster pve-no-subscription

after a reboot I'm not able to start pveproxy.service

systemctl start pveproxy.service
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xe" for details.

● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-10-16 00:51:12 CEST; 1min 17s ago
Process: 7429 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 7431 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)

Oct 16 00:51:12 mox systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Oct 16 00:51:12 mox systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Oct 16 00:51:12 mox systemd[1]: Stopped PVE API Proxy Server.
Oct 16 00:51:12 mox systemd[1]: pveproxy.service: Start request repeated too quickly.
Oct 16 00:51:12 mox systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Oct 16 00:51:12 mox systemd[1]: Failed to start PVE API Proxy Server.



Could you please point me on the right direction to restore proxmox?

thanks a lot

 

[Moayad]

hi,

what does says the output of systemctl status networking.service?

 

[persapi]

Hi Moayad,
thanks for you question, here the output:

systemctl status networking.service
● networking.service - Network initialization
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2020-10-16 00:55:30 CEST; 9h ago
Docs: man:interfaces(5)
man:ifup(8)
man:ifdown(8)
Process: 763 ExecStart=/usr/share/ifupdown2/sbin/start-networking start (code=exited, status=0/SUCCESS)
Main PID: 763 (code=exited, status=0/SUCCESS)

Oct 16 00:55:29 mox systemd[1]: Starting Network initialization...
Oct 16 00:55:29 mox networking[763]: networking: Configuring network interfaces
Oct 16 00:55:30 mox networking[763]: warning: vmbr1: apply bridge ports settings: cmd '/bin/ip -force -batch - [link set dev wlx240a64a0fb0d master vmbr1]' failed: returned 1 (Error: Device doe
Oct 16 00:55:30 mox networking[763]: Command failed -:1
Oct 16 00:55:30 mox networking[763]: )
Oct 16 00:55:30 mox systemd[1]: Started Network initialization.

 

[Moayad]

Hi again

Please try apt update && apt dist-upgrade then reboot your node

 

[persapi]

Hi Moayad,
it works! Just to understand how can I spot this next time?

Thanks a lot, beer payed for you man

 

[Moayad]

Just to understand how can I spot this next time?

I guess when you forgot to add our repositories and tried to install/remove the package (ifupdown2), probably you installed package from the debian repos instead of ours.

glad that you solved your issue, please mark the thread as [SOLVED] to help other people who have the same problem Thanks!

 

[kemil]

Hi again

Please try apt update && apt dist-upgrade then reboot your node

Hi there, I have the same issue, can you please help. I installed ifupdown2 with apt install ifupdown2 and it installed from debian repos as you mentioned instead of proxmox.

now, network connectivity is lost, and my server cannot boot from HD. I just have access to rescue mode.

I tried

apt update && apt dist-upgrade

, but still server could not restart from HD mode.

in the rescue mode, when I check my network interfaces, it is different than when it was working fine. I will put some output below, Please take a look and suggest some solution.

root@rescue:~# ip addr
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: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 06:56:6c:7a:36:af brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 12:cf:58:3d:cf:1d brd ff:ff:ff:ff:ff:ff
4: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
    link/ether b6:ff:98:54:0f:16 brd ff:ff:ff:ff:ff:ff
5: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 32
    link/ether 22:dc:0e:05:88:90 brd ff:ff:ff:ff:ff:ff
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid 3cecef5f1818 state UP group default qlen 1000
    link/ether 3c:ec:ef:5f:18:18 brd ff:ff:ff:ff:ff:ff
    inet 51.222.240.78/24 brd 51.222.240.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2607:5300:203:8c4e::/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::3eec:efff:fe5f:1818/64 scope link
       valid_lft forever preferred_lft forever
7: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop portid 3cecef5f1819 state DOWN group default qlen 1000
    link/ether 3c:ec:ef:5f:18:19 brd ff:ff:ff:ff:ff:ff
8: teql0: <NOARP> mtu 1500 qdisc noop state DOWN group default qlen 100
    link/void
9: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
10: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
    link/gre 0.0.0.0 brd 0.0.0.0
11: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
13: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
14: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd ::

cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

root@rescue:~# systemctl status networking
● networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
        /lib/systemd/system/networking.service.d
           └─network-pre.conf
   Active: active (exited) since Sun 2023-01-08 15:20:39 EST; 5min ago

Jan 08 15:20:40 rescue.ovh.net networking[1212]: Configuring network interfaces...done.
Jan 08 15:20:39 rescue.ovh.net systemd[1]: Started LSB: Raise network interfaces..

root@rescue:~# systemctl start pveproxy.service
Failed to start pveproxy.service: Unit pveproxy.service failed to load: No such file or directory.

Please help.

 

[kemil]

Hi Moayad,
it works! Just to understand how can I spot this next time?

Thanks a lot, beer payed for you man

how did you solve the issue, I am facing the same issue, but cannot resolve it. PLease help.