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.
    • 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
                                      • GheppyG Offline
                                        Gheppy @EddieCh08666741
                                        last edited by

                                        @EddieCh08666741 I restore a VM that is created with bc0afb589e96694fb30410cc5843ada6a866d995 and is ok

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

                                          @olivierlambert
                                          I have a XOCE but I will also try an XOA

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

                                            I wonder, could you test with Node latest, to see if it could be related to something in Node itself? (19.7 is the current one). Don't forget to rebuild everything.

                                            GheppyG 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post