Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install script fails #30

Open
antonkulaga opened this issue Oct 28, 2017 · 6 comments
Open

install script fails #30

antonkulaga opened this issue Oct 28, 2017 · 6 comments

Comments

@antonkulaga
Copy link

Cannot run the install script:

==> dendroVagrantDemo: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
    dendroVagrantDemo: Box Provider: virtualbox
    dendroVagrantDemo: Box Version: 20161214.0.1
==> dendroVagrantDemo: Loading metadata for box 'ubuntu/xenial64'
    dendroVagrantDemo: URL: https://vagrantcloud.com/ubuntu/xenial64
==> dendroVagrantDemo: Adding box 'ubuntu/xenial64' (v20161214.0.1) for provider: virtualbox
    dendroVagrantDemo: Downloading: https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20161214.0.1/providers/virtualbox.box
==> dendroVagrantDemo: Successfully added box 'ubuntu/xenial64' (v20161214.0.1) for 'virtualbox'!
==> dendroVagrantDemo: Importing base box 'ubuntu/xenial64'...
==> dendroVagrantDemo: Matching MAC address for NAT networking...
==> dendroVagrantDemo: Checking if box 'ubuntu/xenial64' is up to date...
==> dendroVagrantDemo: Setting the name of the VM: dendroVagrantDemo
==> dendroVagrantDemo: Clearing any previously set network interfaces...
==> dendroVagrantDemo: Preparing network interfaces based on configuration...
    dendroVagrantDemo: Adapter 1: nat
    dendroVagrantDemo: Adapter 2: hostonly
==> dendroVagrantDemo: Forwarding ports...
    dendroVagrantDemo: 22 (guest) => 2222 (host) (adapter 1)
==> dendroVagrantDemo: Running 'pre-boot' VM customizations...
==> dendroVagrantDemo: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "c41b9658-0106-4e48-a862-ef2de3a4ac0b", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

[FATAL ERROR] There were errors installing Dendro.
Please check any prior error messages.

I also know that:

INFO: Your CPU does not support KVM extensions
KVM acceleration can NOT be used

So, probably I am blocked.
Are there any other ways of running dendro, maybe there is docker-compose somewhere?

@silvae86
Copy link
Member

Hi, what are your computer’s specs? Are you trying to run Dendro-install from inside a virtual machine?

Also, about docker-compose and Docker in general, we did not feel that it was stable enough at the time we started deploying Dendro as an automated installer. Dendro relies on many services and after many crash dumps by Docker we gave up on it and returned to the most solid and basic foundation, which is bash scripts and a clean Linux system (hence the option for vagrant).

At this time there are no plans at this time to port the installer to Docker, but we welcome any pull request towards that goal.

@antonkulaga
Copy link
Author

antonkulaga commented Oct 31, 2017

I tried to deploy it on Azure cloud, Ubuntu LTS 16.04, but failed

@silvae86
Copy link
Member

That is the problem, you cannot deploy a virtual machine inside a virtual machine (apart from very rare exceptions).

Try running the installation script on a real computer; any computer with a Core 2 Duo CPU or later will have VT-x extensions.

@antonkulaga
Copy link
Author

Try running the installation script on a real computer; any computer with a Core 2 Duo CPU or later will have VT-x extensions.

It does not make sense as we deploy all our web resources in the cloud. However, if you have a script that installs all the dependencies, then I can try to install it inside the Azure VM. I am thinking about running ElasticSearch and MongoDB in Docker containers and installing other stuff manually.

@silvae86
Copy link
Member

silvae86 commented Oct 31, 2017

If you have a clean Ubuntu 16.04 machine you can do that, but you need to edit some values in the scripts/constants.sh file; that is what we do when we want to set up a new testing instance.

That file has all the constants used by the installation, and most you can leave as is.

In that file, what you need to edit is the hostnames and IPs of the database servers (virtuoso, mongodb and elasticsearch). All those database services will be installed by the scripts to run in the localhost, so you set those as 127.0.0.1. The Dendro host should then be the IP of your VM or its DNS name.

Any passwords and other credentials are in the scripts/secrets.sh, and you can edit those if you wish.

After you make the necessary edits, cd to the scripts/ folder and run ./install.sh.

@silvae86
Copy link
Member

Hi @antonkulaga want to try out our new Docker image?

  1. Install Docker
  2. Open a Terminal window on Linux/Mac or press Ctrl+R on Windows, type cmd.exe in the box that appears and press Enter
  3. Clone the Dendro Docker installation repository by pasting this code
git clone https://github.com/feup-infolab/dendro-install-docker dendro-install-docker
  1. Run the installation command in the same terminal and wait until no more text is printed. It can take several minutes.
cd dendro-install-docker
docker-compose up
  1. Access your dendro installation at 127.0.0.1:3001 in your browser.
  2. When you want to stop Dendro, just press Ctrl+C at the terminal window

We provide a Docker image for getting you up and running quickly. For deployment in a production server, however, we recommend you use the Dendro install scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants