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

    A "socket" was not created for HTTP request before 300000ms

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    90 Posts 8 Posters 15.8k Views 8 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.
    • BrunoMoraisB Offline
      BrunoMorais
      last edited by

      I've just pulled last main branch:

      b984a9ff00af812bcd1b238523f8f0d75f3c7ca9

      Problem stays the same.

      $ lsb_release -a
      No LSB modules are available.
      Distributor ID: Debian
      Description: Debian GNU/Linux 10 (buster)
      Release: 10
      Codename: buster

      $ node -v
      v16.19.0

      $ yarn -v
      1.22.19

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        @BrunoMorais you are not using a right Node version. Our doc is pretty clear with it: https://xen-orchestra.com/docs/installation.html#nodejs

        Please use the right version and rebuild everything. Even if the result is the same, at least we can compare apples to apples.

        BrunoMoraisB 1 Reply Last reply Reply Quote 0
        • arsenieciprianA Offline
          arsenieciprian @olivierlambert
          last edited by

          @olivierlambert
          root@space:/opt/xo/xo-builds/xen-orchestra-202302270756# git show
          commit 24ac3ea37d0f4f8e35c2532d93ca13a0308aa4a3 (HEAD -> master, origin/master, origin/HEAD)
          Author: Julien Fontanet julien.fontanet@isonoe.net
          Date: Sat Feb 25 10:55:03 2023 +0100

          feat: release 5.79.3
          
          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            @arsenieciprian can you try to go on commit bc0afb589e96694fb30410cc5843ada6a866d995, rebuild and tell me if you have the same problems?

            arsenieciprianA 2 Replies Last reply Reply Quote 0
            • BrunoMoraisB Offline
              BrunoMorais @olivierlambert
              last edited by

              @olivierlambert It must be 16.14?

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                @BrunoMorais have you read the link I provided?

                BrunoMoraisB arsenieciprianA 3 Replies Last reply Reply Quote 0
                • BrunoMoraisB Offline
                  BrunoMorais @olivierlambert
                  last edited by

                  @olivierlambert Yes I've read. It show 16.14 version. I thought to maintain the major verions and I could use a more updated minor version.
                  So I was asking if I must stay with 16.14.

                  1 Reply Last reply Reply Quote 0
                  • BrunoMoraisB Offline
                    BrunoMorais @olivierlambert
                    last edited by

                    @olivierlambert I see. Please always use latest Node LTS.

                    1 Reply Last reply Reply Quote 0
                    • arsenieciprianA Offline
                      arsenieciprian @olivierlambert
                      last edited by

                      @olivierlambert

                      i m doing'it now, wait 10 mins pls

                      EddieCh08666741E arsenieciprianA 2 Replies Last reply Reply Quote 0
                      • EddieCh08666741E Offline
                        EddieCh08666741 @arsenieciprian
                        last edited by

                        @arsenieciprian Bruno it means LTS

                        I'm using the latest lts which is 18

                        1 Reply Last reply Reply Quote 0
                        • arsenieciprianA Offline
                          arsenieciprian @olivierlambert
                          last edited by olivierlambert

                          @olivierlambert

                          root@space:/opt/xo/xo-builds/xen-orchestra-202302271416# git show
                          commit bc0afb589e96694fb30410cc5843ada6a866d995 (HEAD)
                          Author: ...
                          Date: Fri Feb 17 10:42:35 2023 +0100

                          Screenshot 2023-02-27 at 14.41.19.png

                          it seems that is working

                          1 Reply Last reply Reply Quote 0
                          • arsenieciprianA Offline
                            arsenieciprian @arsenieciprian
                            last edited by

                            @arsenieciprian

                            i will retry now with master to see if issue persist

                            1 Reply Last reply Reply Quote 1
                            • arsenieciprianA Offline
                              arsenieciprian @olivierlambert
                              last edited by

                              @olivierlambert

                              commit 9fcd497c42805cd8b7fb936864a6dae9580677d2

                              does not work

                              Screenshot 2023-02-27 at 14.53.18.png

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Offline
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by

                                Okay thanks, so we are now 100% sure about the problematic commit, but we still have hard time to reproduce it and therefore, understand why this is broken.

                                arsenieciprianA GheppyG 2 Replies Last reply Reply Quote 0
                                • arsenieciprianA Offline
                                  arsenieciprian @olivierlambert
                                  last edited by

                                  @olivierlambert
                                  thank you for help and prompt support. i will use this comit bc0afb589e96694fb30410cc5843ada6a866d995 until issue is fixed

                                  EddieCh08666741E 1 Reply Last reply Reply Quote 0
                                  • EddieCh08666741E Offline
                                    EddieCh08666741 @arsenieciprian
                                    last edited by

                                    @arsenieciprian is your restore working fine ?

                                    GheppyG 1 Reply Last reply Reply Quote 0
                                    • GheppyG Offline
                                      Gheppy @olivierlambert
                                      last edited by Gheppy

                                      @olivierlambert
                                      When I get home (I have the same problem on my home lab and at work I don't have internet in the servers area), I can open a tunnel if you want.

                                      1 Reply Last reply Reply Quote 0
                                      • olivierlambertO Offline
                                        olivierlambert Vates 🪐 Co-Founder CEO
                                        last edited by

                                        @Gheppy This will be probably helpful, I suppose you can have an XOA up to date with the issue, right?

                                        GheppyG 1 Reply Last reply Reply Quote 0
                                        • EddieCh08666741E Offline
                                          EddieCh08666741
                                          last edited by

                                          I'm at commit b1e81d8 which Replication and delta works fine now. I'm trying to find the commit where restore starts working.

                                          3320ddaa-0bfd-4a99-8798-78417bb1a024-image.png

                                          1 Reply Last reply Reply Quote 0
                                          • BrunoMoraisB Offline
                                            BrunoMorais
                                            last edited by

                                            I've updated my node version.

                                            $ node -v
                                            v18.14.2

                                            I'm in commit 9fcd497c42805cd8b7fb936864a6dae9580677d2 and problem staus the same.

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