Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
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.
-
@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 =).
-
@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.
-
The nas says nothing about access denied etc.
In 4.x the error message was diffrent but well result the same.
-
@Fetakungen Can you access the share from any other systems using the same credentials?
-
@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.
-
Try this from the console
sudo mkdir ~/mnt sudo mount -t cifs //myserver_ip_address/myshare ~/mnt -o username=samb_user,noexecFilling in your details.
-
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.. -
@Fetakungen So if you have cifs-utils installed now, remove the mount from within XO, and from the console and try to remount it.
-
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
-
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.
-
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.
-
@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.
-
@olivier said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@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.
I'm using SMB to connect to a Mint desktop for my backup testing.
-
@BRRABill I guess depends of Samba config
-
@BRRABill said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@olivier said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@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.
I'm using SMB to connect to a Mint desktop for my backup testing.
But the Samba system, not the lib that they use, I'm guessing.
-
Well all i can say for the 3 sites where this error occur is that the Samba server is Freenas. What logs would you like to see ?
BR,
Fetak -
For anyone wondering, you can run this on Debian (8.5) I've just updated my test system, and all appears to be working without issue.
-
@Fetakungen xo-server output when the issue is triggered.
-
See my previous post. But here it's again :
