New install does not load logs or perform backups

olivierlambert

Please try with XOA to see if it's an install from source issue or XO bug itself.

mauzilla

@olivierlambert Is XO installed on the actual host using the XOA method? We want to separate XO on a different server than the Xenservers. Is this possible?

mauzilla

Nevermind I see it creates a VM, doing it now, will respond shortly

mauzilla

I installed via XOA which worked, but want to still pursuit installing the "from sources"

I booted up a Debian 10 VM and followed the steps as expected. Installed works fine, dont get the internal 500 error anymore in console but "logs" still have a ajax loader (might be a bug, or not).

I then wanted to add a remote NFS. Adding the remote NFS info seems to be correct on screen, but 2 issues:

I dont know if this would be added afterwards, but may be worth mentioning to add nfs-common as one of the required libraries when installed from sources. Debian does not install this by default (dont think any distro does)
Adding the mount point gives a connection failed, with the following output:

EACCES: permission denied, mkdir '/run/xo-server'

XO is running as a non-root user, however, the user (xo) has already been added to the sudoers file. I have tested this from CLI, I can su xo and then sudo as root (without password). I have also edited the config file and enabled the useSudo parameter.

Any advice?

mauzilla

I uncommented useSudo but did not set it to true NFS is working now

mauzilla

But unfortunately no luck, backup issue is still persisting. I want to try and do the backup from the XOA created appliance, but it tells me I need to upgrade my license. I have linked the account and it tells me I have premium trial that expires 5 may, yet, if I go to the backups > create vm backup I get the notice saying:

Upgrade needed
This feature is available starting from Starter Edition

I have signed out and signed back in. Anything else I need to do?

mauzilla

Also worth noting that the backup job cannot start on the Debian VM, when we click start we're immediately getting an Unknown error has occurred. There is also no logs displayed for the backup logs or settings > logs

I am doubtful this is platform based as I can reproduce on both Ubuntu 20.04 and Debian 10.9

olivierlambert

You need a trial to test backups with XOA

If it works there and not on your Debian, then there's a environment issue on your VM. It's hard to find a root cause because there's so many potential way to configure your VM, your network share and so on.

Let's rule out XOA first, then from your XO on the sources, don't forget to rebuild on latest commit on master

Danp

@mauzilla What version of Node are you using? You can verify with node -v in an SSH session to your XO VM.

mauzilla

@olivierlambert thanks Olivier, on the XOA VM, although it says I have premium version until 5 May, when I go to backups, I get an error saying I need to upgrade. I have restarted the XOA VM already. Not sure what could be causing it?

mauzilla

@danp

root@XO:~# nodejs -v
v14.16.1

Danp

@mauzilla You should be using node not nodejs.

mauzilla

@danp it's the exact same

mauzilla

@danp

root@XO:/# node -v
v14.16.1

Danp

@mauzilla said in New install does not load logs or perform backups:

it's the exact same

Not always. For example, this is what I get with my install --

danpollak@ubuntuxo:~$ node -v
v14.16.0
danpollak@ubuntuxo:~$ nodejs -v
v10.19.0

mauzilla

@danp sorry, I did not mean the binaries are the exact same, I meant the 2 versions are the exact same

olivierlambert

@mauzilla Have you clicked on "Update" in XOA view?

mauzilla

@olivierlambert, update sorted it, 2 things I noticed was that logs worked out of the box, and I was able to start the backup. For reference, it's the exact same NFS config as on the sources version

olivierlambert

Okay good, so it could be your install/configuration in your VM

mauzilla

@olivierlambert said in New install does not load logs or perform backups:

your

I guess it can only be that. The 2nd VM is a clean Debian 10.9 build, nothing else installed or configured and steps taken exactly from the sources documentation. I can reproduce this on the 1st install as well, doing the exact same result. If something else needs to be configured we would have no insight on that. Are there logs I can look at to try and decipher what could be causing this?