Unable to install new proxmox on Debian

Discussion in 'Proxmox VE: Installation and configuration' started by toxot, Feb 12, 2019.

  1. toxot

    toxot New Member

    Joined:
    May 11, 2016
    Messages:
    2
    Likes Received:
    0
    Hello,
    I found issiue installation failed every time.
    Im going according guide on wiki Install_Proxmox_VE_on_Debian_Stretch

    and what i see in result

    Do you have any idea thats wrong, and how it fix.
    Thanks.


    short
    Code:
    ....
    Creating config file /etc/samba/smb.conf with new version
    Setting up libdatrie1:amd64 (0.2.10-4+b1) ...
    Setting up libcrypt-openssl-random-perl (0.11-1+b3) ...
    Setting up libprotobuf-c1:amd64 (1.2.1-2) ...
    Processing triggers for initramfs-tools (0.130) ...
    update-initramfs: Generating /boot/initrd.img-4.9.0-8-amd64
    cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
    Setting up libmariadbclient18:amd64 (10.1.37-0+deb9u1) ...
    Setting up pve-kernel-4.15.18-11-pve (4.15.18-33) ...
    Examining /etc/kernel/postinst.d.
    run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.18-11-pve /boot/vmlinuz-4.15.18-11-pve
    run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.15.18-11-pve /boot/vmlinuz-4.15.18-11-pve
    update-initramfs: Generating /boot/initrd.img-4.15.18-11-pve
    cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
    run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.15.18-11-pve /boot/vmlinuz-4.15.18-11-pve
    Generating grub configuration file ...
    Found linux image: /boot/vmlinuz-4.15.18-11-pve
    Found initrd image: /boot/initrd.img-4.15.18-11-pve
    Found linux image: /boot/vmlinuz-4.9.0-8-amd64
    Found initrd image: /boot/initrd.img-4.9.0-8-amd64
    Found linux image: /boot/vmlinuz-4.9.0-7-amd64
    Found initrd image: /boot/initrd.img-4.9.0-7-amd64
    done
    Processing triggers for sgml-base (1.29) ...
    Setting up python-pkg-resources (33.1.1-1) ...
    Setting up smartmontools (6.5+svn4324-1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/smartd.service → /lib/systemd/system/smartd.service.
    Setting up libipset3:amd64 (6.30-2) ...
    Setting up uidmap (1:4.4-4.1) ...
    Setting up libtypes-serialiser-perl (1.0-1) ...
    Setting up open-iscsi (2.0.874-3~deb9u1) ...
    Created symlink /etc/systemd/system/sysinit.target.wants/iscsid.service → /lib/systemd/system/iscsid.service.
    Created symlink /etc/systemd/system/iscsi.service → /lib/systemd/system/open-iscsi.service.
    Created symlink /etc/systemd/system/sysinit.target.wants/open-iscsi.service → /lib/systemd/system/open-iscsi.service.
    Setting up libstatgrab10 (0.91-1+b1) ...
    Setting up libnspr4:amd64 (2:4.12-6) ...
    Setting up fonts-font-awesome (4.7.0~dfsg-1) ...
    Setting up pve-i18n (1.0-9) ...
    Setting up sqlite3 (3.16.2-5+deb9u1) ...
    Setting up bridge-utils (1.5-13+deb9u1) ...
    Setting up libopus0:amd64 (1.2~alpha2-1) ...
    Setting up libasound2:amd64 (1.1.3-5) ...
    Setting up libgraphite2-3:amd64 (1.3.10-1) ...
    Setting up rsync (3.1.2-1+deb9u1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/rsync.service → /lib/systemd/system/rsync.service.
    Setting up libboost-iostreams1.62.0:amd64 (1.62.0+dfsg-4) ...
    Setting up libxslt1.1:amd64 (1.1.29-2.1) ...
    Setting up libdevel-cycle-perl (1.11-2) ...
    Setting up libdevmapper-event1.02.1:amd64 (2:1.02.137-pve6) ...
    Setting up libprotobuf10:amd64 (3.0.0-9) ...
    Setting up libogg0:amd64 (1.3.2-1) ...
    Setting up libio-multiplex-perl (1.16-1) ...
    Setting up libfile-chdir-perl (0.1008-1) ...
    Setting up pve-docs (5.3-2) ...
    Setting up libtevent0:amd64 (0.9.31-1) ...
    Setting up libcrypt-openssl-rsa-perl (0.28-5) ...
    Setting up libxml-sax-base-perl (1.07-1) ...
    Setting up python-cffi-backend (1.9.1-2) ...
    Setting up libtcmalloc-minimal4 (2.5-2.2) ...
    Setting up libx11-xcb1:amd64 (2:1.6.4-3+deb9u1) ...
    Setting up libntlm0:amd64 (1.4-8) ...
    Setting up libpixman-1-0:amd64 (0.34.0-1) ...
    Setting up numactl (2.0.11-2.1) ...
    Setting up python-six (1.10.0-3) ...
    Setting up libgnutlsxx28:amd64 (3.5.8-5+deb9u4) ...
    Setting up liblwp-mediatypes-perl (6.02-1) ...
    Setting up libunwind8 (1.1-4.1) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Setting up libsocket6-perl (0.27-1+b1) ...
    Setting up libfaketime:amd64 (0.9.6-7+b1) ...
    Setting up python-protobuf (3.0.0-9) ...
    Setting up novnc-pve (1.0.0-2) ...
    Setting up liburi-perl (1.71-1) ...
    Setting up libanyevent-http-perl (2.23-1) ...
    Setting up libtirpc1:amd64 (0.2.5-1.2+deb9u1) ...
    Setting up libuuid-perl (0.27-1) ...
    Setting up ipset (6.30-2) ...
    Setting up libsnappy1v5:amd64 (1.1.3-3) ...
    Setting up thin-provisioning-tools (0.6.1-4+b1) ...
    Setting up python-enum34 (1.1.6-1) ...
    Setting up gdisk (1.0.1-1) ...
    Processing triggers for systemd (232-25+deb9u8) ...
    Setting up libltdl7:amd64 (2.4.6-2) ...
    Setting up libhtml-parser-perl (3.72-3) ...
    Setting up libpython2.7:amd64 (2.7.13-2+deb9u3) ...
    Setting up ebtables (2.0.10.4-3.5+b1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/ebtables.service → /lib/systemd/system/ebtables.service.
    update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
    Setting up libcorosync-common4:amd64 (2.4.4-pve1) ...
    Setting up libdigest-hmac-perl (1.03+dfsg-1) ...
    Setting up lxcfs (3.0.2-2) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/lxcfs.service → /lib/systemd/system/lxcfs.service.
    Setting up libfribidi0:amd64 (0.19.7-1+b1) ...
    Setting up libxcb-shm0:amd64 (1.12-1) ...
    Setting up libclone-perl (0.38-2+b1) ...
    Setting up libxrender1:amd64 (1:0.9.10-1) ...
    Setting up liblvm2app2.2:amd64 (2.02.168-pve6) ...
    Setting up libxml-xpathengine-perl (0.13-1) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    Setting up libnet-http-perl (6.12-1) ...
    Setting up libfcgi-bin (2.4.0-8.4+b1) ...
    Setting up libappconfig-perl (1.66-2) ...
    Setting up libc-dev-bin (2.24-11+deb9u3) ...
    Setting up pve-firmware (2.0-6) ...
    Setting up libthai-data (0.1.26-1) ...
    Setting up libconvert-asn1-perl (0.27-2) ...
    Setting up libreadline5:amd64 (5.2+dfsg-3+b1) ...
    Setting up libcaca0:amd64 (0.99.beta19-2+b2) ...
    Setting up libevent-2.0-5:amd64 (2.0.21-stable-3) ...
    Setting up postfix-sqlite (3.1.8-0+deb9u1) ...
    grep: /etc/postfix/dynamicmaps.cf: No such file or directory
    Adding sqlite map entry to /etc/postfix/dynamicmaps.cf
    Setting up libjson-perl (2.90-1) ...
    Setting up libnl-3-200:amd64 (3.2.27-2) ...
    Setting up faketime (0.9.6-7+b1) ...
    Setting up net-tools (1.60+git20161116.90da8a0-1) ...
    Setting up libvorbis0a:amd64 (1.3.5-4+deb9u2) ...
    Setting up x11-common (1:7.7+19) ...
    update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
    Setting up libqb0:amd64 (1.0.3-1~bpo9) ...
    Setting up python-ipaddress (1.0.17-1) ...
    Setting up pve-kernel-4.15 (5.3-2) ...
    Setting up manpages-dev (4.10-2) ...
    Setting up libc6-dev:amd64 (2.24-11+deb9u3) ...
    Setting up ifenslave (2.9) ...
    Setting up libwww-robotrules-perl (6.01-1) ...
    Setting up dtach (0.9-1) ...
    Setting up libapparmor-perl (2.11.0-3+deb9u2) ...
    Setting up cstream (3.0.0-1+b2) ...
    Setting up libauthen-sasl-perl (2.1600-1) ...
    Setting up libguard-perl (1.023-1+b2) ...
    Setting up attr (1:2.4.47-2+b2) ...
    Setting up libbabeltrace1:amd64 (1.5.1-1) ...
    Setting up fuse (2.9.7-1+deb9u2) ...
    update-initramfs: deferring update (trigger activated)
    Processing triggers for rsyslog (8.24.0-1) ...
    Setting up libboost-system1.62.0:amd64 (1.62.0+dfsg-4) ...
    Setting up liblzo2-2:amd64 (2.08-1.2+b2) ...
    Setting up pve-edk2-firmware (1.20181023-1) ...
    Setting up postfix (3.1.8-0+deb9u1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → /lib/systemd/system/postfix.service.
    Adding group `postfix' (GID 112) ...
    Done.
    Adding system user `postfix' (UID 107) ...
    Adding new user `postfix' (UID 107) with group `postfix' ...
    Not creating home directory `/var/spool/postfix'.
    Adding group `postdrop' (GID 113) ...
    Done.
    setting myhostname: cs492395
    setting alias maps
    setting alias database
    mailname is not a fully qualified domain name.  Not changing /etc/mailname.
    setting destinations: $myhostname, cs492395, localhost.localdomain, , localhost
    setting relayhost:
    setting mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
    setting mailbox_size_limit: 0
    setting recipient_delimiter: +
    setting inet_interfaces: all
    setting inet_protocols: all
    /etc/aliases does not exist, creating it.
    WARNING: /etc/aliases exists, but does not have a root alias.
    
    Postfix (main.cf) is now set up with a default configuration.  If you need to
    make changes, edit /etc/postfix/main.cf (and others) as needed.  To view
    Postfix configuration values, see postconf(1).
    
    After modifying main.cf, be sure to run 'service postfix reload'.
    
    Running newaliases
    Setting up rpcbind (0.2.3-0.6) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/rpcbind.service → /lib/systemd/system/rpcbind.service.
    Created symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket → /lib/systemd/system/rpcbind.socket.
    Setting up libavahi-common-data:amd64 (0.6.32-2) ...
    Setting up mailutils-common (1:3.1.1-1) ...
    Setting up libgssapi-perl (0.28-2+b4) ...
    Setting up libfdt1:amd64 (1.4.2-1) ...
    Setting up libxml-sax-perl (0.99+dfsg-2) ...
    update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::PurePerl with priority 10...
    update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
    
    Creating config file /etc/perl/XML/SAX/ParserDetails.ini with new version
    Setting up python-talloc (2.1.8-1) ...
    Setting up libterm-readline-gnu-perl (1.35-1) ...
    Setting up libgsasl7 (1.8.0-8+b2) ...
    Setting up python-setuptools (33.1.1-1) ...
    Setting up vncterm (1.5-3) ...
    Setting up cifs-utils (2:6.7-1) ...
    update-alternatives: using /usr/lib/x86_64-linux-gnu/cifs-utils/idmapwb.so to provide /etc/cifs-utils/idmap-plugin (idmap-plugin) in auto mode
    Setting up python-urllib3 (1.19.1-1) ...
    Setting up libbytes-random-secure-perl (0.28-1) ...
    Setting up fontconfig-config (2.11.0-6.7) ...
    Setting up libhttp-date-perl (6.02-1) ...
    Setting up python-chardet (2.3.0-2) ...
    Setting up pve-libspice-server1 (0.14.1-2) ...
    Setting up libcfg6:amd64 (2.4.4-pve1) ...
    Setting up libio-socket-inet6-perl (2.72-2) ...
    Setting up lzop (1.03-4+b1) ...
    Setting up python-tdb (1.3.11-2) ...
    Setting up libnet-ssleay-perl (1.80-1) ...
    Setting up libarchive13:amd64 (3.2.2-2+deb9u1) ...
    Setting up libboost-thread1.62.0:amd64 (1.62.0+dfsg-4) ...
    Setting up libboost-random1.62.0:amd64 (1.62.0+dfsg-4) ...
    Setting up libattr1-dev:amd64 (1:2.4.47-2+b2) ...
    Setting up nfs-common (1:1.3.4-2.1) ...
    
    Creating config file /etc/idmapd.conf with new version
    Adding system user `statd' (UID 108) ...
    Adding new user `statd' (UID 108) with group `nogroup' ...
    Not creating home directory `/var/lib/nfs'.
    Created symlink /etc/systemd/system/multi-user.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
    Created symlink /etc/systemd/system/remote-fs.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
    nfs-utils.service is a disabled or a static unit, not starting it.
    Setting up libldb1:amd64 (2:1.1.27-1+b1) ...
    Setting up libacl1-dev (2.2.52-3+b1) ...
    Setting up libvotequorum8:amd64 (2.4.4-pve1) ...
    Setting up libcpg4:amd64 (2.4.4-pve1) ...
    Setting up libflac8:amd64 (1.3.2-1) ...
    Setting up libjson-xs-perl (3.030-1) ...
    Setting up libnss3:amd64 (2:3.26.2-1.1+deb9u1) ...
    Setting up libharfbuzz0b:amd64 (1.4.2-1) ...
    Setting up apparmor (2.11.0-3+deb9u2) ...
    Created symlink /etc/systemd/system/sysinit.target.wants/apparmor.service → /lib/systemd/system/apparmor.service.
    update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
    diff: /var/lib/apparmor/profiles/.apparmor.md5sums: No such file or directory
    Setting up libnl-route-3-200:amd64 (3.2.27-2) ...
    Setting up xsltproc (1.1.29-2.1) ...
    Setting up libthai0:amd64 (0.1.26-1) ...
    Setting up libcmap4:amd64 (2.4.4-pve1) ...
    Setting up libquorum5:amd64 (2.4.4-pve1) ...
    Setting up libtemplate-perl (2.24-1.2+b3) ...
    Setting up libnet-dns-perl (1.07-1) ...
    Setting up criu (2.11.1-1~bpo90) ...
    Setting up libio-socket-ssl-perl (2.044-1) ...
    Setting up libhtml-tree-perl (5.03-2) ...
    Setting up libxtst6:amd64 (2:1.2.3-1) ...
    Setting up librados2 (10.2.11-2) ...
    Setting up libgoogle-perftools4 (2.5-2.2) ...
    Setting up guile-2.0-libs:amd64 (2.0.13+1-4) ...
    Setting up python-cryptography (1.7.1-3) ...
    Setting up libice6:amd64 (2:1.0.9-2) ...
    Setting up libfile-listing-perl (6.04-1) ...
    Setting up python-requests (2.12.4-1) ...
    Setting up libhttp-message-perl (6.11-1) ...
    Setting up libavahi-common3:amd64 (0.6.32-2) ...
    Setting up libnet-ldap-perl (1:0.6500+dfsg-1) ...
    Setting up libxml-libxml-perl (2.0128+dfsg-1+deb9u1) ...
    update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser with priority 50...
    update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with priority 50...
    update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
    Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
    Setting up libvorbisenc2:amd64 (1.3.5-4+deb9u2) ...
    Setting up python-rados (10.2.11-2) ...
    Setting up libcrypt-ssleay-perl (0.73.04-2) ...
    Setting up libcephfs1 (10.2.11-2) ...
    Setting up libkyotocabinet16v5:amd64 (1.2.76-4.2+b1) ...
    Setting up libbabeltrace-ctf1:amd64 (1.5.1-1) ...
    Setting up libhttp-negotiate-perl (6.00-2) ...
    Setting up python-ldb (2:1.1.27-1+b1) ...
    Setting up libmailutils5:amd64 (1:3.1.1-1) ...
    Setting up libibverbs1 (1.2.1-2) ...
    Setting up lxc-pve (3.1.0-2) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/lxc-monitord.service → /lib/systemd/system/lxc-monitord.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/lxc-net.service → /lib/systemd/system/lxc-net.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/lxc.service → /lib/systemd/system/lxc.service.
    Setting up libfontconfig1:amd64 (2.11.0-6.7+b1) ...
    Setting up libsm6:amd64 (2:1.2.2-1+b3) ...
    Setting up libnet-smtp-ssl-perl (1.04-1) ...
    Setting up libhtml-format-perl (2.12-1) ...
    Setting up python-cephfs (10.2.11-2) ...
    Setting up libradosstriper1 (10.2.11-2) ...
    Setting up libhttp-cookies-perl (6.01-1) ...
    Setting up python-openssl (16.2.0-1) ...
    Setting up librgw2 (10.2.11-2) ...
    Setting up ceph-fuse (10.2.11-2) ...
    Setting up libhttp-daemon-perl (6.01-1) ...
    Setting up librbd1 (10.2.11-2) ...
    Setting up librdmacm1 (1.1.0-2) ...
    Setting up mailutils (1:3.1.1-1) ...
    update-alternatives: using /usr/bin/frm.mailutils to provide /usr/bin/frm (frm) in auto mode
    update-alternatives: using /usr/bin/from.mailutils to provide /usr/bin/from (from) in auto mode
    update-alternatives: using /usr/bin/messages.mailutils to provide /usr/bin/messages (messages) in auto mode
    update-alternatives: using /usr/bin/movemail.mailutils to provide /usr/bin/movemail (movemail) in auto mode
    update-alternatives: using /usr/bin/readmsg.mailutils to provide /usr/bin/readmsg (readmsg) in auto mode
    update-alternatives: using /usr/bin/dotlock.mailutils to provide /usr/bin/dotlock (dotlock) in auto mode
    update-alternatives: using /usr/bin/mail.mailutils to provide /usr/bin/mailx (mailx) in auto mode
    Setting up python-rbd (10.2.11-2) ...
    Setting up libsndfile1:amd64 (1.0.27-3) ...
    Setting up libhtml-form-perl (6.03-1) ...
    Setting up libtotem-pg5:amd64 (2.4.4-pve1) ...
    Setting up libavahi-client3:amd64 (0.6.32-2) ...
    Setting up fontconfig (2.11.0-6.7+b1) ...
    Regenerating fonts cache... done.
    Setting up ceph-common (10.2.11-2) ...
    Setting up libcups2:amd64 (2.2.1-8+deb9u2) ...
    Setting up libcairo2:amd64 (1.14.8-1) ...
    Setting up libmailtools-perl (2.18-1) ...
    Setting up samba-libs:amd64 (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up glusterfs-common (3.8.8-1) ...
    Setting up python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up libpulse0:amd64 (10.0-1+deb9u1) ...
    Setting up libsmbclient:amd64 (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up smbclient (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up libpango-1.0-0:amd64 (1.40.5-1) ...
    Setting up corosync (2.4.4-pve1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/corosync.service → /lib/systemd/system/corosync.service.
    Setting up samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up glusterfs-client (3.8.8-1) ...
    Setting up libsdl1.2debian:amd64 (1.2.15+dfsg1-4) ...
    Setting up libpangoft2-1.0-0:amd64 (1.40.5-1) ...
    Setting up pve-qemu-kvm (2.12.1-1) ...
    Setting up libpangocairo-1.0-0:amd64 (1.40.5-1) ...
    Setting up librrd8:amd64 (1.6.0-1+b2) ...
    Setting up spiceterm (3.0-5) ...
    Setting up rrdcached (1.6.0-1+b2) ...
    Setting up librrds-perl:amd64 (1.6.0-1+b2) ...
    Setting up liblwp-protocol-https-perl (6.06-2) ...
    Setting up liblvm2cmd2.02:amd64 (2.02.168-pve6) ...
    Setting up libwww-perl (6.15-1) ...
    Setting up dmeventd (2:1.02.137-pve6) ...
    Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket.
    Setting up lvm2 (2.02.168-pve6) ...
    update-initramfs: deferring update (trigger activated)
    Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
    Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
    lvm2-lvmetad.service is a disabled or a static unit, not starting it.
    lvm2-lvmpolld.service is a disabled or a static unit, not starting it.
    lvm2-lvmetad.socket is a disabled or a static unit, not starting it.
    Stopping lvmetad, 'use_lvmetad=0' is set
    Setting up libxml-parser-perl (2.44-2+b1) ...
    Setting up libpve-apiclient-perl (2.0-5) ...
    Setting up libxml-sax-expat-perl (0.40-2) ...
    update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::Expat with priority 50...
    update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
    Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
    Setting up libxml-twig-perl (1:3.50-1) ...
    Setting up libnet-dbus-perl (1.1.0-4+b1) ...
    Setting up libpve-common-perl (5.0-45) ...
    Setting up pve-cluster (5.0-33) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/pve-cluster.service → /lib/systemd/system/pve-cluster.service.
    Setting up pve-xtermjs (3.10.1-1) ...
    Setting up libpve-http-server-perl (2.0-11) ...
    Setting up libpve-access-control (5.1-3) ...
    Setting up pve-ha-manager (2.0-6) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-crm.service → /lib/systemd/system/pve-ha-crm.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-lrm.service → /lib/systemd/system/pve-ha-lrm.service.
    Job for pve-ha-lrm.service failed because the control process exited with error code.
    See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details.
    pve-ha-lrm.service couldn't start.
    Setting up librados2-perl (1.0-6) ...
    Setting up pve-firewall (3.0-17) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/pve-firewall.service → /lib/systemd/system/pve-firewall.service.
    pvefw-logger.service is a disabled or a static unit, not starting it.
    Job for pve-firewall.service failed because the control process exited with error code.
    See "systemctl status pve-firewall.service" and "journalctl -xe" for details.
    pve-firewall.service couldn't start.
    Setting up libpve-storage-perl (5.0-37) ...
    Setting up libpve-guest-common-perl (2.0-20) ...
    Setting up qemu-server (5.0-46) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/qmeventd.service → /lib/systemd/system/qmeventd.service.
    Setting up pve-container (2.0-34) ...
    Setting up pve-manager (5.3-9) ...
    update failed - see /var/log/pveam.log for details
    Created symlink /etc/systemd/system/multi-user.target.wants/pvedaemon.service → /lib/systemd/system/pvedaemon.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/pveproxy.service → /lib/systemd/system/pveproxy.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/spiceproxy.service → /lib/systemd/system/spiceproxy.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/pvestatd.service → /lib/systemd/system/pvestatd.service.
    Created symlink /etc/systemd/system/getty.target.wants/pvebanner.service → /lib/systemd/system/pvebanner.service.
    Created symlink /etc/systemd/system/timers.target.wants/pvesr.timer → /lib/systemd/system/pvesr.timer.
    Created symlink /etc/systemd/system/timers.target.wants/pve-daily-update.timer → /lib/systemd/system/pve-daily-update.timer.
    Created symlink /etc/systemd/system/sysinit.target.wants/pvenetcommit.service → /lib/systemd/system/pvenetcommit.service.
    Created symlink /etc/systemd/system/pve-manager.service → /lib/systemd/system/pve-guests.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service → /lib/systemd/system/pve-guests.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 couldn't start.
    dpkg: error processing package pve-manager (--configure):
     subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of proxmox-ve:
     proxmox-ve depends on pve-manager; however:
      Package pve-manager is not configured yet.
    
    dpkg: error processing package proxmox-ve (--configure):
     dependency problems - leaving unconfigured
    Processing triggers for initramfs-tools (0.130) ...
    update-initramfs: Generating /boot/initrd.img-4.15.18-11-pve
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for systemd (232-25+deb9u8) ...
    Processing triggers for rsyslog (8.24.0-1) ...
    Processing triggers for pve-ha-manager (2.0-6) ...
    Errors were encountered while processing:
     pve-manager
     proxmox-ve
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    Code:
    Feb 12 04:12:19 cs492395 systemd[1]: Started PVE Cluster Ressource Manager Daemon.
    -- Subject: Unit pve-ha-crm.service has finished start-up
    -- Defined-By: systemd
    --
    --
    -- Unit pve-ha-crm.service has finished starting up.
    --
    -- The start-up result is done.
    Feb 12 04:12:19 cs492395 systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
    -- Subject: Unit pve-ha-lrm.service has begun start-up
    -- Defined-By: systemd
    
    --
    -- Unit pve-ha-lrm.service has begun starting up.
    Feb 12 04:12:20 cs492395 sshd[4055]: Connection closed by 114.5.22.170 port 55545 [preauth]
    Feb 12 04:12:20 cs492395 pve-ha-lrm[4146]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:20 cs492395 pve-ha-lrm[4146]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Control process exited, code=exited status=255
    Feb 12 04:12:20 cs492395 systemd[1]: Failed to start PVE Local HA Ressource Manager Daemon.
    -- Subject: Unit pve-ha-lrm.service has failed
    -- Defined-By: systemd
    -- Support:
    --
    -- Unit pve-ha-lrm.service has failed.
    --
    -- The result is failed.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Unit entered failed state.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Failed with result 'exit-code'.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:21 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:21 cs492395 systemd[1]: Starting Proxmox VE firewall logger...
    -- Subject: Unit pvefw-logger.service has begun start-up
    -- Defined-By: systemd
    -- Support: 
    --
    -- Unit pvefw-logger.service has begun starting up.
    Feb 12 04:12:21 cs492395 kernel: Netfilter messages via NETLINK v0.30.
    Feb 12 04:12:21 cs492395 systemd[1]: Started Proxmox VE firewall logger.
    -- Subject: Unit pvefw-logger.service has finished start-up
    -- Defined-By: systemd
    -- Support: 
    --
    -- Unit pvefw-logger.service has finished starting up.
    --
    -- The start-up result is done.
    Feb 12 04:12:21 cs492395 systemd[1]: Starting Proxmox VE firewall...
    -- Subject: Unit pve-firewall.service has begun start-up
    -- Defined-By: systemd
    -- Support: 
    
    Feb 12 04:12:21 cs492395 pvefw-logger[4240]: starting pvefw logger
    Feb 12 04:12:21 cs492395 pve-firewall[4241]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:21 cs492395 pve-firewall[4241]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:21 cs492395 systemd[1]: pve-firewall.service: Control process exited, code=exited status=255
    Feb 12 04:12:21 cs492395 systemd[1]: Failed to start Proxmox VE firewall.
    -- Subject: Unit pve-firewall.service has failed
    -- Defined-By: systemd
    
    -- Unit pveproxy.service has begun starting up.
    Feb 12 04:12:27 cs492395 pveproxy[4498]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:27 cs492395 pveproxy[4498]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:27 cs492395 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
    Feb 12 04:12:27 cs492395 systemd[1]: Failed to start PVE API Proxy Server.
    -- Subject: Unit pveproxy.service has failed
    
    
    root@cs492395:~# cat /var/log/pveam.log
    2019-02-12 04:12:23 starting update
    2019-02-12 04:12:23 start download ...
    2019-02-12 04:12:23 download finished: 200 OK
    2019-02-12 04:12:23 start download ..
    2019-02-12 04:12:23 download finished: 200 OK
    2019-02-12 04:12:23 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.4292.gz'
    2019-02-12 04:12:23 start download ...
    2019-02-12 04:12:24 download finished: 200 OK
    2019-02-12 04:12:24 start download ...
    2019-02-12 04:12:24 download finished: 200 OK
    2019-02-12 04:12:24 update failed: unable to unpack '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.4292.gz'
    
    
    syslog...
    
    eb 12 04:12:17 cs492395 pvecm[4048]: got inotify poll request in wrong process - disabling inotify
    Feb 12 04:12:17 cs492395 systemd[1]: Started The Proxmox VE cluster filesystem.
    Feb 12 04:12:17 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:17 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:18 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:18 cs492395 systemd[1]: Reached target PVE Storage Target.
    Feb 12 04:12:18 cs492395 systemd[1]: Started Proxmox VE watchdog multiplexer.
    Feb 12 04:12:18 cs492395 systemd[1]: Starting PVE API Daemon...
    Feb 12 04:12:18 cs492395 kernel: [  351.051427] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
    Feb 12 04:12:18 cs492395 watchdog-mux[4131]: Watchdog driver 'Software Watchdog', version 0
    Feb 12 04:12:19 cs492395 pvedaemon[4140]: starting server
    Feb 12 04:12:19 cs492395 pvedaemon[4140]: starting 3 worker(s)
    Feb 12 04:12:19 cs492395 pvedaemon[4140]: worker 4141 started
    Feb 12 04:12:19 cs492395 pvedaemon[4140]: worker 4142 started
    Feb 12 04:12:19 cs492395 pvedaemon[4140]: worker 4143 started
    Feb 12 04:12:19 cs492395 systemd[1]: Started PVE API Daemon.
    Feb 12 04:12:19 cs492395 systemd[1]: Starting PVE Cluster Ressource Manager Daemon...
    Feb 12 04:12:19 cs492395 pve-ha-crm[4145]: starting server
    Feb 12 04:12:19 cs492395 pve-ha-crm[4145]: status change startup => wait_for_quorum
    Feb 12 04:12:19 cs492395 systemd[1]: Started PVE Cluster Ressource Manager Daemon.
    Feb 12 04:12:19 cs492395 systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
    Feb 12 04:12:20 cs492395 pve-ha-lrm[4146]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:20 cs492395 pve-ha-lrm[4146]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Control process exited, code=exited status=255
    Feb 12 04:12:20 cs492395 systemd[1]: Failed to start PVE Local HA Ressource Manager Daemon.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Unit entered failed state.
    Feb 12 04:12:20 cs492395 systemd[1]: pve-ha-lrm.service: Failed with result 'exit-code'.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:20 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:21 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:21 cs492395 systemd[1]: Starting Proxmox VE firewall logger...
    Feb 12 04:12:21 cs492395 kernel: [  354.101270] Netfilter messages via NETLINK v0.30.
    Feb 12 04:12:21 cs492395 systemd[1]: Started Proxmox VE firewall logger.
    Feb 12 04:12:21 cs492395 systemd[1]: Starting Proxmox VE firewall...
    Feb 12 04:12:21 cs492395 pvefw-logger[4240]: starting pvefw logger
    Feb 12 04:12:21 cs492395 pve-firewall[4241]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:21 cs492395 pve-firewall[4241]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:21 cs492395 systemd[1]: pve-firewall.service: Control process exited, code=exited status=255
    Feb 12 04:12:21 cs492395 systemd[1]: Failed to start Proxmox VE firewall.
    Feb 12 04:12:21 cs492395 systemd[1]: pve-firewall.service: Unit entered failed state.
    Feb 12 04:12:21 cs492395 systemd[1]: pve-firewall.service: Failed with result 'exit-code'.
    Feb 12 04:12:22 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:22 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:22 cs492395 systemd[1]: Starting PVE Qemu Event Daemon...
    Feb 12 04:12:22 cs492395 systemd[1]: Started PVE Qemu Event Daemon.
    Feb 12 04:12:25 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:25 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:25 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:25 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:26 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:26 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:26 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:26 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:26 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:27 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:27 cs492395 systemd[1]: Starting PVE API Proxy Server...
    Feb 12 04:12:27 cs492395 pveproxy[4498]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:27 cs492395 pveproxy[4498]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 322.
    Feb 12 04:12:27 cs492395 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
    Feb 12 04:12:27 cs492395 systemd[1]: Failed to start PVE API Proxy Server.
    Feb 12 04:12:27 cs492395 systemd[1]: pveproxy.service: Unit entered failed state.
    Feb 12 04:12:27 cs492395 systemd[1]: pveproxy.service: Failed with result 'exit-code'.
    Feb 12 04:12:39 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:39 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:39 cs492395 systemd[1]: Stopping System Logging Service...
    
    Feb 12 04:12:39 cs492395 systemd[1]: Stopped System Logging Service.
    Feb 12 04:12:39 cs492395 systemd[1]: Starting System Logging Service...
    
    Feb 12 04:12:39 cs492395 systemd[1]: Started System Logging Service.
    Feb 12 04:12:40 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:40 cs492395 systemd[1]: Reloading.
    Feb 12 04:12:40 cs492395 systemd[1]: Stopping PVE Cluster Ressource Manager Daemon...
    Feb 12 04:12:41 cs492395 pve-ha-crm[4145]: received signal TERM
    Feb 12 04:12:41 cs492395 pve-ha-crm[4145]: server received shutdown request
    Feb 12 04:12:41 cs492395 pve-ha-crm[4145]: server stopped
    Feb 12 04:12:42 cs492395 systemd[1]: Stopped PVE Cluster Ressource Manager Daemon.
    Feb 12 04:12:42 cs492395 systemd[1]: Starting PVE Cluster Ressource Manager Daemon...
    Feb 12 04:12:42 cs492395 pve-ha-crm[9555]: starting server
    Feb 12 04:12:42 cs492395 pve-ha-crm[9555]: status change startup => wait_for_quorum
    Feb 12 04:12:42 cs492395 systemd[1]: Started PVE Cluster Ressource Manager Daemon.
    Feb 12 04:17:01 cs492395 CRON[9700]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Feb 12 04:21:28 cs492395 systemd[1]: Starting Cleanup of Temporary Directories...
    Feb 12 04:21:28 cs492395 systemd[1]: Started Cleanup of Temporary Directories.
    
    
    
    
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,484
    Likes Received:
    314
    How much RAM do you have?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. toxot

    toxot New Member

    Joined:
    May 11, 2016
    Messages:
    2
    Likes Received:
    0
    Yes this issue is in amount of ram - in this VM was -1Gb, but in fact previous times it was enough for test purpose.
    Actually firstly im unable install on new server - i tried to check on my test VM and get same result, so i've tried couple time ..
    Thanks for advice! Now it works
     
  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