@Danp Yes I did that and it looks good now.
Best posts made by laurentm
Latest posts made by laurentm
-
RE: fatal error while updating XOA (installed from source)
Thanks for your answer.
I'll give a try later, bypassing the PFBlocker module of the router.
Github is not currently on any blacklist, but I block Digital Ocean and some others who host many attackers.
-
RE: fatal error while updating XOA (installed from source)
The XOA running on 8.3 was a clone of the XOA running on 8.2 and has been fine for more than four months. It still works, just the last update cannot be performed.
The VM OS is the same Ubuntu 22.04 LTS with the latest updates.I cannot right now update the 8.2 because it is used by 100+ VMs.
-
RE: fatal error while updating XOA (installed from source)
@Danp I have only one XOA running on XCP-NG 8.3, the other one is on 8.2 and had no issues. I do not know if others 8.3 users have success or not.
The previous updates on 8.3 had no problems.Both XOA VMs are build from source on Ubuntu server 22.04 LTS with 16 GB ram
and 4 vCPU.Hardware:
- DELL Poweredge R820 quad cpu Xeon E4610 for XCP-NG 8.3
- DELL Poweredge R650 two cpu Xeon 4309Y for XCP-NG 8.2.
-
RE: fatal error while updating XOA (installed from source)
cd /root/XenOrchestraInstallerUpdater/ ./xo-install.sh Welcome to automated Xen Orchestra install Following options will be used for installation: OS: Ubuntu 22 Basedir: /opt/xo User: root Port: 80 HTTPS: false Git Branch for source: master Following plugins will be installed: all Number of previous installations to preserve: 3 Node.js and yarn auto update: true Errorlog is stored to /root/XenOrchestraInstallerUpdater/logs/xo-install.log-202403021931 for debug purposes Depending on which installation is chosen: Xen Orchestra configuration will be stored to /root/.config/xo-server/config.toml, if 2a74b636-cb2b-e63d-f4da-76aa3789d6d5you don't want it to be replaced with every update, set CONFIGUPDATE to false in xo-install.cfg Xen Orchestra Proxy configuration will be stored to /root/.config/xo-proxy/config.toml. Config won't be overwritten during update, ever ----------------------------------------- 1. Install 2. Update 3. Rollback 4. Install proxy 5. Update proxy 6. Exit **choice 2 is selected** : 2 [info] Installing nodesource repository [info] Checking current node.js version [ok] node.js version already on 18, checking updates [info] Fetching Xen Orchestra source code [fail] Something went wrong, exiting. Check /root/XenOrchestraInstallerUpdater/logs/xo-install.log-202403021931 for more details and use rollback feature if needed
-
RE: XCP-ng 8.3 beta 🚀
XenOrchestra (from source) update failed with the latest updates of XCP-NG 8.3.
I opened a topic in XOA forum, but I succeeded to update in XCP-NG 8.2, so the
error is coming from 8.3.fatal: unable to access 'https://github.com/vatesfr/xen-orchestra/': server certificate verification failed. CAfile: none CRLfile: none
Finally, I have bypassed the PFBlocker module during the update and no more error happened.
-
fatal error while updating XOA (installed from source)
I'm running XCP-NG 8.3 Beta (with last updates availables) and when I try to update XOA (installed from source), I have this error:
fatal: unable to access 'https://github.com/vatesfr/xen-orchestra/': server certificate verification failed. CAfile: none CRLfile: none
EDIT: same update with XCP-NG 8.2 LTS works perfectly
-
RE: EOL: XCP-ng Center has come to an end (New Maintainer!)
Thanks for your valuable work.
I did not found any information about how Citrix users will manage XenServer after the end of XenCenter.
I doubt they recommend XOlite
Do they plan to rely only on XSconsole or CLI ?I'm still using XOA and XCP-NG Center together because for basic tasks (like start/stop a VM) XCP-NG Center is faster and simple.
XOA is fantastic for advanced use and backups, and does not need a windows machine but you have no overall view at a glance.
-
RE: NVMe storage wrong detection
@davemcl said in NVMe storage wrong detection:
List the LBA format of drive
Thanks, I'm new to NVMe storage in XCP-NG and did not even know the nvme-cli (which is not installed by default in CentOS and XCP-NG). It looks like I'm already using 512b sector size:
/dev/nvme0n1 50026B72830CEBE9 KINGSTON SEDC1500M7680G 1 7.68 TB / 7.68 TB 512 B + 0 B S67F0103
/dev/nvme1n1 50026B72830167A0 KINGSTON SEDC1500M3840G 1 3.84 TB / 3.84 TB 512 B + 0 B S67F0103In the last 15 years, with my previous DELL servers, the RAID controller was doing everything and volumes were perfectly seen by XenServer and XCP-NG. When I bought a full NVMe RS650XS, I did not ordered any RAID controller and only one DELL U2 960 GB to save money because DELL U2 prices are crazy. Instead I bought 4 really cheap KINGSTON DC1500M, which are less expensive than their SATA counterpart (DC600M). Unfortunately, the LVM choice at install leads me to crash half of the VMs after one month !
Now, I'm using EXT and many separate disks, this is far for ideal because I waste room for more VMs but it seems reliable
and these large U2 SSDs are really cheap, while the slower SAS SSDs are still pricey for an unknown reason.