I've tried to find information about this on Google but I couldn't find anything.
Hi All --
I'm also having the problem described above and am wondering if anyone has any light to shed. The only new information I can provide is that I receive the error after applying a lengthy Puppet manifest; if I shorten the manifest I don't receive the error. This is 100% reproducible. Note also that the longer, error generating manifest is applied correctly, i.e., I don't see anything obvious that *is* an error.
JK> Means your puppet apply is failing. Vagrant ssh into the host
JK> and run the command manually, I wager it will fail. Debug the
JK> manifests and modules there, then when you've resolved the issue
JK> run vagrant up from scratch to test.
Thanks for your reply. I had done as you'd suggested but not carefully
enough. Vagrant's good enough to report back that something happened;
running from the command line Puppet merely died silently while writing
its activity log (which looks a lot like success if you don't bother
checking $?, my bad).
At any rate the problem ended up being an out of memory error. Trivial
fix and completely in line with the behavior I was seeing.