XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Shares 0
    • Posts 8
    • Groups 0
    jerry1333J Offline
    1. Home
    2. jerry1333
    3. Topics

    Topics

    • jerry1333J

      CPU Usage of empty server

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XCP-ng
      15
      3
      0 Votes
      15 Posts
      2k Views
      marcoiM
      i think im seeing the same with fake cpu spikes. I started a second pool yesterday to patch and left it on over night. typically i just shut it down once done so the servers dont get too far behind patching. Under the pool stats im seeing spikes but under hosts nothing. It doesnt really bother me, but figure i add to the thread that im also seeing it. [image: c75fecec-d618-4f05-a931-edea6bc6ecce-image.jpeg] [image: 1b9ea5aa-d349-4ff8-af89-30a970d36fbb-image.jpeg] [image: 0f579999-cd96-4216-a0d4-d637ea5febf1-image.jpeg]
    • jerry1333J

      XOA Unable to connect xo server every 30s

      Watching Ignoring Scheduled Pinned Locked Moved Solved Xen Orchestra
      11
      0 Votes
      11 Posts
      2k Views
      poddingueP
      Thanks @cocoon, and I owe a correction: when I said in https://xcp-ng.org/forum/post/104865 that 6.4 would make these alerts disappear for good, I overstated it. If I'm reading the code right this time, the XO server sends a ping every 30 seconds stamped with its own clock (https://github.com/vatesfr/xen-orchestra/blob/master/@xen-orchestra/rest-api/src/events/event.class.mts), and the browser compares that stamp with its own clock and shows the banner once the gap passes 40 seconds (https://github.com/vatesfr/xen-orchestra/blob/master/@xen-orchestra/web-core/lib/packages/remote-resource/sse.store.ts). So https://github.com/vatesfr/xen-orchestra/pull/9681 widened the margin from 32 to 40 seconds, but a browser whose clock runs ahead of the XO server by more than about 10 seconds would still see it. That might be why @GregBinSD saw it on the Windows PC and not on the tablet, though that's only a guess on my part. Comparing two different clocks looks fragile to me, but @Team-XO-Frontend will know far better than I do whether there's a reason it's done that way.