Pools don't appear then disappear on custom XO but are fine on XOA
-
Hi,
Start by checking your Node and npm version.
-
@olivierlambert node was ver 20. npm is 9.6.7
-
Ever hear of murphy's law?
yeah.....once you complain your problems, they go away!!!!
I did what everyone else did and just reinstalled a new one, and problem solved.
here is what I did different.
Apparently, when installing debian if you give root a password, then sudo does not get installed. (note)
so, i installed everything I could under the user (xoa i created) and if i did not have permission, i signed into root su - and installed there, then went back to user. By passing the need for sudo...........doing this made it all work out.
Thank you for the patience, and I am sorry for the new ticket creation!
-
You should stick to the official doc to avoid trouble: https://xen-orchestra.com/docs/installation.html#from-the-sources
Read carefully the "Packages and Pre-requisites" section, telling you about the Node version you should use (Node 18). Node 20 will become LTS in October.
However, I'm happy to know it works already on Node 20 anyway
-
This post is deleted! -
@Hibikisayo and now there broken again, and I can't seem to load logs to find the issue.
-
Test remote
unknown error from the peer
SHOW LOGSbut when I look at logs, it just spins forever. I let it run over night for 9 hours.
any thoughts? I tried to find the logs manually but could not find them VIA cli.
the folder /var/log/syslog no syslog folder. -
The logs are the output of
xo-server -
I had that exact, same issue when trying to run Node 20. Rolling back to an older version of Node did fix the issue for me.
@olivierlambert In @Hibikisayo's defense, the Packages and Pre-requisites page only specifies the use of the latest Node LTS:
Following the "this page" link takes you to an instructional page where you follow yet another link to be taken to the page with instructions on how to install Node depending on which OS you are running. That page is very confusing, however, and you have to dig even further in order to find out which version is the latest LTS version. A cursory look and you would think that Node 20 is the most current (which it is), but you have to dig and interpret charts to figure out which version is the latest LTS version. This would surprise people to find out it's not Node 20, or even Node 19, which is the latest LTS version.
Of course, none of this is on Vates or Xen Orchestra, since it's the NodeSource site itself that is so darned confusing... but I can see how anyone would think they are installing the correct version when they are accidentally two versions ahead.
-
It's hard to make the documentation dynamic pointing automatically to the latest LTS. I don't know how we can improve this, but it's a small impediment to carefully read the doc to enjoy it
-
@olivierlambert Agreed... it's definitely an issue on the NodeSource side and nothing to do with Vates and your documentation! You'd think with that nice chart they have showing each individual version and its compatibility, they could put one more box indicating which is the LTS at any given time.
-
@olivierlambert I guess I made an assumption, cause most guides out there, especially for linux, there pictures are not up to date on what version to use.
Looking back I can see where I missed it.
as for my issue, I did roll it back to node 16.20.2 ( when I reinstalled node using NODE_MAJOR 16 this is what got installed, doesn't match your version exactly) and it still won't load the logs or join my SMB share.
How can I view the logs and upload them here?
-
The doc gives an example, it's the latest Node LTS you should use (so right now it's Node 18).
-
@olivierlambert I don't do documentation, so I'm not 100% sure how easy something like just adding what version XO uses.
-
@olivierlambert switched to node 18.18 and still no logs, or remote server connect
-
It's hard to assist without much information. Can you check the IP of the host is correct? (if you navigate to it).
-
O olivierlambert moved this topic from Xen Orchestra on
-
FWIW, I just ran into this same issue with Node 20.9.0, which is the current LTS version. Reverting to Node 18.18.2 resolved the issue for me.
