@stormi - Thanks for the help.. Yup I removed both packages and now things are going as expected 8-)

Cant wait to try out the new build!

~Peg

@olivierlambert Well.. I have been doing the occasional "yum update" with no new problems. Everything is working great, but I still have that re-scanning of the FS every 30 seconds.. Not impacting anything but just a little weird...

@ilidza I dont use Nagios reporting myself, but I noticed in my /var/log/orchestra.log the following after the last git pull. You might want to see if there is anything in there that looks similar:

2022-12-14T00:00:35.623Z xo:server:handleBackupLog WARN sendToNagios: TypeError: app.sendPassiveCheck is not a function
    at sendToNagios (file:///root/XO/xen-orchestra/packages/xo-server/src/_handleBackupLog.mjs:21:15)
    at handleBackupLog (file:///root/XO/xen-orchestra/packages/xo-server/src/_handleBackupLog.mjs:69:9)
    at file:///root/XO/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng/index.mjs:317:17
    at ChildProcess.<anonymous> (/root/XO/xen-orchestra/@xen-orchestra/backups/runBackupWorker.js:27:11)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.patchedEmit [as emit] (/root/XO/xen-orchestra/@xen-orchestra/log/configure.js:135:17)
    at emit (node:internal/child_process:937:14)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

@bern I just built mine on Dev 11 a few days ago...

Make sure sudo is installed and do:

curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -

@ronan-a Sure.. I would be happy to... I just had to append a .txt to the end of the file in order to upload it.. Please remove .txt and decompress

logs2.tar.gz.txt

Hi Everyone,

I was wondering if this is a bug or if it is something specific to my setup. But.. I just noticed that a 'rescan' seems to be happening on my lab server every 30 seconds..

I noticed this because I was making a new template for XOCE and was deleting snapshots (viewing the /var/log/SMlog to wait until the coalescing was complete) and noticed that this was happening.

I will include the log file for viewing.. The log file is trimmed from 0730 -> present so it would fit in the posting limits.. But this was happening from the begging of the rotated logfile..

smlog.txt

~Peg

Oh! Is this a new feature in XCP-ng 8.3????

If so... YEA!!!!

I was just wondering... Is it just my installation or is there no XenTools ISO in the dropdown for virtual disks?

EDIT: Never mind.. Its a XCP-ng Center thing.. I can mount the ISO from XO (it does not show up in XCP-ng Center in the dropdown list or even when it is mounted)..

@cocoon Thank you for doing that!!!

@stormi Yea.. I though it was weird as well, but I was happy to see it work.. Here is a screen shot of the XCP-ng screen.. I havent upgraded the Peg02 yet (as I have to get more disks in there tonight in order to migrate things around), but notice the version number on the Peg03

The good news is that I eventually got 8.3 installed and it is looking good.. I had a few problems, but this was mostly down to something weird with the partition layout.

Every time I installed 8.3 (fresh install) onto a machine, it would refuse to create any "Local Storage". I bounced around in circles many time and gave up, installing 8.2 (fresh install) and got the same result. What I had to do eventually is "ALT+Right Arrow" until I got to a # prompt, do a lvdisplay to find the VG and then do a lvremove on the VG + a wipefs -a -f /dev/sda3 to clear EVERYTHING out. It was somehow picking up that the drives I were using previously were used in a ZFS pool (btw.. This is really weird as these drives were used in a different machine, on a different RAID system, etc.. I have no idea how it figured out there was a ZFS pool, but whatever).

Once I did the above, the fresh install worked just fine (8.2), joined it my my existing pool, promote it to a pool master and then do an upgrade to 8.3

After the upgrade, local storage was showing offline for about 5 minutes, but then it magically kicked itsself into life. I am assuming it was doing something in the background as the new pool master.

As a point of note, it looks like XCP-ng Center V20.11.0.3 is still compatiable as I am using that as well as XO to manage the pool with no issues (so far)