XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    new smb remote fails

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 2 Posters 289 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      gonzametal
      last edited by olivierlambert

      I have a clean install from sources in debian of Xen Orchestra. The product is not running as root.
      When I create a new smb remote to a Windows Share (with remote username and password) It fails with the following error

      {
        "errno": -13,
        "code": "EACCES",
        "syscall": "mkdir",
        "path": "/run/xo-server"
      }
      

      What can I do? Thanks

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        Did you follow the documentation for running as a non-root user?

        https://docs.xen-orchestra.com/installation#sudo

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          gonzametal @Danp
          last edited by olivierlambert

          @Danp Yes, I have tried all this stuff. Have modified all config.toml files found in the whole filesystem with useSudo = true add added in sudoers, xo_username ALL=(root) NOPASSWD: /bin/mount, /bin/umount, /bin/findmnt. Removed and recreated the remote, and same error

          remote.test
          {
            "id": "3ee175c8-41b7-410e-9607-463ca468a980"
          }
          {
            "errno": -13,
            "code": "EACCES",
            "syscall": "mkdir",
            "path": "/run/xo-server",
            "message": "EACCES: permission denied, mkdir '/run/xo-server'",
            "name": "Error",
            "stack": "Error: EACCES: permission denied, mkdir '/run/xo-server'"
          }
          

          Is there any filesystem permission missing?

          G 1 Reply Last reply Reply Quote 0
          • G Offline
            gonzametal @gonzametal
            last edited by

            @gonzametal I modified sudoers and could create the folder in the terminar but the error still there (I think because the syscall). I will install as root again to avoid this kind of issues in the future

            1 Reply Last reply Reply Quote 0
            • First post
              Last post