It's not a vagrant error. It is an error in the app I am testing but it happens when I spin up multiple boxes.
For example: Spin up box 1, deploy my app, while testing another box is spun up, application on first box crashes. I've narrowed it down to the nat configuration that happens before each box. The nat configuration that happens causes slight interruptions which causes one of our services to crash. I was hoping to narrow down exactly what was happening so I could provide the developers with concrete steps to fix our app. On Jan 17, 2015 12:41 AM, "Alvaro Miranda Aguilera" <[email protected]> wrote: > what error? > > On Sat, Jan 17, 2015 at 9:05 AM, Umair Chagani <[email protected]> > wrote: > >> I'm seeing a weird error when spinning up machines on the same host. I'm >> pretty sure it is a port forwarding problem but I can't isolate it to a >> single line in the debug logs. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
