Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

FUSE on OpenVZ VPS: can't open fuse device

postcdpostcd Member
edited September 2016 in Help

OpenVZ VPS configuration file contains:

DEVNODES="net/tun:rw fuse:rw "

DEVICES=""

VPS was restarted by vzctl

and when done from VPS: # stat /dev/fuse

File: `/dev/fuse'

Size: 0 Blocks: 0 IO Block: 4096 character special file

Device: 1bh/27d Inode: 16131188 Links: 1 Device type: a,e5

Access: (0644/crw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)

Access: 2016-09-22 16:05:22.406822397 +0200

Modify: 2016-09-22 16:05:22.406822397 +0200

Change: 2016-09-22 16:05:22.406822397 +0200

Birth: -

Done on the VPS:

mount -t davfs http://localhost/ /mnt/4shared.disk/

/sbin/mount.davfs: can't open fuse device

/sbin/mount.davfs: trying coda kernel file system

/sbin/mount.davfs: no free coda device to mount

Host node kernel should support fuse: 2.6.32***

"lsmod|grep fu" done from node is empty result

Please how to fix it?

// UPDATE: i did: modprobe fuse (on the node)
then it still not worked, then after: vzctl restart CTID
it started working. Not sure why fuse was not there, eems like mdule was not loaded after node reboot, not sure why

Comments

  • racksxracksx Member
    edited September 2016

    Maybe


    modprobe fuse

    would help :)

    Thanked by 1postcd
  • postcdpostcd Member
    edited September 2016

    @racksx said:
    modprobe fuse

    yes, indeed, thx, not sure why it was not loaded after node reboot, im sure i used fuse alread in VPSes

  • ktkt Member, Host Rep

    @postcd said:

    @racksx said:
    modprobe fuse

    yes, indeed, thx, not sure why it was not loaded after node reboot, im sure i used fuse alread in VPSes

    The modules aren't loaded on boot automatically regardless of if you were previously using it.

    Add it to /etc/rc.modules "modprobe fuse" and any other modules like tun etc.

    Thanked by 1postcd
  • postcdpostcd Member
    edited September 2016

    @kt said:
    Add it to /etc/rc.modules "modprobe fuse" and any other modules like tun etc.

    I do not have any such file/folder on my CentOS OVZ node.

    ls /etc|grep mod

    depmod.d

    modprobe.d

    Inside modprobe.d are some .conf files, like:

    cat openvz.conf

    options nf_conntrack ip_conntrack_disable_ve0=1

  • @postcd said:

    add it to/etc/modules.conf

  • postcdpostcd Member
    edited September 2016

    In my case this file also not existed on my CentOS 6 server.

    But OpenVZ says on their page: "you can also add it or into /etc/modules.conf (on RHEL see /etc/sysconfig/modules/ directory)"

    On other page they say: "The following method and directory location is applicable to CentOS v6. I am not sure about v5. The directory location may be different for that version."

    nano /etc/sysconfig/modules/ppp.modules

    !/bin/sh

    /sbin/modprobe ppp_async

    /sbin/modprobe ppp_deflate

    /sbin/modprobe ppp_mppe


    So in my case i have it now like this:

    cat /etc/sysconfig/modules/my.modules

    /sbin/modprobe ip_gre

    /sbin/modprobe nf_conntrack_proto_gre

    /sbin/modprobe tun

    /sbin/modprobe fuse

    stat /etc/sysconfig/modules/my.modules

    File: `/etc/sysconfig/modules/my.modules'

    Size: 99 Blocks: 8 IO Block: 4096 regular file

    Device: fd00h/64768d Inode: 33294690 Links: 1

    Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)

    Thx for help and advices racksx and kt

Sign In or Register to comment.