@Danp Current commit is 3d3b6.

xo-server: 5.103.0
xo-web: 5.104.0

Yes... as I had mentioned, everything worked until I updated yesterday at around 3:50 PM. I noticed there were five different commits that were released yesterday, and the one you linked to is one of those. So, as I figured, one of the commits from yesterday "broke" the ability to run continuous replications.

Now that it looks like you've focused on a cause, I'm sure it's only a matter of time until a new commit is published to fix the issue. Once it's released, I'll get it installed and, hopefully, we can put this behind us.

Thanks!!

@julien-f hi there,

I'm sorry for my delay but was a bit overwhelmed with other tasks.

So running only npm i now gives me the following output:

# git checkout . Updated 13 paths from the index # git branch * fix_fuse_dependancy_arm master # git pull --ff-only remote: Enumerating objects: 79, done. remote: Counting objects: 100% (73/73), done. remote: Compressing objects: 100% (41/41), done. remote: Total 79 (delta 36), reused 61 (delta 30), pack-reused 6 Unpacking objects: 100% (79/79), 87.43 KiB | 3.01 MiB/s, done. From https://github.com/vatesfr/xen-orchestra f1ab62524..3d3b63a59 master -> origin/master + 2378c0882...2d9a44c6e tasks -> origin/tasks (forced update) Already up to date. # npm i npm WARN deprecated modular-cssify@12.1.3: Renamed to @modular-css/browserify npm WARN deprecated modular-css-core@12.1.3: Renamed to @modular-css/processor npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. added 267 packages, removed 204 packages, changed 54 packages, and audited 3280 packages in 37s 209 packages are looking for funding run `npm fund` for details 70 vulnerabilities (5 low, 13 moderate, 49 high, 3 critical) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. #

This seems to throw a lot of warnings but no fatal errors, do you confirm? Also it's not suggesting to use the --legacy-peer-deps flag.

After using these commands and rebooting the host, XO is stopped.
Is npm i the same as yarn; yarn build ? Thank you!

edit: when I get an hour I'll redo from scratch to see how that goes.

@Danp

Thanks, yes of course. I got excited about fixing my problems and reported too early 🙂

Well, the VM has been working fine since the export / import. I can see both drives.

Although the VM running fine, since the last post I had to address two related VDIs that had been connected to the Control Domain. One being million_D and the other million_D (with a camera icon). These probably ended up here because of a aborted / faulty snapshot or backup. I disconnected them .. checked a few things ... and then forgot them. Everything is running fine now.

For future googlers: During the problem solving, I found out some pretty helpful info using tail -f /var/log/SMlog.

To me, this issue is solved. Thank you all for the feedback.

Hmm this could be done with a XAPI plugin I suppose 🤔

same for me. Enabled health check once to test my problem and now can't disable them.
commit f1ab6
backup log https://pastebin.com/zvy1P6wU

@florent No, I did not see that in the logs. I did see this problem is bigger than I thought.

It happens more often than just causing a VM backup failure. It happens during the merge or other checks which causes the backup process to destroy (remove) parts of other VM backups.

Clean VM directory parent VHD is missing parent VHD is missing parent VHD is missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing

and

Clean VM directory VHD check error some VHDs linked to the backup are missing

@Tristis-Oris can you open a support tunnel and give me the access code ( by direct message ) ?
https://help.vates.fr/help/en-us/8-technical-support/16-create-a-support-tunnel

I would like to look into this in detail since we made quite a lot of changes on the merge and the caching recently
regards

@Danp thank you for the suggestion. Actually I didn't choose that commit for any reason in particular, I just saw the log back to a date which I sorta reminded having done an update and XO was working and that one seemed back enough but with a huge level of uncertainty was just ball parking.

The commit you suggested worked!!! holy guacamole! ❤ that commit is gold!

We got an exception from XAPI, but let's see if it's "because" of XO. Pinging @julien-f

Yay! Thanks both @Gheppy for the report and @errellion for the feedback 🙂

@olivierlambert Thanks for the link , seems i will go the XOA route as suggested by @Darkbeldin

got error log at manual sync. Looks like only this pool break the whole syncing.
https://pastebin.com/peBbN8HP

@jcdick1 I run opnsense on xcp-ng personally as well and use their packaged tools without issue, the only time I've gotten this behavior is when I hot-added interfaces and it changed the order of interfaces. If that's not it, I'm really not sure what would be causing this

One last thing you can try in case it's a weird cash issue is (inside XOA) go to settings > servers, click the green connected button next to your xcp-ng server to disconnect it from xoa - then wait a couple seconds and click it again to reconnect it

@Darkbeldin In my network NFS and Samba shares would be a VM also on the same host so I would be in the same boat as before

Same message than the other thread: https://xen-orchestra.com/docs/community.html

Read this carefully.

You should always start to read this before creating a new thread: https://xen-orchestra.com/docs/community.html

It is in the same place in XO. Network tab of the host.

Change the Mode from None to Static (or DHCP). This should get you a pop up to enter the address, netmask, etc.