error with pve cluster and pve manager

Discussion in 'Proxmox VE: Installation and configuration' started by hec, Oct 3, 2011.

  1. hec

    hec Member

    Joined:
    Jan 8, 2009
    Messages:
    205
    Likes Received:
    7
    Today i run an apt-get update && apt-get dist-upgrade and then proxmox has a broken package.

    Code:
    Setting up pve-cluster (1.0-8) ...Starting pve cluster filesystem : pve-clusterfuse: mountpoint is not empty
    fuse: if you are sure this is safe, use the 'nonempty' mount option
     (warning).
    invoke-rc.d: initscript pve-cluster, action "start" failed.
    dpkg: error processing pve-cluster (--configure):
     subprocess installed post-installation script returned error exit status 255
    configured to not write apport reports
                                          dpkg: dependency problems prevent configuration of pve-manager:
     pve-manager depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing pve-manager (--configure):
     dependency problems - leaving unconfigured
    configured to not write apport reports
                                          Errors were encountered while processing:
     pve-cluster
     pve-manager
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    
    
    
    How can this be fixed?
     
  2. bread-baker

    bread-baker Member

    Joined:
    Mar 6, 2010
    Messages:
    432
    Likes Received:
    0
    try restarting and boot system maintenance mode [ 2-nd line in grub here ].

    log in as root.

    then

    Code:
    ls -l /etc/pve
    
    AFAIK that should be empty. fuse file systems give that warning when there is an attempt to mount on a directory which is not empty.

    if it is not empty I would do this

    Code:
    mv /etc/pve /etc/pve.old
    mkdir /etc/pve
    
    then resume normal boot by pressing ctl+d
     
  3. hec

    hec Member

    Joined:
    Jan 8, 2009
    Messages:
    205
    Likes Received:
    7
    I solved this problem.

    A part of the problem are the apache2 certs.
     
  4. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,459
    Likes Received:
    310
    What problem?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    Hello all i am new here and having difficulty getting proxmox 2.0 beta to install on Debian sqeeze. Getting the same error see below, I have tried the recovery boot and /etc/pve is empty. I would like to know how the original other fixed this problem as
    I fixed this problem is not really enough infos. He mentions something about apache certs, but it is very unclear how he manged to fix this.

    I have followed the install doc to the letter and am running the correct kernel.
    Code:
    uname -a
    Linux debian 2.6.32-6-pve #1 SMP Mon Sep 26 10:35:47 CEST 2011 x86_64 GNU/Linux
    NOTE get the following error while updating the kernel but the system seems fine and i have working network.
    Code:
                            Setting up pve-kernel-2.6.32-6-pve (2.6.32-46) ...  
     update-initramfs: Generating /boot/initrd.img-2.6.32-6-pve  
     W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3  
     W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3  
     W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3  
     

    My sources.lists looks like this do i need contrib at the end of the line? or could i just leave sources.list as is, and just add the last PVE repository? NOTE i also disabled the Volitle repsitories all seemed to make no difference and i continue getting errors.

    Code:
    ##### Commented out for PVE
    #deb http://ftp3.nrc.ca/debian/ squeeze main
    #deb-src http://ftp3.nrc.ca/debian/ squeeze main
    #####
    
    # for PVE
    deb http://ftp.at.debian.org/debian squeeze main contrib
    
    ##### Commented out for PVE
    #deb http://security.debian.org/ squeeze/updates main
    #deb-src http://security.debian.org/ squeeze/updates main
    #####
    
    # For PVE
    deb http://security.debian.org/ squeeze/updates main contrib
    
    ##### Commented out for PVE
    # squeeze-updates, previously known as 'volatile'
    #deb http://ftp3.nrc.ca/debian/ squeeze-updates main
    #deb-src http://ftp3.nrc.ca/debian/ squeeze-updates main
    #####
    
    # PVE packages provided by proxmox.com
    deb http://download.proxmox.com/debian squeeze pve
    
    
    The errors mentioned above

    Code:
    root@debian:/home/c0mputerking# aptitude install proxmox-ve-2.6.32
    The following NEW packages will be installed:
      apache2{a} apache2-mpm-prefork{a} apache2-utils{a} apache2.2-common{a}
     
    <...SNIP...>
    Setting up rrdcached (1.4.3-1) ...
    Starting RRDtool data caching daemon: rrdcached.
    Setting up pve-cluster (1.0-9) ...
    Starting pve cluster filesystem : pve-cluster (warning).
    invoke-rc.d: initscript pve-cluster, action "start" failed.
    dpkg: error processing pve-cluster (--configure):
     subprocess installed post-installation script returned error exit status 255
    configured to not write apport reports
                                          dpkg: dependency problems prevent configuration of libpve-access-control:
     libpve-access-control depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing libpve-access-control (--configure):
     dependency problems - leaving unconfigured
    Setting up libopenais3-pve (1.1.4-1) ...
    configured to not write apport reports
                                          Setting up corosync-pve (1.4.1-1) ...
    Setting up openais-pve (1.1.4-1) ...
    dpkg: dependency problems prevent configuration of redhat-cluster-pve:
     redhat-cluster-pve depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing redhat-cluster-pve (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of clvm:
     clvm depends on redhat-cluster-pve; however:
      Package redhat-cluster-pve is not configured yet.
    dpkg: error processing clvm (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of libpve-storage-perl:
     libpve-storage-perl depends on clvm; however:
      Package clvm is not configured yet.
    dpkg: error processing libpve-storage-perl (--configure):
     dependency problems - leaving unconfigured
    Setting up libvncserver0 (0.9.7-2+b1) ...
    configured to not write apport reports
                                          configured to not write apport reports
                                                                                configured to not write apport reports
                                      Setting up pve-firmware (1.0-13) ...
    Setting up vncterm (1.0-2) ...
    Setting up libaio1 (0.3.107-7) ...
    Setting up pve-qemu-kvm (0.15.0-1) ...
    dpkg: dependency problems prevent configuration of qemu-server:
     qemu-server depends on libpve-storage-perl; however:
      Package libpve-storage-perl is not configured yet.
     qemu-server depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
     qemu-server depends on redhat-cluster-pve; however:
      Package redhat-cluster-pve is not configured yet.
    dpkg: error processing qemu-server (--configure):
     dependency problems - leaving unconfigured
    Setting up vlan (1.9-3) ...
    configured to not write apport reports
                                          dpkg: dependency problems prevent configuration of pve-manager:
     pve-manager depends on qemu-server (>= 1.1-1); however:
      Package qemu-server is not configured yet.
     pve-manager depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
     pve-manager depends on libpve-storage-perl; however:
      Package libpve-storage-perl is not configured yet.
     pve-manager depends on libpve-access-control; however:
      Package libpve-access-control is not configured yet.
     pve-manager depends on redhat-cluster-pve; however:
      Package redhat-cluster-pve is not configured yet.
    dpkg: error processing pve-manager (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
     proxmox-ve-2.6.32 depends on pve-manager; however:
      Package pve-manager is not configured yet.
     proxmox-ve-2.6.32 depends on qemu-server; however:
      Package qemu-server is not configured yet.
    dpkg: error processing proxmox-ve-2.6.32 (--configure):
     dependencyconfigured to not write apport reports
                                                     configured to not write apport reports
            problems - leaving unconfigured
    Setting up libbsd-resource-perl (1.2904-1) ...
    Errors were encountered while processing:
     pve-cluster
     libpve-access-control
     redhat-cluster-pve
     clvm
     libpve-storage-perl
     qemu-server
     pve-manager
     proxmox-ve-2.6.32
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install.  Trying to recover:
    Setting up pve-cluster (1.0-9) ...
    Starting pve cluster filesystem : pve-cluster (warning).
    invoke-rc.d: initscript pve-cluster, action "start" failed.
    dpkg: error processing pve-cluster (--configure):
     subprocess installed post-installation script returned error exit status 255
    dpkg: dependency problems prevent configuration of pve-manager:
     pve-manager depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing pve-manager (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
     proxmox-ve-2.6.32 depends on pve-manager; however:
      Package pve-manager is not configured yet.
    dpkg: error processing proxmox-ve-2.6.32 (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of libpve-access-control:
     libpve-access-control depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing libpve-access-control (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of qemu-server:
     qemu-server depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing qemu-server (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of redhat-cluster-pve:
     redhat-cluster-pve depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing redhat-cluster-pve (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of clvm:
     clvm depends on redhat-cluster-pve; however:
      Package redhat-cluster-pve is not configured yet.
    dpkg: error processing clvm (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of libpve-storage-perl:
     libpve-storage-perl depends on clvm; however:
      Package clvm is not configured yet.
    dpkg: error processing libpve-storage-perl (--configure):
     dependency problems - leaving unconfigured
    Errors were encountered while processing:
     pve-cluster
     pve-manager
     proxmox-ve-2.6.32
     libpve-access-control
     qemu-server
     redhat-cluster-pve
     clvm
     libpve-storage-perl
    
    PS I also get an error about mounting none on dev failed hoping it is not related, and cannot find any mention of it in the logs just on the console during boot up.
     
  6. bread-baker

    bread-baker Member

    Joined:
    Mar 6, 2010
    Messages:
    432
    Likes Received:
    0
    I do not know the cause of the problem but I would boot maintenance mode and run the update.

    from what I see at runlevel 1 /etc/init.d/pve* stuff is not started. so maybe 'aptitude safe-upgrade' will finish the update.

    for the tg3 firmware try installing firmware-linux-free . if that does not work try adding non-free to sources.list and install firmware-linux-nonfree .
     
  7. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    I already tried installing from maintenance mode, and just tried a aptitude safe-upgrade which yielded the same errors.

    As for the firmware-linux-free i get this so i just quit the installer as i think i should stick to the pve firmware right?

    aptitude install firmware-linux-free
    The following NEW packages will be installed:
    firmware-linux-free
    The following partially installed packages will be configured:
    clvm libpve-access-control libpve-storage-perl proxmox-ve-2.6.32 pve-cluster pve-manager
    qemu-server redhat-cluster-pve
    0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    Need to get 151 kB of archives. After unpacking 283 kB will be used.
    The following packages have unmet dependencies:
    pve-firmware: Conflicts: firmware-linux-free but 2.6.32-35squeeze2 is to be installed.
    The following actions will resolve these dependencies:

    Remove the following packages:
    1) proxmox-ve-2.6.32
    2) pve-firmware



    Accept this solution? [Y/n/q/?] q
    Abandoning all efforts to resolve these dependencies.
    Abort.
     
  8. bread-baker

    bread-baker Member

    Joined:
    Mar 6, 2010
    Messages:
    432
    Likes Received:
    0
    it is good you choose not to remove those.... and you probably can ignore the tg3 warnings as your network is working.

    I do not have another suggestion regarding the partially installed packages .
     
  9. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    So it works for everyone but me on Debian squeeze? this is a fresh install on real hardware too!
     
  10. bread-baker

    bread-baker Member

    Joined:
    Mar 6, 2010
    Messages:
    432
    Likes Received:
    0
    sounds like you've run into a bug. the thing is to report it .

    the devs are I think mostly from Europe, so wait until 9am or so their time to expect a response.

    also there is a proxmox tracking system. use it to check on and report this issue.
     
  11. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    How do i report this possible bug?
     
  12. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,459
    Likes Received:
    310
    Do you use DHCP? If so, that will not work. You need to install debian using a fixed network address.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    Thank you for the reply, and I did use DHCP (the default) during the install but i have since switched to static now, but still get the same error when tryng to install proxmox. Any reason this might not be working even after being switched to static?

    Here is my /etc/networking/interfaces

    Code:
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).
    
    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    #allow-hotplug eth0
    #NetworkManager
    #auto eth0
    #iface eth0 inet dhcp
    
    auto eth0
    iface eth0 inet static
            address 192.168.1.2
            network 192.168.1.0
            broadcast 192.168.1.255
            netmask 255.255.255.0
            gateway 192.168.1.1
    
    and my hosts file

    Code:
    127.0.0.1       sun     localhost.localdomain   localhost
    
    192.168.1.2     sun     sun.xxxxx.com     sun
    
    127.0.1.1       sun.xxxxxx.com     sun
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    
     
  14. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,459
    Likes Received:
    310
    Your hosts file looks broken. Do not use 'sun' as name for localhost. And what is the output of

    # hostname
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. iti-asi

    iti-asi Member

    Joined:
    Jul 14, 2009
    Messages:
    52
    Likes Received:
    0
    To c0mputerking:
    I've done an instalation from a clean squeeze instalation like you (with dhcp and modifying /etc/network/interface after) and I got the same trouble.

    The trouble was with pve-cluster that couldn't start.

    I've commented in /var/lib/dpkg/info/pve-cluster.postinst those line (remember to uncomment it after you solved it):
    Code:
            if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then
                    invoke-rc.d pve-cluster $_dh_action || exit $?
            else
                    /etc/init.d/pve-cluster $_dh_action || exit $?
            fi
    
    and try to start pve-cluster manually and continue the instalation with apt-get install -f

    My trouble was with an error about bad resolution name and updating the /etc/hosts with the hostname and IP solved it.

    Hope it could help.
     
  16. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    The output of my hostname is
    Code:
    ~$ hostname
    sun
    
    I thought my host file looked pretty standard can you recommend what the host file should look like?

    also as an aside apache complained about not being able to determine a hostname and that it would use 127.0.0.1 each time it started up. I fixed this error by placing a ServerName sun.xxxxxxx.com directive in my httpd.conf file.

    I have not tried commenting out the lines in pve-cluster-post.inst file yet, would this be necessary even with a properly formed hostfile and correct name resolution.
     
  17. rmoglia

    rmoglia Member

    Joined:
    Jul 28, 2009
    Messages:
    83
    Likes Received:
    0
    I pass from the same problem and edited my hosts file and fix the machine name according with my local test ip and working and pass dpkg installer rotines.
    root@proxmox:~# cat /etc/hosts
    127.0.0.1 localhost
    192.168.0.5 proxmox.xxxx.sytes.net proxmox

    ps i modified eth0 into vmbr0 like proxmox 1.X series. i´m testing now and will be put results here.
     
  18. c0mputerking

    c0mputerking Member

    Joined:
    Oct 5, 2011
    Messages:
    172
    Likes Received:
    3
    Yep modified my hosts file and got past the errors thanks everyone for your help. I would mark this thread SOLVED but it is not mine
     
  19. timeJunky

    timeJunky New Member

    Joined:
    Dec 21, 2010
    Messages:
    23
    Likes Received:
    0
    I couldn't get rid of the errors :(

    Changed /etc/hosts... but it didn't help. Any ideas?

    Code:
    pm:/home/npe# aptitude install -f
    
    ...
    
    pm:/home/npe# screen -S upgrade redhat-cluster-pve
     clvm
     libpve-storage-perl
     qemu-server
     pve-manager
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install.  Trying to recover:
    Setting up pve-cluster (1.0-9) ...
    Starting pve cluster filesystem : pve-clusterfuse: mountpoint is not empty
    fuse: if you are sure this is safe, use the 'nonempty' mount option
     (warning).
    invoke-rc.d: initscript pve-cluster, action "start" failed.
    dpkg: error processing pve-cluster (--configure):
     subprocess installed post-installation script returned error exit status 255
    dpkg: dependency problems prevent configuration of pve-manager:
     pve-manager depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing pve-manager (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of libpve-access-control:
     libpve-access-control depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing libpve-access-control (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of qemu-server:
     qemu-server depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing qemu-server (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of redhat-cluster-pve:
     redhat-cluster-pve depends on pve-cluster; however:
      Package pve-cluster is not configured yet.
    dpkg: error processing redhat-cluster-pve (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of clvm:
     clvm depends on redhat-cluster-pve; however:
      Package redhat-cluster-pve is not configured yet.
    dpkg: error processing clvm (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of libpve-storage-perl:
     libpve-storage-perl depends on clvm; however:
      Package clvm is not configured yet.
    dpkg: error processing libpve-storage-perl (--configure):
     dependency problems - leaving unconfigured
    Errors were encountered while processing:
     pve-cluster
     pve-manager
     libpve-access-control
     qemu-server
     redhat-cluster-pve
     clvm
     libpve-storage-perl
    
    
    
     
  20. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,459
    Likes Received:
    310
    Please remove all file inside /etc/pve - then try again.
     
    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