Incomplete start of the virtual machine #16
Comments
|
This actually looks like it booted but failed to login. After that sequence
times out, I would try logging in again with "vagrant ssh".
…On Fri, Jul 14, 2017 at 2:40 AM, Rivas ***@***.***> wrote:
Hello everyone, I have several versions of the virtual machine with this
problem, never just started, someone has encountered the same problem?
Thank you all.
[image: image]
<https://user-images.githubusercontent.com/5821130/28205042-af3ad442-6880-11e7-8f4e-d897b8450b57.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AFXxKrjiN5TWBLbDKKlgpUzejMTRF1x9ks5sNymPgaJpZM4OX-8W>
.
|
|
thanks @aniskand but I was not able to connect either, it returns connection timeout error, I'cant login. |
|
Tell me this, after it timeouts, if you go into a browser and try to open,
http://localhost:8000/app/
Does the LITE application load?
…On Fri, Jul 14, 2017 at 11:01 AM, Rivas ***@***.***> wrote:
thanks @aniskand <https://github.com/aniskand> but I was not able to
connect either, it returns connection timeout error, I'cant login.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKpTFavf-OyFxiRMDotVYyzejaugGks5sN56mgaJpZM4OX-8W>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
Actually sorry, looks like I messed something up with the LITE config so
that won't work, try this instead and tell me if something loads,
http://localhost:8080/infobutton-service/infoRequest?
On Fri, Jul 14, 2017 at 11:27 AM, Andrew Iskander <andrew.iskander@utah.edu>
wrote:
… Tell me this, after it timeouts, if you go into a browser and try to open,
http://localhost:8000/app/
Does the LITE application load?
On Fri, Jul 14, 2017 at 11:01 AM, Rivas ***@***.***> wrote:
> thanks @aniskand <https://github.com/aniskand> but I was not able to
> connect either, it returns connection timeout error, I'cant login.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#16 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFXxKpTFavf-OyFxiRMDotVYyzejaugGks5sN56mgaJpZM4OX-8W>
> .
>
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
Neither address is working, and this is the message that the terminal returns.
|
|
Ok, so the VM isn't booting at all, I didn't see that in your original
message. Can you tell me what version of VirtualBox and Vagrant you're
running?
…On Fri, Jul 14, 2017 at 11:49 AM, Rivas ***@***.***> wrote:
Neither address is working, and this is the message that the terminal
returns.
[image: image]
<https://user-images.githubusercontent.com/5821130/28223887-620fd0c6-68cd-11e7-9ca4-6282e0edcfb5.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKm-IPJTyGmBxrHWfpgO22_uiPTdlks5sN6o0gaJpZM4OX-8W>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
I would say that I followed the recommendations of the installation guide, the versions are: VirtualBox --> Versión 5.0.38 r114632 |
|
What's weird is I don't see any error message. I had an issue on my Windows
machine where it wouldn't boot until I enabled virtualization in my bios,
but I was getting a specific error message indicating that. It's possible
it is booting, but just taking longer than the default timeout. Have you
successfully booted any VirtualBox VMs on that machine?
…On Fri, Jul 14, 2017 at 12:08 PM, Rivas ***@***.***> wrote:
I would say that I followed the recommendations of the installation guide,
the versions are:
VirtualBox --> Versión 5.0.38 r114632
Vagrant --> Installed Version: 1.9.5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKh44LtcDU0Iu8QemNsgIlhxeoMj6ks5sN66cgaJpZM4OX-8W>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
I have a 2.0 realese working, with some problems of the version, but is running. Maybe something must have changed in the configuration of version 2.1... |
|
Hmmm, I didn't change anything to the Vagrant configuration, I only updated
the version of OpenInfobutton that was preloaded onto the VM. Did you make
sure to halt/destroy the 2.0 VM before trying to boot the new one? To be
honest, I'm no expert on VirtualBox/Vagrant, I followed online guides to
setup a fairly standard config that works on my machines and can only debug
problems I've encountered myself.
…On Fri, Jul 14, 2017 at 12:52 PM, Rivas ***@***.***> wrote:
I have a 2.0 realese working, with some problems of the version, but is
running. Maybe something must have changed in the configuration of version
2.1...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXxKrAmBBh2Xnr_fbqJHMX06q8dKuZgks5sN7jagaJpZM4OX-8W>
.
--
Andrew Iskander
Software Engineer/BRISC
421 Wakara Way
Home/Cell: (919) 442-8129
Office Phone: (801) 587-8045
|
|
Yes, I only hace that VM in VirtualBox, I'm gonna tray build and compile the source Code, but Next week, It's already Friday night here. Thank you so much for everything. Greetings |
|
@AMJahhaf and I ran into a similar issue here, where the VM would start to boot and lock up at the same spot. Per this post it looks like it's a known bug which requires a serial port to be enabled. From the VM setup guide, I know we're told to turn off the serial port. Instead of disabling the serial port in VirtualBox, we needed to leave it enabled and change the Path/Address for Port 1. It was set to a path that doesn't exist on our machines, and once that was changed to some valid path the VM would boot properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone, I have several versions of the virtual machine with this problem, never just started, someone has encountered the same problem?
Thank you all.
The text was updated successfully, but these errors were encountered: