Error when attempting to start the vm: "vagrant up" #23
Comments
|
@jxfish2 does the host hardware you're running on support virtualization, and is it enabled? |
|
Thanks for the response, but I just finished editing my original post. My server is running 64-bit CentOS 7. My server is a VM, running in the Azure cloud. Now, this brings up another question. This is a dedicated server, just for InfoButtons. Can we run Vagrant, and the OIB, without installing VirtualBox? Is there a way to install your VM, or the application, via your source code, directly on the server, without VirtualBox? |
|
As RedHat Linux is the default Linux platform for the majority of corporate IT environments, RedHat and CentOS really need to be supported, by any projects that you develop. What is the fastest, and easiest way, to install InfoButtons directly on a dedicated RedHat based server? I have an older InfoButtons server that I built back when you were first developing InfoButtons. I wanted to upgrade this older version, but you do not offer any upgrade instructions that I could find, and the new process is completely different than the old process. My original InfoButtons server was built on a VM located in our own dedicated data center. We recently migrated everything to the Azure cloud, and I need to build a new InfoButtons instance in the Azure cloud. In the Azure cloud, we carved out a dedicated CentOS 7 VM, just for InfoButtons. Note, that this server is for our own internal development efforts. Production installs will be done on supported RedHat Linux servers. |
|
@jxfish2 thanks for the extra info. Just to disclose, I'm not a member of the dev team, just an enthusiastic community member :) Sounds like you had already gone through the install guide and are looking for something to streamline the process further. Are you hoping to use the "official" build in another container platform, or do you want to further streamline the process of building it yourself? @gdelfiol - I'm blanking, but has the team done anything with other deployment options like a Docker container? Is this something on the roadmap, or (if not, but it's desirable) is this something we could contribute? |
|
@aniskand may be able to help with some your questions. I will try to help with what I know. We have not done anything with Docker, but we could if it helps. @jxfish2 , do you know what version of OpenInfobutton are you using? We had a major change to the profile XML schema over 5 years ago and then several changes to the DB schema. If your version is prior to those changes, it will be simpler to start from fresh and use the LITE tool to reconfigure your resource profiles. |
|
@gdelfiol , If you were able to publish your VM as a Docker container, downloadable from GitHub, that would be MUCH more platform independent. As a Docker container, it would not matter the platform, and it would not matter whether it was in Azure, AWS, IBM's new cloud, the Google cloud, or at a local data center. If all of your development efforts were designed as Docker containers, everything you do would be so much easier for end users to deploy, and it would not matter what Operating System the end users were working on. However, in the meantime, I still need to try to get InfoButtons up and working on a CentOS 7 server, running in the Azure cloud. Any ideas or assistance would be greatly appreciated. Thanks for your time, and have a great new year. |
|
Hi Joseph,
As was mentioned earlier, the current VM is basically a "dead" platform at
this point. It hasn't been updated for a number release versions and we're
not going to commit any further development effort towards it. I will work
towards creating a Docker container going forward which should streamline
things for folks looking to install OIB on various platforms. The original
VM was built on basically a blank Ubuntu VM that I then added a bunch of
the necessary dependencies too and installed OIB. It was really meant as
more of a proof of concept then a release product meant for wide use.
For now, as you suggested, it would probably be best to install OIB
directly. To do that, your best best would be to export your profile
database from the existing VM, and run the necessary scripts to upgrade it
to the new version. Or, you can start from scratch with a new install of
OIB/LITE and a fresh database. I would definitely recommend going ahead
with OIB 2.3,
https://github.com/VHAINNOVATIONS/InfoButtons
as I've streamlined the installation a bit by removing a bunch of
unnecessary dependencies, replaced some others with newer more enterprise
friendly ones, fixed a couple bugs that would have affected high
concurrency usage, and updated it to ensure support of JDK8. You should be
able to basically follow this BUILDGUIDE to install,
https://github.com/VHAINNOVATIONS/InfoButtons/blob/2.3-SNAPSHOT/oib-request/BUILDGUIDE
I know the recent changes only say 2.2, but nothing changed in the build
process between 2.2 and 2.3 for the Infobutton Manager. Feel free to reach
out to me if you run into any issues, but you're starting from a fresh
CentOS VM with no prior maven repository, then things should go fairly
smoothly. The biggest issues people run into are due to conflicts with
older dependency version in their maven repository.
…On Thu, Jan 24, 2019 at 9:25 AM jxfish2 ***@***.***> wrote:
@gdelfiol <https://github.com/gdelfiol> , If you were able to publish
your VM as a Docker container, downloadable from GitHub, that would be MUCH
more platform independent.
As a Docker container, it would not matter the platform, and it would not
matter whether it was in Azure, AWS, IBM's new cloud, the Google cloud, or
at a local data center.
If all of your development efforts were designed as Docker containers,
everything you do would be so much easier for end users to deploy, and it
would not matter what Operating System the end users were working on.
However, in the meantime, I still need to try to get InfoButtons up and
working on a CentOS 7 server, running in the Azure cloud.
Any ideas or assistance would be greatly appreciated.
Thanks for your time, and have a great new year.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKtmp8GtSI-8-5Pmkk5eX-Ld_6Lv7ks5vGd45gaJpZM4aPvBE>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
Hi Andrew, I am using the BUILDGUIDE link you specified above. I do have a few quick questions:
|
|
1. Honestly, I'm not sure about the JDK version. You can try the latest,
but I've personally never tested it with anything greater than JDK8. In
theory, they should be backwards compatible.
2. I've tried all the MySQL 5.x versions on various installations, and they
all work. Similarly, MariaDB 10.x is a drop-in replacement for MySQL 5.x,
and should also work just fine.
…On Mon, Jan 28, 2019 at 10:36 AM jxfish2 ***@***.***> wrote:
Hi Andrew,
I am using the BUILDGUIDE link you specified above.
I do have a few quick questions:
1.
The latest JDK is 11.0.2. Is it ok to install this latest version, or
would it be better to install an older version?
2.
I am attempting to download the latest MySQL 5.x version, but there
are several options on the download page. Which version should I download?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKrMK58hEWHZq6UVriyCZiqPJv5rRks5vHzUOgaJpZM4aPvBE>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
@jxfish2 - just be aware of licensing in JDK 11 vs. OpenJDK 11 |
--> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing
VBoxManage, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "93808398-d11a-4c5e-855f-a55725de6bbd", "--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
The Stderr listed here is different from the error shown in your documentation.
My environment:
CentOS 7
Virtual Machine, hosted in the Azure cloud.
I installed Vagrant, VirtualBox, VirtualBox repository, Vagrant file, OpenInfoButtonVM, and Kernel Modules in support of VirtualBox (to import the Oracle Public Key)
Note that we have several other projects running Vagrant just fine in the Azure cloud.
Do you have any specific instructions for installing from the source file?
Any help would be greatly appreciated.
Have a great evening.
The text was updated successfully, but these errors were encountered: