Strato Debian Instillation?

ledmax

New Member
Sep 13, 2023
27
1
3
Hello

As I was just told by Strato Support a Proxmox is possible at Strato under Debian.

Can someone tell me how this is done or show a tutorial ?


Hallo

Wie mir gerade der Strato Support mitgeteilt hat ist eine Proxmox bei Strato möglich unter Debian.

Kann mir jemand sagen wie das gemacht wird oder ein Anleitung zeigen ?
 
sorry if I am ignorant but strato.de debian12 installed and logged in here via ssh but get no further


1695650270249.png
 
Did you actually read the official guide I linked? You need to follow all steps from top to bottom. I can't see that you actually tried anything shown there except for the "apt install proxmox-ve"...
 
yes with it I come further ... announce me if it's stuck
1695653639134.png


1695653722328.png

1695653867812.png


1695654163626.png
 
Last edited:
i finally got the /hosts file and /etc/network/interfaces to work but i can't update... what am i doing wrong?

1695678181768.png
 
If you want to use the (default) enterprise repository, you need to buy a support subscription. Otherwise disable the enterprise repository and configure the no-subscription repository instead (you did the latter but without removing the first, which explains the error messages you are getting).
Did you search this forum for this problem, it's very common? Personally, I find your screenshots difficult to read; can't you copy-paste the relevant text in CODE-tag?
 
  • Like
Reactions: LnxBil and ledmax
in itself I try a lot ... but he forgets the settings
Preparing to unpack .../dnsutils_1%3a9.18.19-1~deb12u1_all.deb ... Unpacking dnsutils (1:9.18.19-1~deb12u1) ... Setting up pve-manager (8.0.4) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess returned error exit status 1 Setting up bind9-dnsutils (1:9.18.19-1~deb12u1) ... Setting up dnsutils (1:9.18.19-1~deb12u1) ... Processing triggers for man-db (2.11.2-2) ... Errors were encountered while processing: pve-manager E: Sub-process /usr/bin/dpkg returned an error code (1) root@5375f6b4-956a-491a-9e95-f034b65e850c:~# sudo apt update sudo apt upgrade Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:2 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B] Hit:6 http://deb.debian.org/debian bookworm InRelease Hit:7 http://deb.debian.org/debian bookworm-updates InRelease Hit:8 http://security.debian.org/debian-security bookworm-security InRelease Hit:3 https://deb.debian.org/debian bookworm InRelease Hit:4 https://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.debian.org/debian bookworm-backports InRelease Hit:9 https://deb.debian.org/debian-security bookworm-security InRelease Get:10 http://download.proxmox.com/debian/pve bookworm InRelease [2768 B] Err:11 https://enterprise.proxmox.com/debian/pve bookworm InRelease 401 Unauthorized [IP: 2a01:7e0:0:424::249 443] Reading package lists... Done E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease 401 Unauthorized [IP: 2a01:7e0:0:424::249 443] E: The repository 'https://enterprise.proxmox.com/debian/pve bookworm InRelease' is not signed. 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. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image proxmox-kernel-helper proxmox-mail-forward proxmox-mini-journalreader proxmox-offline-mirror-docs proxmox-offline-mirror-helper proxmox-websocket-tunnel proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-edk2-firmware pve-firewall pve-firmware pve-ha-manager pve-i18n pve-lxc-syscalld pve-manager pve-qemu-kvm pve-xtermjs python3-ceph-argparse python3-ceph-common python3-cephfs python3-gpg python3-ldb python3-prettytable python3-protobuf python3-rados python3-rbd python3-samba python3-talloc python3-tdb python3-wcwidth qemu-server qrencode rrdcached rsync samba-common samba-common-bin samba-dsdb-modules samba-libs smartmontools smbclient spiceterm sqlite3 swtpm swtpm-libs swtpm-tools thin-provisioning-tools uidmap va-driver-all vdpau-driver-all vncterm xsltproc zfs-zed zfsutils-linux Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up pve-manager (8.0.4) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: pve-manager E: Sub-process /usr/bin/dpkg returned an error code (1) root@5375f6b4-956a-491a-9e95-f034b65e850c:~# sudo dpkg --configure -a Setting up pve-manager (8.0.4) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: pve-manager root@5375f6b4-956a-491a-9e95-f034b65e850c:~# systemctl status pveproxy ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled) Active: active (running) since Tue 2023-09-26 09:53:57 UTC; 40min ago Main PID: 900 (pveproxy) Tasks: 4 (limit: 9406) Memory: 140.5M CPU: 1min 14.520s CGroup: /system.slice/pveproxy.service ├─ 900 pveproxy ├─49832 "pveproxy worker" ├─49833 "pveproxy worker" └─49834 "pveproxy worker" Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[49790]: worker exit Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: worker 49789 finished Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: starting 1 worker(s) Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[49832]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) > Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: worker 49833 started Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[49833]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) > Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: worker 49790 finished Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: starting 1 worker(s) Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[900]: worker 49834 started Sep 26 10:34:07 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[49834]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) > root@5375f6b4-956a-491a-9e95-f034b65e850c:~# wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg # verify sha512sum /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg 7da6fe34168adc6e479327ba517796d4702fa2f8b4f0a9833f5exxxxxxxxxxxxxxxxxxxxxxxxxe201595edc86a84463d50383d07f64bdde2e3658108db7d6dc87 /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg --2023-09-26 10:37:43-- https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg Resolving enterprise.proxmox.com (enterprise.proxmox.com)... 2a01:7e0:0:424::249, 212.224.123.70 Connecting to enterprise.proxmox.com (enterprise.proxmox.com)|2a01:7e0:0:424::249|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1187 (1.2K) [application/octet-stream] Saving to: ‘/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg’ /etc/apt/trusted.gpg.d/proxmox-releas 100%[=======================================================================>] 1.16K --.-KB/s in 0s 2023-09-26 10:37:43 (31.2 MB/s) - ‘/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg’ saved [1187/1187] 7da6fe34168adc6e479327ba517796d4702fa2f8b4f0a9xxxxxxxxxxxxxxxxxxx274fe201595edc86a84463d50383d07f64bdde2e3658108db7d6dc87 /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg -bash: 7da6fe34168adc6e479327ba517796d4702fa2f8b4f0a9xxxxxxxxxxxxxxxxx595edc86a84463d50383d07f64bdde2e3658108db7d6dc87: command not found root@5375f6b4-956a-491a-9e95-f034b65e850c:~# cat /etc/apt/sources.list.d/pve-no-subscription.list deb http://download.proxmox.com/debian/pve bosudo apt updateubscriptionroot@5375f6b4-956a-491a-9e95-f034b65e850c:~# sudo apt update sudo apt full-upgrade Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:2 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B] Hit:6 http://deb.debian.org/debian bookworm InRelease Hit:7 http://deb.debian.org/debian bookworm-updates InRelease Hit:8 http://security.debian.org/debian-security bookworm-security InRelease Hit:3 https://deb.debian.org/debian bookworm InRelease Hit:4 https://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.debian.org/debian bookworm-backports InRelease Hit:9 https://deb.debian.org/debian-security bookworm-security InRelease Get:10 http://download.proxmox.com/debian/pve bookworm InRelease [2768 B] Fetched 2768 B in 1s (2678 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 W: Target Packages (pve-no-subscription/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 W: Target Translations (pve-no-subscription/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 W: Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 W: Target Packages (pve-no-subscription/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 W: Target Translations (pve-no-subscription/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/pve-install-repo.list:1 and /etc/apt/sources.list.d/pve-no-subscription.list:1 Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: alsa-topology-conf alsa-ucm-conf bridge-utils ceph-common ceph-fuse cifs-utils cloud-image-utils cloud-utils corosync criu cstream dconf-gsettings-backend dconf-service dmeventd dtach ebtables faketime fontconfig fontconfig-config fonts-dejavu-core fonts-font-awesome fonts-glyphicons-halflings genisoimage glib-networking glib-networking-common glib-networking-services glusterfs-client glusterfs-common grub-pc gsettings-desktop-schemas gstreamer1.0-libav gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-x hdparm i965-va-driver ibverbs-providers idn intel-media-va-driver ipset javascript-common libaa1 libaacs0 libaio1 libanyevent-http-perl libanyevent-perl libaom3 libappconfig-perl libapt-pkg-perl libarchive13 libasound2 libasound2-data libass9 libasync-interrupt-perl libasyncns0 libauthen-pam-perl libavahi-client3 libavahi-common-data libavahi-common3 libavc1394-0 libavcodec59 libavfilter8 libavformat59 libavutil57 libbabeltrace1 libbdplus0 libblas3 libbluray2 libboost-context1.74.0 libboost-filesystem1.74.0 libboost-iostreams1.74.0 libboost-program-options1.74.0 libboost-thread1.74.0 libbs2b0 libcaca0 libcairo-gobject2 libcairo2 libcdparanoia0 libcephfs2 libcfg7 libchromaprint1 libcjson1 libcmap4 libcodec2-1.0 libcorosync-common4 libcpg4 libcrypt-openssl-bignum-perl libcrypt-openssl-random-perl libcrypt-openssl-rsa-perl libcups2 libdatrie1 libdav1d6 libdbi1 libdconf1 libdeflate0 libdevel-cycle-perl libdevmapper-event1.02.1 libdigest-bubblebabble-perl libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libdv4 libdw1 libepoxy0 libev-perl libfaketime libfdt1 libfile-chdir-perl libfile-readbackwards-perl proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image proxmox-kernel-helper proxmox-mail-forward proxmox-mini-journalreader proxmox-offline-mirror-docs proxmox-offline-mirror-helper proxmox-websocket-tunnel proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-edk2-firmware pve-firewall pve-firmware pve-ha-manager pve-i18n pve-lxc-syscalld pve-manager pve-qemu-kvm pve-xtermjs python3-ceph-argparse python3-ceph-common python3-cephfs python3-gpg python3-ldb python3-prettytable python3-protobuf python3-rados python3-rbd python3-samba python3-talloc python3-tdb python3-wcwidth qemu-server qrencode rrdcached rsync samba-common samba-common-bin samba-dsdb-modules samba-libs smartmontools smbclient spiceterm sqlite3 swtpm swtpm-libs swtpm-tools thin-provisioning-tools uidmap va-driver-all vdpau-driver-all vncterm xsltproc zfs-zed zfsutils-linux Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up pve-manager (8.0.4) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: pve-manager E: Sub-process /usr/bin/dpkg returned an error code (1) root@5375f6b4-956a-491a-9e95-f034b65e850c:~# sudo apt update sudo apt full-upgrade
 

Attachments

  • 1695725118020.png
    1695725118020.png
    241.7 KB · Views: 3
Last edited:
please again for help :) the installation has now finally gone through cleanly.. on debian12 but how nice everything was installed without error ... so the https://xx.xx.xx.xxx:8006 does not want to call any page

can I somehow check if proxmox is installed / started correctly ?
 
hoo ... has looked so nice during installation ^^ but now no longer
root@5375f6b4-956a-491a-9e95-f034b65e850c:~# netstat -tulnp | grep 8006 -bash: netstat: command not found root@5375f6b4-956a-491a-9e95-f034b65e850c:~#

root@5375f6b4-956a-491a-9e95-f034b65e850c:~# systemctl status pve* × pve-ha-lrm.service - PVE Local HA Resource Manager Daemon Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:22 UTC; 6min ago Process: 893 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=111) CPU: 595ms Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: Unable to load access control list: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-lrm[893]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-ha-lrm.service: Control process exited, code=exited, status=111/n/a Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-ha-lrm.service: Failed with result 'exit-code'. Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pve-ha-lrm.service - PVE Local HA Resource Manager Daemon. ● pvefw-logger.service - Proxmox VE firewall logger Loaded: loaded (/lib/systemd/system/pvefw-logger.service; enabled; preset: enabled) Active: active (running) since Wed 2023-09-27 06:54:17 UTC; 6min ago Process: 383 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS) Main PID: 395 (pvefw-logger) Tasks: 2 (limit: 9406) Memory: 636.0K CPU: 38ms CGroup: /system.slice/pvefw-logger.service └─395 /usr/sbin/pvefw-logger Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger... Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger. Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c pvefw-logger[395]: starting pvefw logger × pvescheduler.service - Proxmox VE scheduler Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:23 UTC; 6min ago Process: 899 ExecStart=/usr/bin/pvescheduler start (code=exited, status=111) CPU: 603ms Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvescheduler[899]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvescheduler[899]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvescheduler[899]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvescheduler[899]: Unable to load access control list: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvescheduler[899]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pvescheduler.service: Control process exited, code=exited, status=111/n/a Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pvescheduler.service: Failed with result 'exit-code'. Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pvescheduler.service - Proxmox VE scheduler. ● pvebanner.service - Proxmox VE Login Banner Loaded: loaded (/lib/systemd/system/pvebanner.service; enabled; preset: enabled) Active: active (exited) since Wed 2023-09-27 06:54:17 UTC; 6min ago Process: 381 ExecStart=/usr/bin/pvebanner (code=exited, status=0/SUCCESS) Main PID: 381 (code=exited, status=0/SUCCESS) CPU: 192ms Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pvebanner.service - Proxmox VE Login Banner... Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Finished pvebanner.service - Proxmox VE Login Banner. ● pvenetcommit.service - Commit Proxmox VE network changes Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; preset: enabled) Active: active (exited) since Wed 2023-09-27 06:54:17 UTC; 6min ago Process: 384 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS) Process: 389 ExecStart=sh -c if [ -f ${FN}.new ]; then mv ${FN}.new ${FN}; fi (code=exited, status=0/SUCCESS) Main PID: 389 (code=exited, status=0/SUCCESS) CPU: 3ms Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pvenetcommit.service - Commit Proxmox VE network changes... Sep 27 06:54:17 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Finished pvenetcommit.service - Commit Proxmox VE network changes. ● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service; enabled; preset: enabled) Active: active (running) since Wed 2023-09-27 06:54:19 UTC; 6min ago Main PID: 502 (pve-lxc-syscall) Tasks: 5 (limit: 9406) Memory: 1.3M CPU: 3ms CGroup: /system.slice/pve-lxc-syscalld.service └─502 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock Sep 27 06:54:19 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon... Sep 27 06:54:19 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Started pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon. × pve-guests.service - PVE guests Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:23 UTC; 6min ago Process: 897 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS) Process: 898 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=111) Main PID: 898 (code=exited, status=111) CPU: 922ms Sep 27 06:54:22 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pve-guests.service - PVE guests... Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvesh[898]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvesh[898]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvesh[898]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c pvesh[898]: Unable to load access control list: Connection refused Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-guests.service: Main process exited, code=exited, status=111/n/a Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-guests.service: Failed with result 'exit-code'. Sep 27 06:54:23 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pve-guests.service - PVE guests. ● pvedaemon.service - PVE API Daemon Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled) Active: active (running) since Wed 2023-09-27 06:54:20 UTC; 6min ago Process: 584 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS) Main PID: 879 (pvedaemon) Tasks: 4 (limit: 9406) Memory: 215.0M CPU: 970ms CGroup: /system.slice/pvedaemon.service ├─879 pvedaemon ├─880 "pvedaemon worker" ├─881 "pvedaemon worker" └─882 "pvedaemon worker" Sep 27 06:54:19 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Starting pvedaemon.service - PVE API Daemon... Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvedaemon[879]: starting server Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvedaemon[879]: starting 3 worker(s) Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvedaemon[879]: worker 880 started Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvedaemon[879]: worker 881 started Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvedaemon[879]: worker 882 started Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Started pvedaemon.service - PVE API Daemon. ● pve-daily-update.timer - Daily PVE download activities Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; preset: enabled) Active: active (waiting) since Wed 2023-09-27 06:54:19 UTC; 6min ago Trigger: Thu 2023-09-28 05:13:27 UTC; 22h left Triggers: ● pve-daily-update.service Sep 27 06:54:19 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Started pve-daily-update.timer - Daily PVE download activities. × pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:21 UTC; 6min ago Process: 884 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=111) CPU: 606ms Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-crm[884]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-crm[884]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-crm[884]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-crm[884]: Unable to load access control list: Connection refused Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c pve-ha-crm[884]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-ha-crm.service: Control process exited, code=exited, status=111/n/a Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-ha-crm.service: Failed with result 'exit-code'. Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon. ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled) Active: active (running) since Wed 2023-09-27 06:54:21 UTC; 6min ago Process: 885 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111) Process: 887 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS) Main PID: 889 (pveproxy) Tasks: 4 (limit: 9406) Memory: 140.8M CPU: 12.036s CGroup: /system.slice/pveproxy.service ├─ 889 pveproxy ├─4438 "pveproxy worker" ├─4439 "pveproxy worker" └─4440 "pveproxy worker" Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: starting 1 worker(s) Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: worker 4396 finished Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: worker 4438 started Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: worker 4397 finished Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: starting 2 worker(s) Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: worker 4439 started Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[889]: worker 4440 started Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[4438]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or ke> Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[4439]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or ke> Sep 27 07:00:30 5375f6b4-956a-491a-9e95-f034b65e850c pveproxy[4440]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or ke> × pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:20 UTC; 6min ago Process: 585 ExecStart=/usr/bin/pvestatd start (code=exited, status=111) CPU: 509ms Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvestatd[585]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvestatd[585]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvestatd[585]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvestatd[585]: Unable to load access control list: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pvestatd[585]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pvestatd.service: Failed with result 'exit-code'. Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pvestatd.service - PVE Status Daemon. ● pve-storage.target - PVE Storage Target Loaded: loaded (/lib/systemd/system/pve-storage.target; static) Active: active since Wed 2023-09-27 06:54:19 UTC; 6min ago Sep 27 06:54:19 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Reached target pve-storage.target - PVE Storage Target. × pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:21 UTC; 6min ago Process: 886 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION) CPU: 10ms Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5. Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem. Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-cluster.service: Start request repeated too quickly. Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-cluster.service: Failed with result 'exit-code'. Sep 27 06:54:21 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem. × pve-firewall.service - Proxmox VE firewall Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-27 06:54:20 UTC; 6min ago Process: 583 ExecStartPre=/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy (code=exited, status=0/SUCCESS) Process: 586 ExecStartPre=/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy (code=exited, status=0/SUCCESS) Process: 587 ExecStartPre=/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy (code=exited, status=0/SUCCESS) Process: 588 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=111) CPU: 548ms Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pve-firewall[588]: ipcc_send_rec[1] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pve-firewall[588]: ipcc_send_rec[2] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pve-firewall[588]: ipcc_send_rec[3] failed: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c pve-firewall[588]: Unable to load access control list: Connection refused Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-firewall.service: Control process exited, code=exited, status=111/n/a Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: pve-firewall.service: Failed with result 'exit-code'. Sep 27 06:54:20 5375f6b4-956a-491a-9e95-f034b65e850c systemd[1]: Failed to start pve-firewall.service - Proxmox VE firewall.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!