ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra SMB Remote problem

    IT Discussion
    xen server xen orchestra backup
    8
    37
    8.6k
    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.
    • DanpD
      Danp
      last edited by

      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.

      AdamFA 1 Reply Last reply Reply Quote 1
      • AdamFA
        AdamF @Danp
        last edited by

        @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
        
        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD
          Danp @AdamF
          last edited by

          @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?

          AdamFA 2 Replies Last reply Reply Quote 0
          • AdamFA
            AdamF @Danp
            last edited by

            @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!

            1 Reply Last reply Reply Quote 0
            • AdamFA
              AdamF @Danp
              last edited by AdamF

              @Danp

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

              AdamFA 1 Reply Last reply Reply Quote 0
              • AdamFA
                AdamF @AdamF
                last edited by

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

                DanpD 1 Reply Last reply Reply Quote 1
                • DanpD
                  Danp @AdamF
                  last edited by

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

                  P.S. Your link above is broken.

                  AdamFA 1 Reply Last reply Reply Quote 0
                  • AdamFA
                    AdamF @Danp
                    last edited by

                    @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
                    
                    1 Reply Last reply Reply Quote 0
                    • DustinB3403D
                      DustinB3403
                      last edited by

                      @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?

                      1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403
                        last edited by

                        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

                        AdamFA 1 Reply Last reply Reply Quote 0
                        • AdamFA
                          AdamF @DustinB3403
                          last edited by

                          @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
                          1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403
                            last edited by

                            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?

                            AdamFA 1 Reply Last reply Reply Quote 0
                            • AdamFA
                              AdamF @DustinB3403
                              last edited by

                              @DustinB3403

                              In the CLI of the VM where XO is installed:

                              smbclient //192.168.1.200/xsbackups -U xenbackups

                              Then of course I'm prompted for the password and it connect immediately.

                              DustinB3403D 1 Reply Last reply Reply Quote 0
                              • DustinB3403D
                                DustinB3403 @AdamF
                                last edited by DustinB3403

                                @fuznutz04 I assume you meant to use \

                                It's odd that this works from the CLI but not the web interface.

                                In the address field which is proceeded by \\ and then <address\share>* are you typing in the double \\ or just putting in "192.168.1.200\xsbackups"?

                                0_1475586898062_chrome_2016-10-04_09-14-52.png

                                1 Reply Last reply Reply Quote 0
                                • DustinB3403D
                                  DustinB3403
                                  last edited by

                                  Or are you putting in just the ip address of the server, and in the following field putting in the folder?

                                  1 Reply Last reply Reply Quote 0
                                  • AdamFA
                                    AdamF
                                    last edited by

                                    It will only allow you to put in the correct format of IP\Share. So in this example, i only put in 192.168.1.200\xsbackups. xsbackups is the name of the SMB share.

                                    I keep looking at this connection refused error. It makes me think it is something specifically with the web interface, or that the API is not working properly.

                                    1 Reply Last reply Reply Quote 0
                                    • DustinB3403D
                                      DustinB3403
                                      last edited by

                                      It might be a bug that needs to go up to @olivier to take a look at.

                                      1 Reply Last reply Reply Quote 1
                                      • olivierO
                                        olivier
                                        last edited by

                                        Please put a screenshot here with how you filled those fields.

                                        AdamFA 2 Replies Last reply Reply Quote 2
                                        • AdamFA
                                          AdamF @olivier
                                          last edited by

                                          @olivier 0_1475798522725_2016-10-06 20_01_33-Settings.png

                                          mrfusion is the name of my desktop where the share is located. I also tried putting in the workgroup name in that field instead of the PC name.

                                          1 Reply Last reply Reply Quote 0
                                          • AdamFA
                                            AdamF @olivier
                                            last edited by

                                            @olivier
                                            0_1475798740323_2016-10-06 20_05_07-.png

                                            Opening Chrome developer tools gives me these messages when trying to either add the remote share.

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