cannot access /etc/pve: Transport endpoint not connected

Discussion in 'Proxmox VE: Installation and configuration' started by carlosho17, Nov 18, 2011.

  1. carlosho17

    carlosho17 New Member

    Joined:
    Dec 6, 2010
    Messages:
    11
    Likes Received:
    1
    Hi
    I'm getting this error when running vzlist or anything related to access /etc/pve:

    Unable to open /etc/pve/openvz/200.conf: Transport endpoint is not connected
    Unable to open /etc/pve/openvz/201.conf: Transport endpoint is not connected
    Unable to open /etc/pve/openvz/202.conf: Transport endpoint is not connected
    Unable to open /etc/pve/openvz/203.conf: Transport endpoint is not connected


    The containers kept running , I'm looking for a command to restore /etc/pve
    mount -o remount /etc/pve yields

    /bin/sh: /dev/fuse: Permission denied
    cxxxxxxxxxxxx:~(12:15:43)> l -d /dev/fuse
    crw-rw---- 1 root fuse 10, 229 Oct 24 17:50 /dev/fuse




    It's an installation based on squeeze with RAID-1, LVM and ext4 por pve-data and pve-root



    pve-manager: 2.0-7 (pve-manager/2.0/de5d8ab1)
    running kernel: 2.6.32-6-pve
    proxmox-ve-2.6.32: 2.0-46
    pve-kernel-2.6.32-6-pve: 2.6.32-46
    lvm2: 2.02.86-1pve1
    clvm: 2.02.86-1pve1
    corosync-pve: 1.4.1-1
    openais-pve: 1.1.4-1
    libqb: 0.5.1-1
    redhat-cluster-pve: 3.1.7-1
    pve-cluster: 1.0-9
    qemu-server: 2.0-2
    pve-firmware: 1.0-13
    libpve-common-perl: 1.0-6
    libpve-access-control: 1.0-1
    libpve-storage-perl: 2.0-4
    vncterm: 1.0-2
    vzctl: 3.0.29-3pve2
    vzdump: 1.2.6-1
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 0.15.0-1
    ksm-control-daemon: 1.1-1

    Here's the output of df -h

    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/pve-root 92G 1.2G 86G 2% /
    tmpfs 3.9G 0 3.9G 0% /lib/init/rw
    udev 10M 252K 9.8M 3% /dev
    tmpfs 3.9G 3.1M 3.9G 1% /dev/shm
    /dev/mapper/pve-data 367G 12G 337G 4% /var/lib/vz
    df: `/etc/pve': Transport endpoint is not connected

    And /etc/fstab

    proc /proc proc defaults 0 0
    /dev/mapper/pve-root / ext4 noatime,relatime,errors=remount-ro 0 1
    /dev/mapper/pve-data /var/lib/vz ext4 noatime,relatime 0 2
    /dev/mapper/pve-swap none swap sw 0 0
    /dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto 0 0

    And the output of mount

    /dev/mapper/pve-root on / type ext4 (rw,noatime,relatime,errors=remount-ro)
    tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    udev on /dev type tmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
    /dev/mapper/pve-data on /var/lib/vz type ext4 (rw,noatime,relatime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    /dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
    beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
    container on /proc/vz/container type cgroup (rw,name=container)
    fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)

    Thanks for any clue
     
  2. carlosho17

    carlosho17 New Member

    Joined:
    Dec 6, 2010
    Messages:
    11
    Likes Received:
    1
    /etc/init.d/pve-cluster restart restored /etc/pve
     
  3. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    15,939
    Likes Received:
    243
    pve-manger version should be 2.0-10, please update.
     
  4. MichaelA

    MichaelA New Member

    Joined:
    Jan 4, 2012
    Messages:
    13
    Likes Received:
    0
    Same issue on version 2.0-18

    And the directory /etc/pve particulary empty:

    Where the rest files could gone (they were before adding this node to cluster)?
    And there is no way to create there anything: permission denied (under root, whith no chattr +i and rw mount).

    Restarting cluster doesn't helps.

    Maybe this gonna help to figure this out:

     
    #4 MichaelA, Jan 4, 2012
    Last edited: Jan 4, 2012
  5. Faye

    Faye Member

    Joined:
    Jan 2, 2012
    Messages:
    39
    Likes Received:
    0
    /etc/pve is created from a userspace program pmxcfs which generates the data from /var/lib/pve-cluster/config.db
     
  6. MichaelA

    MichaelA New Member

    Joined:
    Jan 4, 2012
    Messages:
    13
    Likes Received:
    0
    Thank you. Mount with pmxcfs works like a charm.
    But why I still can't create a file/dir in /etc/pve ?
     
  7. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    15,939
    Likes Received:
    243
    What error do you get now?
     
  8. MichaelA

    MichaelA New Member

    Joined:
    Jan 4, 2012
    Messages:
    13
    Likes Received:
    0
    Will explain from begining.

    I want to connect two nodes: node1a (v.2.0-18) and node1b (v.2.0-18)

    What I've got at node1a:
    What I've got at node1b:
    Now I try to add a node1b to cluster:
    And what I've got at node1a:
    And on node1b:
     
  9. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    15,939
    Likes Received:
    243
    Are both nodes in the same physical network? And your switch supports IP multicast?
     
  10. MichaelA

    MichaelA New Member

    Joined:
    Jan 4, 2012
    Messages:
    13
    Likes Received:
    0
    Both servers are in different networks (and even in different cities) and no multicast available. Don't I have chances? :(
     

Share This Page

  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