LXC Container starten nicht mehr!

Discussion in 'Proxmox VE (Deutsch)' started by mafe68, Aug 12, 2019.

  1. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Habe hier ein Problem, dass ich keinen einzigen Container mehr starten kann. Auch auf das WebIF kann ich nicht mehr zugreifen. Beim Starten den Proxmox sehe ich kurz die Meldung "pve-cluster service failed" Wo kann ich ansetzen um den Fehler zu beheben?
    Hier noch Info zum System:
    Code:
    root@pve:~# pveversion -v
    proxmox-ve: 5.4-2 (running kernel: 4.15.18-19-pve)
    pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
    pve-kernel-4.15: 5.4-7
    pve-kernel-4.15.18-19-pve: 4.15.18-45
    pve-kernel-4.15.18-15-pve: 4.15.18-40
    pve-kernel-4.15.18-9-pve: 4.15.18-30
    pve-kernel-4.15.18-8-pve: 4.15.18-28
    pve-kernel-4.15.18-7-pve: 4.15.18-27
    corosync: 2.4.4-pve1
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: not correctly installed
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.1-12
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-54
    libpve-guest-common-perl: 2.0-20
    libpve-http-server-perl: 2.0-14
    libpve-storage-perl: 5.0-44
    libqb0: 1.0.3-1~bpo9
    lvm2: 2.02.168-pve6
    lxc-pve: 3.1.0-3
    lxcfs: 3.0.3-pve1
    novnc-pve: 1.0.0-3
    proxmox-widget-toolkit: 1.0-28
    pve-cluster: 5.0-37
    pve-container: 2.0-40
    pve-docs: 5.4-2
    pve-edk2-firmware: 1.20190312-1
    pve-firewall: 3.0-22
    pve-firmware: 2.0-7
    pve-ha-manager: 2.0-9
    pve-i18n: 1.1-4
    pve-libspice-server1: 0.14.1-2
    pve-qemu-kvm: 3.0.1-4
    pve-xtermjs: 3.12.0-1
    qemu-server: 5.0-54
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.13-pve1~bpo2
    root@pve:~#
    

    Hier auch noch die Ausgabe von "systemctl status pve-cluster pveproxy pvedaemon"

    Code:
     root@pve:~# systemctl status pve-cluster pveproxy pvedaemon
    ● pve-cluster.service - The Proxmox VE cluster filesystem
       Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Mon 2019-08-12 11:26:42 CEST; 45min ago
      Process: 1819 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
          CPU: 23ms
    
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:42 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
    Aug 12 11:26:42 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    
    ● pveproxy.service - PVE API Proxy Server
       Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Mon 2019-08-12 11:26:48 CEST; 45min ago
      Process: 1864 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
          CPU: 2.547s
    
    Aug 12 11:26:45 pve systemd[1]: Starting PVE API Proxy Server...
    Aug 12 11:26:48 pve pveproxy[1864]: start failed - failed to get address info for: pve: Der Name oder der Dienst ist nicht bekannt
    Aug 12 11:26:48 pve pveproxy[1864]: start failed - failed to get address info for: pve: Der Name oder der Dienst ist nicht bekannt
    Aug 12 11:26:48 pve systemd[1]: pveproxy.service: Control process exited, code=exited status=255
    Aug 12 11:26:48 pve systemd[1]: Failed to start PVE API Proxy Server.
    Aug 12 11:26:48 pve systemd[1]: pveproxy.service: Unit entered failed state.
    Aug 12 11:26:48 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
    
    ● pvedaemon.service - PVE API Daemon
       Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
       Active: active (running) since Mon 2019-08-12 11:26:45 CEST; 45min ago
      Process: 1717 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
     Main PID: 1853 (pvedaemon)
        Tasks: 4 (limit: 4915)
       Memory: 123.9M
          CPU: 2.900s
       CGroup: /system.slice/pvedaemon.service
               ├─1853 pvedaemon
               ├─1856 pvedaemon worker
               ├─1857 pvedaemon worker
               └─1858 pvedaemon worker
    
    Aug 12 11:26:41 pve systemd[1]: Starting PVE API Daemon...
    Aug 12 11:26:45 pve pvedaemon[1853]: starting server
    Aug 12 11:26:45 pve pvedaemon[1853]: starting 3 worker(s)
    Aug 12 11:26:45 pve pvedaemon[1853]: worker 1856 started
    Aug 12 11:26:45 pve pvedaemon[1853]: worker 1857 started
    Aug 12 11:26:45 pve pvedaemon[1853]: worker 1858 started
    Aug 12 11:26:45 pve systemd[1]: Started PVE API Daemon.
    root@pve:~#
    
     
    #1 mafe68, Aug 12, 2019
    Last edited: Aug 12, 2019
  2. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Hier habe ich auch noch die Ausgabe von "journalctl"
    Code:
    root@pve:~# journalctl -b -u pve-cluster
    -- Logs begin at Mon 2019-08-12 11:26:32 CEST, end at Mon 2019-08-12 12:18:01 CEST. --
    Aug 12 11:26:41 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
    Aug 12 11:26:41 pve pmxcfs[1641]: [main] crit: Unable to get local IP address
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Aug 12 11:26:41 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:41 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:41 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Aug 12 11:26:41 pve pmxcfs[1745]: [main] crit: Unable to get local IP address
    Aug 12 11:26:41 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:41 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:42 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
    Aug 12 11:26:42 pve pmxcfs[1788]: [main] crit: Unable to get local IP address
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Aug 12 11:26:42 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:42 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
    Aug 12 11:26:42 pve pmxcfs[1803]: [main] crit: Unable to get local IP address
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Aug 12 11:26:42 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:42 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
    Aug 12 11:26:42 pve pmxcfs[1819]: [main] crit: Unable to get local IP address
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Aug 12 11:26:42 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
    Aug 12 11:26:42 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
    Aug 12 11:26:42 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Unit entered failed state.
    Aug 12 11:26:42 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'
     
  3. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,399
    Likes Received:
    132
    Ich nehme an, dass ist der wahre Grund für die Fehler: Die node kann ihre eigene IP<->Hostname Zuordnung nicht finden:
    * der name (`uname -r`) muss sich mittels Eintrag in der '/etc/hosts' auf eine IP auflösen lassen

    Hoffe das hilft weiter!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Da habe ich nichts dran gemacht!
    Das ist der Eintrag in der /etc/hosts/
    Code:
    127.0.0.1       localhost.localdomain localhost
    192.168.188.24  prox4m1.proxmox.com prox4m1 pvelocalhost
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     localhost ip6-localhost ip6-loopback
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    Hier auch noch der von der /etc/network/interfaces
    Code:
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).
    
    source /etc/network/interfaces.d/*
    
    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    allow-hotplug enp4s0
    iface enp4s0 inet manual
    auto vmbr0
    iface vmbr0 inet static
            address 192.168.188.24
            netmask 255.255.255.0
            gateway 192.168.188.1
            bridge_ports enp4s0
            bridge_stp off
            bridge_fd 0
    
    Das müsste so alles stimmen. Per SSH kann ich ganz normal zugreifen!
     
  5. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Mit dem Befehl "uname -r" bekomme ich die Kernel Version und den Host Namen der auch stimmt.
    Code:
    root@pve:~# uname -r
    4.15.18-19-pve
    
     
  6. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,399
    Likes Received:
    132
    `uname -n` hätte das sein sollen - Verzeihung!
    '/etc/hostname' enthält 'prox4m1'?

    `ping prox4m1` von dem system aus funktioniert?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Ja beide geben das richtige aus!
    Code:
    root@pve:~# uname -n
    pve
    root@pve:~# ping prox4m1
    PING prox4m1.proxmox.com (192.168.188.24) 56(84) bytes of data.
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=1 ttl=64 time=0.080 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=2 ttl=64 time=0.055 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=3 ttl=64 time=0.056 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=4 ttl=64 time=0.062 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=5 ttl=64 time=0.061 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=6 ttl=64 time=0.055 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=7 ttl=64 time=0.054 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=8 ttl=64 time=0.054 ms
    64 bytes from prox4m1.proxmox.com (192.168.188.24): icmp_seq=9 ttl=64 time=0.072 ms
    ^C
    --- prox4m1.proxmox.com ping statistics ---
    9 packets transmitted, 9 received, 0% packet loss, time 8174ms
    rtt min/avg/max/mdev = 0.054/0.061/0.080/0.008 ms
    
     
  8. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Möchte auch noch sagen das der Proxmox nicht auf der Proxmox ISO basiert sonder auch Debian Strech mit den Sourcen von Proxmox. Nur das System läuft schon seit einem Jahr ohne Probleme.
     
  9. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,399
    Likes Received:
    132
    ist nicht gleich:
    entweder den hostname richtig eintragen ('/etc/hostname' editieren und rebooten) - dort müsste dann 'prox4m1' stehen und nicht 'pve'
    oder (wenn der host tatsächlich 'pve' heißen soll - 'pve' zu den aliasen in '/etc/hosts' hinzufügen.

    hoffe das hilft!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    mafe68 likes this.
  10. mafe68

    mafe68 Member

    Joined:
    Oct 30, 2018
    Messages:
    43
    Likes Received:
    5
    Tausendfach Dank an dich! Das war der Fehler der das ganze verursacht hat. Nur weiß ich nicht warum es zu dem gekommen ist. Kann das sein, dass das durch das Update gekommen ist das ich gemacht habe? Nur nach dem Update und dem reboot ging noch alles. Kann ich das wo herausfinden was den Fehler verursacht hat?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice