Xen Orchestra SMB Remote problem

Jason

I don't use Xen Orchestra but I have to ask since this isn't windows why the heck are you using SMB instead of NFS?

JaredBusch

@Jason said in Xen Orchestra SMB Remote problem:

I don't use Xen Orchestra but I have to ask since this isn't windows why the heck are you using SMB instead of NFS?

If I had to wager, I would put my money on his existing target NAS/whatever already has a SMB share available.

DustinB3403

I'm not using SMB, but I would recommend trying to connect to the SMB share via the XO CLI first, that will give you a more verbose report as to what went wrong.

hobbit666

Think I had a similar issue with SMB shares but switched to NFS once I worked out how to do it

AdamF

Correct, I have a Windows box with enough storage to be a backup target, so I just used SMB.

@DustinB3403 , Do you mean connect via the CLI on the OS where XO is installed, or is there a separate XO CLI built into the web client?

Also, I have XO installed on a VM on the XenServer for testing. For those of you using XO in production, do you typically have XO installed on a separate physical box?

DustinB3403

@fuznutz04 you can access the XO console from within XO (or you can use XC), or putty (recommended approach).

Running XO on your production system is fine, having dedicated hardware for it would defeat part of the purpose of virtualizing.

AdamF

@DustinB3403

Thanks. I just connected via the XS console directly and was able to connect to the share. This seems to be a XO issue now.

In regards to separate hardware for XO: That's what I thought, but was just thinking about how you go about managing XS if the XO VM is unavailable. XenCenter would be the best route here for those running Windows. There isn't any other non Windows management app besides XO that I'm aware of, correct?

DustinB3403

@fuznutz04 I'm not aware of any other well developed tools to manage XenServer, outside of Xen Orchestra (mildly XenCenter).

Danp

What version of XO? Make sure you are running a recent version as there have been some updates to this code recently.

Also, open a PuTTY window and connect to your XO host. Then run the following command to observe the XO log in realtime: journalctl -u xo-server -f -n 50

Now try connecting to the SMB share via XO and watch for any meaningful output in the logs.

AdamF

@Danp

I'm running 5.2.3 for XO server and 5.2.1 for the web client.

Following your steps, I don't see any logs at all.

[root@XenServer ~]# journalctl -u xo-server -f -n 50
No journal files were found.

If I open developer tools in chrome, it at least gives me more of an error message.

VM50:37 WebSocket connection to 'ws://192.168.1.246/api/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSEDWrappedWebSocket @ VM50:37
index.js:68 next attempt in 559 ms

Danp

@fuznutz04 You must have built the VM using an alternate method than most of us here. Otherwise, that command would show the output from xo-server.

How do you start xo-server?

AdamF

@Danp I used a guide on here. I'll find it and review how I did it. I installed Ubuntu and then installed XO on it. I need to step out for a bit. I'll get details when I return. Thanks!

AdamF

@Danp

So I followed this guide, but it was a couple weeks ago. I don't remember deviating from the guide though.

AdamF

@fuznutz04 To clarify, I followed the original post, which used Scott's script, not the manual instructions further down in the post.

Danp

@fuznutz04 Post the output of sudo systemctl status xo-server.service .

P.S. Your link above is broken.

AdamF

@Danp said in Xen Orchestra SMB Remote problem:

@fuznutz04 Post the output of sudo systemctl status xo-server.service .

P.S. Your link above is broken.

Fixed the link above, thanks. The output is:

sudo systemctl status xo-server.service
[sudo] password for adam: 
● xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset
   Active: active (running) since Mon 2016-10-03 09:25:45 EDT; 22h ago
 Main PID: 21941 (node)
   CGroup: /system.slice/xo-server.service
           └─21941 /usr/local/bin/node ./bin/xo-server

Oct 04 08:13:55 xeno xo-server[21941]: Tue, 04 Oct 2016 12:13:55 GMT xo:api adam
Oct 04 08:13:56 xeno xo-server[21941]: Tue, 04 Oct 2016 12:13:56 GMT xo:api adam
Oct 04 08:13:56 xeno xo-server[21941]: Tue, 04 Oct 2016 12:13:56 GMT xo:api adam
Oct 04 08:14:00 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:00 GMT xo:perf blo
Oct 04 08:14:00 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:00 GMT xo:api adam
Oct 04 08:14:00 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:00 GMT xen-api roo
Oct 04 08:14:01 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:01 GMT xen-api roo
Oct 04 08:14:01 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:01 GMT xen-api roo
Oct 04 08:14:02 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:02 GMT xo:api adam
Oct 04 08:14:02 xeno xo-server[21941]: Tue, 04 Oct 2016 12:14:02 GMT xo:api adam

DustinB3403

@fuznutz04 so your XO installation is running, and there aren't any apparent issues being reported.

You said you were manually able to connect to the SMB share using the XO cli, if you try to connect to the SMB in the web interface what happens?

Is this share hosted on a domain?

DustinB3403

From the CLI of XO put in

watch sudo systemctl status xo-server.service

and then try to connect to the SMB share from the web interface.

Using Putty is highly recommended

AdamF

@DustinB3403

No, this is a single server, in a lab, in a workgroup. Connecting from the XO Web interface does nothing at all. No error message on the screen. If I open developer tools in Chrome, it shows me a little more about what's happening. see below.

ebSocket connection to 'ws://192.168.1.246/api/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
t {message: "invalid status closed, expected open", name: "t"}
message
:
"invalid status closed, expected open"
name
:
"t"
stack
:
(...)
get stack
:
stack()
set stack
:
stack()
__proto__
:r

So every time I click the connect button in the web UI of XO, it seems to restart XO server. Then the only other message that I see that gives me a clue is : xo:api (unknown user) | session.signIn(...) [3ms] ==> object. Full output below.

Oct 04 08:48:44 xeno systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Oct 04 08:48:44 xeno systemd[1]: Stopped XO Server.
Oct 04 08:48:44 xeno systemd[1]: Started XO Server.
Oct 04 08:48:46 xeno xo

Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 161ms
Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:main + WebSocket connection (::ffff:192.168.1.41)
Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 33ms
Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 12ms
Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 69ms
Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xen-api [email protected]: event.from(...) [2s] ==> object
Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:perf blocked for 258ms
Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:api (unknown user) | session.signIn(...) [3ms] ==> object
Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xen-api [email protected]: event.from(...) [33ms] ==> object
Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:api

DustinB3403

Without providing the password; what do you have in your SMB connection setting?

You were able to connect to the SMB share from the XO console right?