XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. cgasser
    3. Posts
    C
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 22
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Nos stats problem (but not the know one I guess)

      @florent Sure. I get that. But the XOA is part of that network as it needs to make the backups. I can also ping the the IPs. I need to go to the datacenter to do more checks. Don't want to do them by remote as the severs are operational currently. Will keep you updated.

      BR
      C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      @florent Yes. That was set. We want to run all backups in a dedicated network (VLAN, 10 Gbit, et,c). That network is completely separated.

      Does that mean if I use a backup network, I wont get any stats?
      Is there any documentation available on that that I can read?

      BR
      C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      If it is the state.db file, then there is no mention of 127.0.0.1.

      grep "127.0.0.1" state.db brings nothing no result. C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      Folder /var/lib/xcp/ file xapi? C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      @olivierlambert Would you mind giving me a hint on where to find that file? C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      @olivierlambert Nothing with 127.0.0.1. Also hostname ( RO): is set correct. I can find some localhost entries. But for license server, etc. C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      @olivierlambert Right. Any idea on how to check and change that? Management interfaces seems to be OK on the hosts. I can access and manage all servers. It seems it is just the stats that are not working. C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      @olivierlambert Hi! No, that is not the case. All servers are in the same rack. Connected to the same switch. Same network (VLAN, IP Range).

      XOA runs on the master server. No stats for that server. But stats for another server are ok (just one), all the others are not working.

      C

      posted in Management
      C
      cgasser
    • RE: Nos stats problem (but not the know one I guess)

      Update: I have 4 hosts in that pool. For one host, I can see stats. But just for that one host only. Not sure if that helps to point to the right directrion.

      BR
      C

      posted in Management
      C
      cgasser
    • Nos stats problem (but not the know one I guess)

      I have upgraded from 8.2.1 to 8.3. No I cant see any stats anymore. But I get a lot of these messages:

      {
        "id": "0mfjnqn6i",
        "properties": {
          "method": "vm.stats",
          "params": {
            "id": "2dd9279e-1f06-0151-6b9a-1ebf29d48edc"
          },
          "name": "API call: vm.stats",
          "userId": "7a3187b0-312e-43f9-9870-cfd591078f02",
          "type": "api.call"
        },
        "start": 1757852076761,
        "status": "failure",
        "updatedAt": 1757852076845,
        "end": 1757852076845,
        "result": {
          "errno": -111,
          "code": "ECONNREFUSED",
          "syscall": "connect",
          "address": "127.0.0.1",
          "port": 443,
          "message": "connect ECONNREFUSED 127.0.0.1:443",
          "name": "Error",
          "stack": "Error: connect ECONNREFUSED 127.0.0.1:443\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)\n    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:128:17)"
        }
      }
      

      To me it looks like XOA tries to load the data from 127.0.0.1.
      I have another pool connected to that XOA. Also 8.3. No issues. Therefore I assume it is not my XOA that causes that problem. I also update to the latest version via git pull. No change.

      Anyone and idea why this is?

      BR
      C

      posted in Management
      C
      cgasser
    • RE: CPU assignment

      Oh. That clarifies it. Just the colors 😉 Thank you!

      posted in Compute
      C
      cgasser
    • RE: CPU assignment

      That was quick 😉

      I try it with other words: Let's assume I have two VMs with 10 CPUs assignes each. Then I would expect that VM1 uses CPU 0 to CPU 9 and VM2 uses CPU 10 to CPU 19. But not both of them are using CPU 0 to CPU 9.

      Is my assumption wrong?

      And to answer your question: As there is no data for CPU 15 and above. And there are 9VMs on that host with in total much more than 15 CPUs ssigned.

      BR
      C

      posted in Compute
      C
      cgasser
    • CPU assignment

      Hi have a host with a bunch of cores. 18 cores times 2 CPUs. The assignment looks like that in the Stats:

      50f58170-fc2f-481a-ba4a-0f63ac4608f3-image.png

      CPU is: [https://www.intel.de/content/www/de/de/products/sku/192451/intel-xeon-gold-6254-processor-24-75m-cache-3-10-ghz/specifications.html](link url)

      My question now is: Why is nothing assigned to "CPU14"?
      I would have thought, that XCP NG / Xen is distributing the load over all availabel cores.

      Is there any way to optimize that?

      BR
      C

      posted in Compute
      C
      cgasser
    • Moving a VM from 8.2.1 to 8.3 (no opaque ref found)

      I try to move a VM from one host/pool (8.2.1) to another host/pool (8.3). When starting the import on the target I get this error message: no opaque ref found

      Source VM and target VM belong to a different pool but are connected via VPN.

      Any idea, what the reason might be?

      BR
      C

      posted in Management
      C
      cgasser
    • RE: One pool with more than one job / jobs should not run in parallel

      @DustinB Will give it a try with "1". Thank you!

      posted in Backup
      C
      cgasser
    • RE: One pool with more than one job / jobs should not run in parallel

      @DustinB Thank's for your response. But how to set my job-concurrency? Like "just 1 job at the time"?

      C

      posted in Backup
      C
      cgasser
    • One pool with more than one job / jobs should not run in parallel

      I have one pool with a bunch ob VMs. I have three backup jobs created (different requirements for different machines). They all are all set to start at 01:00. As far as I read in the docs, etc. all jobs would run in parallel then. Not sure if this is correct?
      Is there any option to define that job 2 runs after job 1 finished. Job 3 after job 2, etc.? Cause I do not know for sure how long each job runs. I can estimate of course, but there is still a risk of "conflict".

      BR
      C

      posted in Backup
      C
      cgasser
    • RE: [NOSNAP] [NOBAK] but disk is still backed up

      @olivierlambert Sorry. 8.3. Delta Backup.

      BR
      C

      posted in Backup
      C
      cgasser
    • [NOSNAP] [NOBAK] but disk is still backed up

      Hi,

      I have a VM with 2 disks. I do not want the second disk to be included in the backup. I have added [NOSNAP] [NOBAK] as prefix to the second disk's name.

      2c8165fd-6e77-4272-aa5b-165d0e7251c7-image.png

      Nevertheless, when doing a full backup, the data of this disk is tranfered as well:

      36cc7c34-e677-4e7a-a2ae-bf5850fef638-image.png

      I read some posts in this forum about that but it is still not clear to me.

      • Is the data of the disk transfered, but then deleted from the backup?
      • Did I do anything wrong?
      • Shouldn't it be transfered in the first place?

      BR
      C

      posted in Backup
      C
      cgasser
    • RE: Delta Backup / Snapshot / disk space

      @olivierlambert Thank your for poiting this out! Very much apreciated!

      posted in Backup
      C
      cgasser