From: solotus@... Date: 2020-04-21T08:31:52+00:00 Subject: [ruby-core:97997] [Ruby master Bug#16804] Vagrant Up does not work anymore Issue #16804 has been reported by xolge (Gerard Bee). ---------------------------------------- Bug #16804: Vagrant Up does not work anymore https://bugs.ruby-lang.org/issues/16804 * Author: xolge (Gerard Bee) * Status: Open * Priority: Normal * ruby -v: 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin16] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- Good day, I was able to set up a VM (Scotch Box Pro @ https://github.com/scotch-io/scotch-box) last week and it was successful; I didn't encounter any ruby bug or hints. Yesterday, I updated VirtualBox and Vagrant, and created a different/another VM using Scotch Box Pro and encountered bugs. I updated ruby and it is the same bug. The error was: *You may have encountered a bug in the Ruby interpreter or extension libraries.* I encountered it with the commands: ``` vagrant up ``` ``` vagrant box outdated ``` So, I updated ruby; it still failed. I went back to my successful VM last week and did vagrant up -- it failed. I tried my older VMs (running with VCCW @ https://github.com/vccw-team/vccw as well as Trellis @ https://github.com/roots/trellis), and they do not start with *vagrant up* anymore. Versions: OS: Mac OS X 10.12.6 Vagrant: 2.2.7 VirtualBox: Version 6.0.18 r136238 (Qt5.6.3) ruby: 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin16] Please look into the attached logfiles. ---Files-------------------------------- ruby_2020-04-21-035353_MBP.crash (43.4 KB) ruby_2020-04-21-141905_MBP.crash (44 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: