Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

BRRABill

Has anyone updated to 5.1 yet?

I tried today, and it kept me on 5.0.

Is it under next-release or stable? Or something entirely different?

FORGET IT I FIGURED IT OUT.

I must have been on next-release or something.

I ran it again with no issues.

DustinB3403

I updated.

BRRABill

@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

I updated.

A reboot fixed my issue, finally.

Here I thought that was just a Windows thing.

Fetakungen

hi, i have trouble gettings cifs to work. Smbclient etc is installed i have tried 3 diffrent installs 15.10 as 16.04 everything else is working fine the error i get is

"Create Remote connection has been closed"

The smb server is a AD member freenas.

Also the login looks like this as of 5.x

DustinB3403

@Fetakungen

The login screen is a known issue

As for connecting to your remote store, you mean SMB, correct?

You may need to manually connect to the share from the XO console.

scottalanmiller

@Fetakungen welcome to the community!

Fetakungen

@scottalanmiller

Thanks

@DustinB3403
I see i havent looked into it but i guess it's simply looking for the logo in the wrong place / the logo is missing.

Well mounting it directly in the OS is no problem but i want to have a OVF that fit for fight after install and of course if want to be able to use the intergrated smb mount just because it should work.
Also this removes the need of linux knowledge.

DustinB3403

I personally use NFS shares for XO, just very simple to setup and manage.

Do you need to use SMB for this, or could you convert the share to an NFS and connect that way? It should work to connect using either method, but we'd need to see what is occurring when you attempt to connect.

Fetakungen

@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

Do you need to use SMB for this, or could you convert the share to an NFS and connect that way? It should work to connect using either method, but we'd need to see what is occurring when you attempt to connect.

My log knowledge regarding XO is a bit rusty what logs should i check ?

I Could use NFS , Right now this is more about that i should work than i need it =).

DustinB3403

@Fetakungen When you're in the web console, at the screen where you are attempting to connect to the SMB share, what happens? You can take a screenshot for us.

Fetakungen

@DustinB3403

The nas says nothing about access denied etc.

In 4.x the error message was diffrent but well result the same.

DustinB3403

@Fetakungen Can you access the share from any other systems using the same credentials?

Fetakungen

@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@Fetakungen Can you access the share from any other systems using the same credentials?

Yes , im using the nas with many servers and as an end user myself. I have tried various creds. From user to Admin.

DustinB3403

Try this from the console

sudo mkdir ~/mnt
sudo mount -t cifs //myserver_ip_address/myshare ~/mnt -o username=samb_user,noexec

Filling in your details.

Fetakungen

@DustinB3403

It works as expected.
I realized i hadn't installed cifs-utils when i tried to mount.It's installed now, unfortunetly the error remains..

DustinB3403

@Fetakungen So if you have cifs-utils installed now, remove the mount from within XO, and from the console and try to remount it.

Fetakungen

@DustinB3403

Already done , I also did a reboot but it's still the same..

This "Error" pops up when i do an ls of the mount folder. Does XO do hardlink of the mount ? If so this might be the cause..

This happens at the mount.

I rolledback to nodejs 5.x instead of 6.x and rebuildning atm.

Same error with 5.x

olivier

SMB "mount" is not done via the system but with a Javascript library (lib-smb2), contrary to NFS which is mounted via a "mount" command.

So for SMB it's not really mounted, we are streaming files via SMB protocol.

Fetakungen

@olivier

I see. Ideas where to start looking ? According to the log i would say it's nodejs related but i'm no expert in the linux world.

olivier

@Fetakungen I would like to see the logs (in text format please). I bet on a broken SMB protocol thing (either on the lib we use or the SMB server). We tested it against Windows Server SMB, not Samba. The issue is probably there. NFS should work better.