New install does not load logs or perform backups
-
@olivierlambert No, I've just configured port 8080 non-http (just wanted to get it running first) - Should I configure https first?
-
Please try HTTPS to rule out a websocket issue you might have in your environment.
If you want to test quickly, go ahead with XOA to get a turnkey thing that just work outside the box.
-
@olivierlambert I enabled https, restarted the service and same result unfortunately, i'll play around and see if I can get it resolved and post feedback, not disputing that this might be a user error but I did follow the install steps.
-
Please try with XOA to see if it's an install from source issue or XO bug itself.
-
@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?
-
Nevermind
I see it creates a VM, doing it now, will respond shortly -
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?
-
I uncommented useSudo but did not set it to true
NFS is working now -
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 EditionI have signed out and signed back in. Anything else I need to do?
-
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
-
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 -
@mauzilla What version of Node are you using? You can verify with
node -vin an SSH session to your XO VM. -
@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?
-
root@XO:~# nodejs -v v14.16.1 -
@mauzilla You should be using
nodenotnodejs. -
@danp it's the exact same
-
root@XO:/# node -v v14.16.1 -
@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 -
@danp sorry, I did not mean the binaries are the exact same, I meant the 2 versions are the exact same
-
@mauzilla Have you clicked on "Update" in XOA view?
