Xen Orchestra - Community Edition - Installing with Yarn
-
While the script should detect the error and abort, you can't hold it responsible for something on your end that is preventing the package from being found. This is what I get when I run the same command --
sudo apt search redis-server Sorting... Done Full Text Search... Done golang-github-stvp-tempredis-dev/bionic,bionic 0.0~git20160122.0.83f7aae-1 all Go package to start and stop temporary redis-server processes libtest-redisserver-perl/bionic,bionic 0.21-1 all redis-server runner for tests python-hiredis/bionic 0.2.0-3 amd64 redis protocol reader for Python 2.X using hiredis python3-hiredis/bionic 0.2.0-3 amd64 redis protocol reader for Python using hiredis redis/bionic,bionic 5:4.0.9-1 all Persistent key-value database with network interface (metapackage) redis-server/bionic,now 5:4.0.9-1 amd64 [installed] Persistent key-value database with network interface
-
@bnrstnr Did your install from the mini.iso work?
-
@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:
https://mirror.pnl.gov/releases/bionic/ubuntu-18.04.1-live-server-amd64.iso
For some reason most of the normal sources aren't available on the install from this iso.
running
apt-cache policy
gives me like 3 results, where the ISO I normally use, and even the mini.iso list like 15 sources -
Its not something on my end.
The repo for redis-server isnt on the server iso repo.
It is on the regular ubuntu repo. -
@danp yes, the mini.iso worked
-
@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:
Its not something on my end.
The repo for redis-server isnt on the server iso repo.
It is on the regular ubuntu repo.But that isn't something we should "fix", if you chose to use a repo that doesn't have the minimal requirements, you should install the requirements before installing this.
-
I just had this conversation 2 maybe 3 weeks ago with a person who was complaining about the install failing because they chose an ISO that had cmdtest package, which breaks other dependencies.
If you're using a shitty iso, it's on you to fix the issues in that ISO, not on us to hope and pray we've caught and fixed every possible upstream issue.
-
With that said, if you come and report the issue to us, we can try and assist you with the error you're encountering. But you can't expect us to account for things that we aren't specifically out looking for.
If redis-server isn't in your repos' add it, update and then try the install.
sudo add-apt-repository ppa:chris-lea/redis-server sudo apt-get update
-
It is the official server iso from ubuntu. I also redownloaded this same iso from ubuntu.com and there is also no redis-server. Nowhere does your guide say to install prerequisites or add repositories to install. It says 'install ubuntu server and use this one line installer'. I did that and it fails 100% of the time. redis-server isnt on the ubuntu server iso repo by default.
-
Use the alternate version
http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.1-server-amd64.isoInstead of the new default version
http://releases.ubuntu.com/18.04.1/ubuntu-18.04.1-live-server-amd64.iso -
@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:
It is the official server iso from ubuntu. I also redownloaded this same iso from ubuntu.com and there is also no redis-server. Nowhere does your guide say to install prerequisites or add repositories to install. It says 'install ubuntu server and use this one line installer'. I did that and it fails 100% of the time. redis-server isnt on the ubuntu server iso repo by default.
But you've stated redis isn't included in the ISO you've used, normally you don't have to go and troubleshoot anything as the main Ubuntu and Debian distro's just work. (Debian does require some additional setup but that's adding sudo and curl).
Otherwise nothing is required. I'm testing with the ISO you've provided.
-
Even if not included, apt-get should go and find it.
-
Fixed by ditching ubuntu, my SOP today with ubuntu based installers and setups.
First try on debian, works with one warning about optional fsevents component.
This component only seems to be for osx so not sure why it is being triggered here during the install. -
@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:
Fixed by ditching ubuntu, my SOP today with ubuntu based installers and setups.
First try on debian, works with one warning about optional fsevents component.
This component only seems to be for osx so not sure why it is being triggered here during the install.Very odd since most of the testing is Ubuntu.
-
@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:
First try on debian, works with one warning about optional fsevents component.
This happens with Ubuntu, too. Not sure what it's supposed to do, but none of the installs I've done ever have it.
-
@momurda for what it's worth with the ISO you provided I'm seeing the same error messages.
Jul 31 18:35:45 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:45 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:45 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:45 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:45 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:45 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:45 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:45 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:46 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:46 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:46 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:46 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:46 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:46 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:46 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:46 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:47 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:47 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:47 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:47 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:49 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:49 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:49 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:49 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:52 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:52 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:52 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:52 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:35:56 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:35:56 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:35:56 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:35:56 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:36:05 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:36:05 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:36:05 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:36:05 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:36:19 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:36:19 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:36:19 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:36:19 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:36:42 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:36:42 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:36:42 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:36:42 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:37:23 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:37:23 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:37:23 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:37:23 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14) Jul 31 18:38:31 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379 Jul 31 18:38:31 xoce xo-server[5052]: at Object._errnoException (util.js:992:11) Jul 31 18:38:31 xoce xo-server[5052]: at _exceptionWithHostPort (util.js:1014:20) Jul 31 18:38:31 xoce xo-server[5052]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
The ISO is missing the minimal requirements to make the install work.
-
@dustinb3403 The new 18.04.1 live-server ISO even directly from the ubuntu site doesn't include the universe repos anymore. I was in the process of posting an issue in your github but got distracted.
-
@bnrstnr It's likely the same ISO just hosted from multiple sources. I'll have to see what repo's are missing.
-
@dustinb3403 here is all that's in the new version sources.list
deb http://archive.ubuntu.com/ubuntu bionic main deb http://archive.ubuntu.com/ubuntu bionic-security main deb http://archive.ubuntu.com/ubuntu bionic-updates main
-
Yes it is something Canonical has done to their server iso. Cant even install glances at the moment with it due to missing the software repos. Just doesnt make much sense why they would do that.