Fresh Install - Can't Create VMs or See VMs after Refresh?

Soarin

Hi! I've installed XenOrchestra from source more than once, I initially used a Github script I found online from a video made by LawrenceSystems. I noticed that it'd work great, but if I refresh the page then XenOrchestra no longer thinks it's connected to XCP-NG, I'll go to the servers tab and it'll say connected, but I have to disconnect it and reconnect it for it to show all my VMs again.

I've tested this on Ubuntu 16.04 Server and Ubuntu 18.04 Server, just now I've built it from source without any scripts and followed the guide on the wiki. It ended up the same, is this a bug with the current version or is there something I'm doing wrong? Thank you

The error I get is:

Jun 09 09:28:22 xoserve xo-server[810]: 2019-06-09T09:28:22.852Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:28:23 xoserve xo-server[810]: 2019-06-09T09:28:23.129Z - xo:api - [WARN] admin@admin.net | xo.getAllObjects(...) [19ms] =!> XoError: invalid parameters
Jun 09 09:30:31 xoserve xo-server[810]: 2019-06-09T09:30:31.219Z - xo:main - [INFO] - WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:30:32 xoserve xo-server[810]: 2019-06-09T09:30:32.249Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:30:32 xoserve xo-server[810]: 2019-06-09T09:30:32.426Z - xo:api - [WARN] admin@admin.net | xo.getAllObjects(...) [1ms] =!> XoError: invalid parameters
Jun 09 09:30:33 xoserve xo-server[810]: 2019-06-09T09:30:33.458Z - xo:main - [INFO] - WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:30:34 xoserve xo-server[810]: 2019-06-09T09:30:34.586Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:30:34 xoserve xo-server[810]: 2019-06-09T09:30:34.751Z - xo:api - [WARN] admin@admin.net | xo.getAllObjects(...) [2ms] =!> XoError: invalid parameters
Jun 09 09:31:22 xoserve xo-server[810]: 2019-06-09T09:31:22.071Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:31:22 xoserve xo-server[810]: 2019-06-09T09:31:22.353Z - xo:api - [WARN] admin@admin.net | xo.getAllObjects(...) [3ms] =!> XoError: invalid parameters

I'd really like to use XenOrchestra with all the features source has but this problem isn't letting me use it other than to browse the interface. I can't create VMs, made a user account and they can't make the self service VM they have access to, and here's the error for that which I suspect is related:

Jun 09 09:41:41 xoserve xo-server[810]: 2019-06-09T09:41:41.875Z - xo:api - [WARN] soarin | xo.getAllObjects(...) [2ms] =!> XoError: invalid parameters
Jun 09 09:42:07 xoserve xo-server[810]: 2019-06-09T09:42:07.016Z - xo:main - [INFO] - WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:42:07 xoserve xo-server[810]: 2019-06-09T09:42:07.104Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:42:07 xoserve xo-server[810]: 2019-06-09T09:42:07.131Z - xo:main - [INFO] - WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:42:08 xoserve xo-server[810]: 2019-06-09T09:42:08.554Z - xo:main - [INFO] + WebSocket connection (::ffff:192.168.1.29)
Jun 09 09:42:08 xoserve xo-server[810]: 2019-06-09T09:42:08.651Z - xo:api - [WARN] soarin | xo.getAllObjects(...) [2ms] =!> XoError: invalid parameters
Jun 09 09:43:25 xoserve xo-server[810]: 2019-06-09T09:43:25.256Z - xo:api - [WARN] soarin | vm.create(...) [4ms] =!> XoError: invalid parameters

I don't see anything in tasks -> logs either, I hope this can be resolved. I hope to be able to use the source build so I can get the features I'd like since I'm just a home user and offering servers to friends. Thank you

olivierlambert

You are maybe hitting a bug from master branch. Please wait for someone to fix it. This can happen, because there is no guarantee on master branch, even if we try to make it working.

Note: this is not happening in XOA because it's frozen after a validation/QA process.

olivierlambert

Pinging @julien-f

Soarin

Alrighty, thank you for the quick response! I'll wait, I haven't migrated from Proxmox yet so I should be fine until then.

~~Does this problem exist on the XOA currently too? Thank you~~ Just read your quote, apologies

olivierlambert

You can use XOA Free for… free with all administration features, in the mean time. Also you have a free 15 days trial unlocking Premium.

Then you can go back to the sources

borzel

@Soarin you can also checkout a tagged version in git to avoid the cutting edge technology in master

olivierlambert

Yeah but there's no guarantee it will work better at all. Sometimes we make tags and make QA, then spot issues.

borzel

@olivierlambert of course

Soarin

@olivierlambert That's exactly what I've done, very impressed. I'm moving some servers over now to see how they react to Xen and so far so good. Thank you for the help

@borzel Thank you for that suggestion, I'll try that out once the XOA premium expires and if master branch still isn't working for me.

olivierlambert

XOA Free let you create, migrate and all admin needed operations No need for Premium for this!

julien-f

Thank you for your report, I just fixed it: https://github.com/vatesfr/xen-orchestra/commit/4b16a2c0c53c4675709f2a553f815b9abff82b57

Please use our bug tracker to report issues

0

julien-f committed to vatesfr/xen-orchestra

fix(xo-server/xo.getAllObjects): correctly validate ndjson param

Fixes https://xcp-ng.org/forum/topic/1478/fresh-install-can-t-create-vms-or-see-vms-after-refresh

Soarin

@julien-f Thank you! I'll get that after the XOA Premium expires!

Rt

@julien-f got the same issue with @Soarin, but after the update I was now able to create VMs. Thanks.
OS: Ubuntu 18.04.2

julien-f

@Rt You're welcome, thanks for your feedbacks

bjotte

Hi.
I think I have got similar issue with xen orchestra built from source, the problem seems to be with ubuntu as it works fine in Debian 9.9 Have tried to build it several with several scripts and even following the guide in the wiki and all fail on Ubuntu 18.04.2 but works 100% on Debian. it might be a dependency issue or something in ubuntu as it all of a sudden just stopped working after working for a long time. So my fix was just going for a Debian server instead.

Danp

@bjotte Have you tried a newer version of Ubuntu (ie: 19.x)? Worked for me as of a week ago.

bjotte

@Danp No, I haven't as I never use non-LTS servers from Ubuntu, and most software and guides asks for LTS.
I might test it later with 19.04 but my posting here was more for the sake of others as I imagine that I'm not the only one that has experienced this on Ubuntu so when I figured out that it works in Debian I figured others could get some help too. It might also point the developers in the right direction if they wish to look into this, I don't know how many users there are that have got this problem but at least there are some of us so it might be something to look at if not at least there is a posted alternative. Most would not change OS if all guides tell them that Ubuntu works so this was more meant as a PSA if nothing else.