Well there has been some changes since this post lol.
Changed the following:

• Replaced the 480gb sata ssd's in the storage server with 8x480gb 12g sas ssd's and 4x 3.84tb 12g sas ssd's.
• Removed the Mikrotik switch from the rack to use it elsewhere and used 1g rj45 sfp modules to run the copper instead.

Soon to add:

• Rebuilding each of the hosts 1 by 1 as I put in some 4x10g cards I picked up for a great price (Chelsio T540-CR cards), just waiting on the DAC cables to arrive.

I might look at upgrading the ram and cpu in the 3900xt host so it matches the other two hosts at some point too... either that or start upgrading to Ryzen 7000 series

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@psafont Would designating a new pool master do the same thing?
I ran the above command and its had no effect

Well, I tried changing the pool master and when VMHost11 was the master I was able to enable HA.
Switching back to VMHost13 as the master now so will see how that goes

Everything is working as expected/hoped.

So for anyone reading through this and wants a TL;DR

• Issue was related to the pool master setting, changing the pool master to a different host and then back to the original fixed the incorrect settings allowing HA to be enabled

Well everything is moved over to an NFS datastore, thanks for the responses all
Performance seems unchanged (which is great)

@lawrencesystems said in My XCP-NG Homelab 2023 edition:

@jmannik

Looks good, nice cable management as well.

Thanks, ill make a note to never show the other sides for cable management so that compliment still applies lol

Hi All,

Posted this on twitter a number of times, but here is my homelab.

From top to bottom:

• Unifi Pro Aggregation Switch
• Mikrotik CRS328-24P-4S+RM
• Intel i5 2400, 8GB Ram, Ubuntu 22.04 bare metal Xen Orchestra Community Edition
• Ryzen 3900XT, 64GB RAM, 2x10G network (1 for VM, 1 for iSCSI), XCP-NG 8.3
• Ryzen 5900X, 128GB RAM, 2x10G network (1 for VM, 1 for iSCSI) XCP-NG 8.3
• Ryzen 5900X, 128GB RAM, 2x10G network (1 for VM, 1 for iSCSI) XCP-NG 8.3
• Ryzen 3600, 16GB RAM, 2x25G network, 17x 480GB SAS SSD's (RAID F1 with 1 hot spare) Xpenology(Synology) 7.2.1 U1 for the iSCSI target.

I currently run a number of game servers on this setup:

• Minecraft.
• DCS World.
• IL-2 Great Battles Series (Stalingrad, Moscow, Kuban, Bodenplatte, Normandy etc.)
• Euro Truck Sim 2 and American Truck Sim.

I also run a few other things for my internal only network:

• iVENTOY
• PiHole
• Universal Media Server/PS3 Media server/etc.

Plan is to add a number of larger drives to the storage server, add in another NAS for backup storage to replace my existing NAS. And maybe one day pick up a Supermicro Microcloud AM5 system (8 Ryzen 7000 series in a 3U chassis)

@olivierlambert said in SMAPIv3 - Feedback & Bug reports:

Wait for a blog post coming next week

You have my attention

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@psafont Would designating a new pool master do the same thing?
I ran the above command and its had no effect

Well, I tried changing the pool master and when VMHost11 was the master I was able to enable HA.
Switching back to VMHost13 as the master now so will see how that goes

Everything is working as expected/hoped.

So for anyone reading through this and wants a TL;DR

• Issue was related to the pool master setting, changing the pool master to a different host and then back to the original fixed the incorrect settings allowing HA to be enabled

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@psafont Would designating a new pool master do the same thing?
I ran the above command and its had no effect

Well, I tried changing the pool master and when VMHost11 was the master I was able to enable HA.
Switching back to VMHost13 as the master now so will see how that goes

@psafont Would designating a new pool master do the same thing?
I ran the above command and its had no effect

@psafont said in Unable to enable High Availability - INTERNAL_ERROR(Not_found):

@jmannik The IPs match, and now I don't have an explanation on why is this happening, I'll take another look at the codepath, but that'll have to take a while, as work is piling up

Ahh but they dont match.
VMHost13 lists 192.168.10.13
VMHost12 and VMHost11 list 192.168.30.13

Ok, so in this process I have come across a re-occurring issue I have had with XCP-NG where it will have the wrong order for the ethernet interfaces.
Each of my hosts has a 1gbit interface onboard, then a 4 port 10gbit card
It SHOULD be ordering the interfaces like so:
ETH0 1gbit
ETH1 10gbit
ETH2 10gbit
ETH3 10gbit
ETH4 10gbit

But it will randomly decide upon install (VMHost11 was recently rebuilt due to an id10t pebkac issue) to order them like below for no apparent reason:

ETH0 10gbit
ETH1 1gbit
ETH2 10gbit
ETH3 10gbit
ETH4 10gbit

And to be able to re-order the interfaces its just a lot more difficult that I think it should be.

[22:27 vmhost12 ~]# xe pool-param-get uuid=213186d2-e3ba-154f-d371-4122388deb83 param-name=master | xargs -I _ xe host-param-get uuid=_ param-name=address
192.168.10.13
[22:27 vmhost12 ~]# cat /etc/xensource/pool.conf
slave:192.168.30.13[22:27 vmhost12 ~]#

[22:27 vmhost11 ~]# xe pool-param-get uuid=213186d2-e3ba-154f-d371-4122388deb83  param-name=master | xargs -I _ xe host-param-get uuid=_ param-name=address
192.168.10.13
[22:28 vmhost11 ~]# cat /etc/xensource/pool.conf
slave:192.168.30.13[22:28 vmhost11 ~]#

I think I see where the issue is, not sure how to solve it though

@psafont
[22:13 vmhost13 ~]# xe pool-param-get uuid=213186d2-e3ba-154f-d371-4122388deb83 param-name=master | xargs -I _ xe host-param-get uuid=_ param-name=address
192.168.10.13
[22:13 vmhost13 ~]# cat /etc/xensource/pool.conf
master[22:14 vmhost13 ~]#

Well this is what im getting now:

{
  "id": "0mhbgkupy",
  "properties": {
    "method": "pool.enableHa",
    "params": {
      "pool": "213186d2-e3ba-154f-d371-4122388deb83",
      "heartbeatSrs": [
        "381caeb2-5ad9-8924-365d-4b130c67c064"
      ],
      "configuration": {}
    },
    "name": "API call: pool.enableHa",
    "userId": "71d48027-d471-4b01-83f9-830df4279f7e",
    "type": "api.call"
  },
  "start": 1761709884550,
  "status": "failure",
  "updatedAt": 1761709923544,
  "end": 1761709923544,
  "result": {
    "code": "INTERNAL_ERROR",
    "params": [
      "unable to gather the coordinator's UUID: Not_found"
    ],
    "call": {
      "duration": 38993,
      "method": "pool.enable_ha",
      "params": [
        "* session id *",
        [
          "OpaqueRef:a83a416f-c97d-1ed8-c7fc-213af89b8f86"
        ],
        {}
      ]
    },
    "message": "INTERNAL_ERROR(unable to gather the coordinator's UUID: Not_found)",
    "name": "XapiError",
    "stack": "XapiError: INTERNAL_ERROR(unable to gather the coordinator's UUID: Not_found)\n    at Function.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)\n    at file:///opt/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21\n    at runNextTicks (node:internal/process/task_queues:65:5)\n    at processImmediate (node:internal/timers:453:9)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }
}

@psafont
That is done now, tried to enable HA again and it was unsuccessful, what would you like me to do now?

@tjkreidl This hasn't been my experience so far, enabling HA has just enabled HA, no reboot needed.

@psafont I am patching all my hosts now, will do the above test packages on Sunday Night (it is Friday afternoon at the time of this post)