Fehler bei installation von PROXMOX auf Linux Debian

Discussion in 'Proxmox VE (Deutsch)' started by Kevin Kutschenreiter, Jan 10, 2019.

  1. Kevin Kutschenreiter

    Joined:
    Jan 10, 2019
    Messages:
    3
    Likes Received:
    0
    Sehr geehrte Damen und Herren,

    ich versuche seit gestern PROXMOX VE auf einem Linux Debian Stretch zu installieren.
    Dazu habe ich folgende Anleitung verwendet:

    pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch

    Nach der Eingabe des Befehls:

    apt install proxmox-ve postfix open-iscsi

    bekomme ich allerdings folgende Fehlermeldung:

    dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure):
    Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
    dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proxmox-ve:
    proxmox-ve hängt ab von pve-manager; aber:
    Paket pve-manager ist noch nicht konfiguriert.

    dpkg: Fehler beim Bearbeiten des Paketes proxmox-ve (--configure):
    Abhängigkeitsprobleme - verbleibt unkonfiguriert
    Fehler traten auf beim Bearbeiten von:
    pve-manager
    proxmox-ve
    E: Sub-process /usr/bin/dpkg returned an error code (1)



    Mein journalctl -xe log:

    -- Subject: Unit pve-cluster.service has begun start-up
    -- Defined-By: systemd
    --
    -- Unit pve-cluster.service has begun starting up.
    Jan 10 23:31:01 XXXX.strato systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
    Jan 10 23:31:01 XXXX.strato systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
    Jan 10 23:31:01 XXXX.strato pmxcfs[2396]: fuse: device not found, try 'modprobe fuse' first
    Jan 10 23:31:01 XXXX.strato pmxcfs[2396]: [main] crit: fuse_mount error: No such file or directory
    Jan 10 23:31:01 XXXX.strato pmxcfs[2396]: [main] crit: fuse_mount error: No such file or directory
    Jan 10 23:31:01 XXXX.strato pmxcfs[2396]: [main] notice: exit proxmox configuration filesystem (-1)
    Jan 10 23:31:01 XXXX.strato pmxcfs[2396]: [main] notice: exit proxmox configuration filesystem (-1)
    Jan 10 23:31:01 XXXX.strato systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Jan 10 23:31:01 XXXX.strato systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    -- Subject: Unit pve-cluster.service has failed
    -- Defined-By: systemd


    --
    -- Unit pve-cluster.service has failed.
    --
    -- The result is failed.
    Jan 10 23:31:01 XXXX.strato systemd[1]: pve-cluster.service: Unit entered failed state.
    Jan 10 23:31:01 XXXX.strato systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Jan 10 23:31:01 XXXX.strato systemd[1]: Starting The Proxmox VE cluster filesystem...
    -- Subject: Unit pve-cluster.service has begun start-up
    -- Defined-By: systemd


    --
    -- Unit pve-cluster.service has begun starting up.
    Jan 10 23:31:02 XXXX.strato pmxcfs[2404]: fuse: device not found, try 'modprobe fuse' first
    Jan 10 23:31:02 XXXX.strato pmxcfs[2404]: [main] crit: fuse_mount error: No such file or directory
    Jan 10 23:31:02 XXXX.strato pmxcfs[2404]: [main] notice: exit proxmox configuration filesystem (-1)
    Jan 10 23:31:02 XXXX.strato systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
    Jan 10 23:31:02 XXXX.strato pmxcfs[2404]: [main] crit: fuse_mount error: No such file or directory
    Jan 10 23:31:02 XXXX.strato systemd[1]: Failed to start The Proxmox VE cluster filesystem.
    -- Subject: Unit pve-cluster.service has failed
    -- Defined-By: systemd


    --
    -- Unit pve-cluster.service has failed.
    -- The result is failed.
    Jan 10 23:31:02 XXXX.strato systemd[1]: pve-cluster.service: Unit entered failed state.
    Jan 10 23:31:02 XXXX.strato systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
    Jan 10 23:31:02 XXXX.strato systemd[1]: Starting PVE Status Daemon...
    -- Subject: Unit pvestatd.service has begun start-up
    -- Defined-By: systemd
    -- Support: h.tt.ps://ww.w.d.ebian..or.g/su.pp.ort
    --
    -- Unit pvestatd.service has begun starting up.
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[1] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[1] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[2] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[2] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[3] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: ipcc_send_rec[3] failed: Connection refused
    Jan 10 23:31:02 XXXX.strato pvestatd[2420]: Unable to load access control list: Connection refused
    Jan 10 23:31:02 XXXX.strato systemd[1]: pvestatd.service: Control process exited, code=exited status=111
    Jan 10 23:31:02 XXXX.strato systemd[1]: Failed to start PVE Status Daemon.
    -- Subject: Unit pvestatd.service has failed
    -- Defined-By: systemd
    --
    -- Unit pvestatd.service has failed.
    --
    -- The result is failed.
    Jan 10 23:31:02 XXXX.strato systemd[1]: pvestatd.service: Unit entered failed state.
    Jan 10 23:31:02 XXXX.strato systemd[1]: pvestatd.service: Failed with result 'exit-code'.
    Jan 10 23:31:03 XXXX.strato pveproxy[2335]: worker exit
    Jan 10 23:31:03 XXXX.strato pveproxy[19882]: worker 2335 finished
    Jan 10 23:31:03 XXXX.strato pveproxy[19882]: starting 1 worker(s)
    Jan 10 23:31:03 XXXX.strato pveproxy[19882]: worker 2423 started
    Jan 10 23:31:03 XXXX.strato pveproxy[2423]: /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 1647.
    Jan 10 23:31:04 XXXX.strato pveproxy[2360]: worker exit




    Meine Vermutung ist das es an dem File-System liegt. Kann es eventuell sein das mein VServer-Anbieter mir den Zugriff auf mein Laufwerk einschränkt und ich aus diesem Grund bei der Installation nicht weiter komme?

    Vielen Dank für eure Hilfe!
     
  2. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    4,710
    Likes Received:
    313
    Hi,

    ich glaub eher das es am /etc/hosts und /etc/hostname liegt.

    Bitte mal die Dateien Schicken.
    Wenn eine Public IP in der hosts Datei ist bitte maskieren.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Kevin Kutschenreiter

    Joined:
    Jan 10, 2019
    Messages:
    3
    Likes Received:
    0
    /etc/hosts

    #::1 localhost ip6-localhost ip6-loopback
    #ff02::1 ip6-allnodes
    #ff02::2 ip6-allrouters

    127.0.0.1 localhost
    11.111.111.111 servername.stratoserver.net serveralias

    /etc/hostname

    servername.stratoserver.net
     
  4. dlimbeck

    dlimbeck Proxmox Staff Member
    Staff Member

    Joined:
    Aug 1, 2018
    Messages:
    137
    Likes Received:
    9
    in der /etc/hostname Datei nur <servername> eintragen und in /etc/hosts <ip> <fqdn> <servername> und optional noch einen alias dranhängen.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Kevin Kutschenreiter

    Joined:
    Jan 10, 2019
    Messages:
    3
    Likes Received:
    0
    /etc/hosts

    #::1 localhost ip6-localhost ip6-loopback
    #ff02::1 ip6-allnodes
    #ff02::2 ip6-allrouters

    127.0.0.1 localhost.localdomain localhost
    11.111.111.111 proxmox.stratoserver.net proxmox

    /etc/hostname

    proxmox

    Habe das jetzt mal so angepasst, bei der Installation komme ich aber trotzdem nicht weiter(immer noch der gleiche Fehler).
    Reboot habe ich auch durchgeführt.

    Freue mich natürlich über jeden weiteren Tipp!
     
  6. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,228
    Likes Received:
    109
    nur um sicher zu gehen: nach der umstellung muss noch rebooted werden!
    (alternativ der hostname via `hostname proxmox` gesetzt werden)

    was ist das output von
    `uname -n`
    `hostname`
    `hostname -f`
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  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