[SOLVED] Failed to start The Proxmox VE cluster filesystem, bitte um Hilfe

O

Oliver_W

New Member
Sep 12, 2021
5
0
1
56
Hallo zusammen,
mein Name ist Oliver und ich habe zum 2. Mal das Problem das mir beim Neustart von Proxmox (booten)
zig "Failed" angezigt werden. Dazu gehört dann auch kein Zugriff auf die Web-GUI. Mein Englisch ist nicht ganz so schlecht
aber ich habe soweit nichts gefunden was mein Problem löst oder ich habe es nicht richtig verstanden. Nach dem 1. Mal habe ich Proxmox und die VMs
neu installiert. Es lief alles absolut problemlos, heute habe ich aber das System runtergefahren und eine zusätzliche Netzwerkkarte eingebaut,
allerdings das Netzwerkkabel an der alten Karte gelassen, so das sich Netzwerktechnisch nichts geändert haben sollte.

Hier mal die diversen Ausgaben:

systemctl status pve-cluster.service Sep 12 13:45:00 prox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5. Sep 12 13:45:00 prox systemd[1]: Stopped The Proxmox VE cluster filesystem. Sep 12 13:45:00 prox systemd[1]: pve-cluster.service: Start request repeated too quickly. Sep 12 13:45:00 prox systemd[1]: pve-cluster.service: Failed with result 'exit-code'. Sep 12 13:45:00 prox systemd[1]: Failed to start The Proxmox VE cluster filesystem.

systemctl status pveproxy root@prox:/# systemctl status pveproxy ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-09-12 12:33:59 CEST; 1h 37min ago Process: 2418 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111) Process: 2419 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS) Main PID: 2421 (pveproxy) Tasks: 4 (limit: 38074) Memory: 130.7M CPU: 1min 31.121s CGroup: /system.slice/pveproxy.service ├─2421 pveproxy ├─6650 pveproxy worker ├─6651 pveproxy worker └─6652 pveproxy worker Sep 12 14:11:18 prox pveproxy[2421]: worker 6648 finished Sep 12 14:11:18 prox pveproxy[2421]: worker 6650 started Sep 12 14:11:18 prox pveproxy[6649]: worker exit Sep 12 14:11:18 prox pveproxy[6650]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:11:18 prox pveproxy[2421]: worker 6649 finished Sep 12 14:11:18 prox pveproxy[2421]: starting 2 worker(s) Sep 12 14:11:18 prox pveproxy[2421]: worker 6651 started Sep 12 14:11:18 prox pveproxy[2421]: worker 6652 started Sep 12 14:11:18 prox pveproxy[6651]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:11:18 prox pveproxy[6652]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891.

journalctl -xe ░░ A stop job for unit pve-cluster.service has finished. ░░ ░░ The job identifier is 12193 and the job result is done. Sep 12 14:13:06 prox systemd[1]: pve-cluster.service: Start request repeated too quickly. Sep 12 14:13:06 prox systemd[1]: pve-cluster.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'. Sep 12 14:13:06 prox systemd[1]: Failed to start The Proxmox VE cluster filesystem. ░░ Subject: A start job for unit pve-cluster.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit pve-cluster.service has finished with a failure. ░░ ░░ The job identifier is 12193 and the job result is failed. Sep 12 14:13:06 prox systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped. ░░ Subject: A start job for unit corosync.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit corosync.service has finished successfully. ░░ ░░ The job identifier is 12271. Sep 12 14:13:09 prox pveproxy[6723]: worker exit Sep 12 14:13:09 prox pveproxy[2421]: worker 6723 finished Sep 12 14:13:09 prox pveproxy[2421]: starting 2 worker(s) Sep 12 14:13:09 prox pveproxy[2421]: worker 6733 started Sep 12 14:13:09 prox pveproxy[2421]: worker 6734 started Sep 12 14:13:09 prox pveproxy[6724]: worker exit Sep 12 14:13:09 prox pveproxy[6733]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:09 prox pveproxy[6734]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:09 prox pveproxy[2421]: worker 6724 finished Sep 12 14:13:09 prox pveproxy[2421]: starting 1 worker(s) Sep 12 14:13:09 prox pveproxy[2421]: worker 6735 started Sep 12 14:13:09 prox pveproxy[6735]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:14 prox pveproxy[6733]: worker exit Sep 12 14:13:14 prox pveproxy[6734]: worker exit Sep 12 14:13:14 prox pveproxy[2421]: worker 6733 finished Sep 12 14:13:14 prox pveproxy[2421]: starting 1 worker(s) Sep 12 14:13:14 prox pveproxy[2421]: worker 6734 finished Sep 12 14:13:14 prox pveproxy[2421]: worker 6736 started Sep 12 14:13:14 prox pveproxy[6735]: worker exit Sep 12 14:13:14 prox pveproxy[6736]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:14 prox pveproxy[2421]: worker 6735 finished Sep 12 14:13:14 prox pveproxy[2421]: starting 2 worker(s) Sep 12 14:13:14 prox pveproxy[2421]: worker 6737 started Sep 12 14:13:14 prox pveproxy[2421]: worker 6738 started Sep 12 14:13:14 prox pveproxy[6737]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:14 prox pveproxy[6738]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:19 prox pveproxy[6736]: worker exit Sep 12 14:13:19 prox pveproxy[2421]: worker 6736 finished Sep 12 14:13:19 prox pveproxy[2421]: starting 1 worker(s) Sep 12 14:13:19 prox pveproxy[2421]: worker 6739 started Sep 12 14:13:19 prox pveproxy[6737]: worker exit Sep 12 14:13:19 prox pveproxy[6738]: worker exit Sep 12 14:13:19 prox pveproxy[6739]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:19 prox pveproxy[2421]: worker 6737 finished Sep 12 14:13:19 prox pveproxy[2421]: worker 6738 finished Sep 12 14:13:19 prox pveproxy[2421]: starting 1 worker(s) Sep 12 14:13:19 prox pveproxy[2421]: worker 6740 started Sep 12 14:13:19 prox pveproxy[6740]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:24 prox pveproxy[6739]: worker exit Sep 12 14:13:24 prox pveproxy[2421]: worker 6739 finished Sep 12 14:13:24 prox pveproxy[2421]: starting 2 worker(s) Sep 12 14:13:24 prox pveproxy[2421]: worker 6741 started Sep 12 14:13:24 prox pveproxy[2421]: worker 6742 started Sep 12 14:13:24 prox pveproxy[6740]: worker exit Sep 12 14:13:24 prox pveproxy[6741]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:24 prox pveproxy[6742]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891. Sep 12 14:13:24 prox pveproxy[2421]: worker 6740 finished Sep 12 14:13:24 prox pveproxy[2421]: starting 1 worker(s) Sep 12 14:13:24 prox pveproxy[2421]: worker 6743 started Sep 12 14:13:24 prox pveproxy[6743]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1891.
journalctl -b -- Journal begins at Wed 2021-09-01 15:03:41 CEST, ends at Sun 2021-09-12 14:16:25 CEST. -- Sep 12 12:33:55 prox kernel: Linux version 5.11.22-3-pve (wbumiller@olga) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.11.22-7 (Wed, 18 Aug 2021 15:06:12 +0200) () Sep 12 12:33:55 prox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.22-3-pve root=/dev/mapper/pve-root ro quiet Sep 12 12:33:55 prox kernel: KERNEL supported cpus: Sep 12 12:33:55 prox kernel: Intel GenuineIntel Sep 12 12:33:55 prox kernel: AMD AuthenticAMD Sep 12 12:33:55 prox kernel: Hygon HygonGenuine Sep 12 12:33:55 prox kernel: Centaur CentaurHauls Sep 12 12:33:55 prox kernel: zhaoxin Shanghai Sep 12 12:33:55 prox kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Sep 12 12:33:55 prox kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Sep 12 12:33:55 prox kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Sep 12 12:33:55 prox kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Sep 12 12:33:55 prox kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Sep 12 12:33:55 prox kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Sep 12 12:33:55 prox kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Sep 12 12:33:55 prox kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Sep 12 12:33:55 prox kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Sep 12 12:33:55 prox kernel: BIOS-provided physical RAM map: Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000005a89ffff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000005a8a0000-0x000000005a8a0fff] ACPI NVS Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000005a8a1000-0x000000005a8cafff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000005a8cb000-0x000000005a91efff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000005a91f000-0x000000005b63ffff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x000000005b640000-0x0000000076b89fff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000076b8a000-0x0000000076be0fff] type 20 Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000076be1000-0x00000000777b0fff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000777b1000-0x0000000077f99fff] ACPI NVS Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000077f9a000-0x0000000077ffefff] ACPI data Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000077fff000-0x0000000077ffffff] usable Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000078000000-0x00000000780fffff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Sep 12 12:33:55 prox kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000875ffffff] usable Sep 12 12:33:55 prox kernel: NX (Execute Disable) protection: active Sep 12 12:33:55 prox kernel: efi: EFI v2.40 by American Megatrends Sep 12 12:33:55 prox kernel: efi: ACPI=0x77f2f000 ACPI 2.0=0x77f2f000 SMBIOS=0xf05e0 Sep 12 12:33:55 prox kernel: secureboot: Secure boot could not be determined (mode 0) Sep 12 12:33:55 prox kernel: SMBIOS 2.8 present. Sep 12 12:33:55 prox kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme6+, BIOS P7.40 01/22/2018 Sep 12 12:33:55 prox kernel: tsc: Detected 3400.000 MHz processor Sep 12 12:33:55 prox kernel: tsc: Detected 3399.906 MHz TSC Sep 12 12:33:55 prox kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Sep 12 12:33:55 prox kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Sep 12 12:33:55 prox kernel: last_pfn = 0x876000 max_arch_pfn = 0x400000000 Sep 12 12:33:55 prox kernel: MTRR default type: write-back Sep 12 12:33:55 prox kernel: MTRR fixed ranges enabled: Sep 12 12:33:55 prox kernel: 00000-9FFFF write-back Sep 12 12:33:55 prox kernel: A0000-BFFFF uncachable Sep 12 12:33:55 prox kernel: C0000-FFFFF write-protect Sep 12 12:33:55 prox kernel: MTRR variable ranges enabled: Sep 12 12:33:55 prox kernel: 0 base 0080000000 mask 7F80000000 uncachable Sep 12 12:33:55 prox kernel: 1 base 007C000000 mask 7FFC000000 uncachable Sep 12 12:33:55 prox kernel: 2 base 007A000000 mask 7FFE000000 uncachable Sep 12 12:33:55 prox kernel: 3 base 0079000000 mask 7FFF000000 uncachable Sep 12 12:33:55 prox kernel: 4 base 0078800000 mask 7FFF800000 uncachable Sep 12 12:33:55 prox kernel: 5 disabled Sep 12 12:33:55 prox kernel: 6 disabled Sep 12 12:33:55 prox kernel: 7 disabled Sep 12 12:33:55 prox kernel: 8 disabled Sep 12 12:33:55 prox kernel: 9 disabled Sep 12 12:33:55 prox kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Sep 12 12:33:55 prox kernel: last_pfn = 0x78000 max_arch_pfn = 0x400000000 Sep 12 12:33:55 prox kernel: found SMP MP-table at [mem 0x000fc750-0x000fc75f] Sep 12 12:33:55 prox kernel: check: Scanning 1 areas for low memory corruption Sep 12 12:33:55 prox kernel: Using GB pages for direct mapping Sep 12 12:33:55 prox kernel: secureboot: Secure boot could not be determined (mode 0) Sep 12 12:33:55 prox kernel: RAMDISK: [mem 0x310ed000-0x3486dfff] Sep 12 12:33:55 prox kernel: ACPI: Early table checksum verification disabled Sep 12 12:33:55 prox kernel: ACPI: RSDP 0x0000000077F2F000 000024 (v02 ALASKA)

Ich möchte das ganze nicht wieder neu machen müssen, kann mir bitte jemand unter die Arme greifen, dass wäre echt super.


Danke und Gruß
Oliver
 
Ich habe nun weiter im Netz Infos gesucht, komme aber nicht wirklich weiter.
Hier unten ist zu sehen was beim booten von Proxmox passiert

Fehler-1.jpg
 
Problem gelöst, wirklich dämlich...

/etc/hosts 127.0.0.1 localhost.localdomain localhost 127.0.0.1 prox.local prox 192.168.0.250 prox.local prox

1x 127.0.0.1 zuviel. Keine Ahnung wann ich das mal reingeschriben habe, muss wohl verdammt spät gewesen sein o_O

Fazit:
Kleine Sache mega Auswirkung


Schönen ABend noch zusammen.


Gruß
Olli
 
You must log in or register to reply here.
Top Bottom