I am running into below error during terraform apply.
Error: timeout while waiting for plugin to start
Debug LOG:
2020-07-09T13:15:46.551-0400 [DEBUG] plugin: plugin process exited: path=/.terraform/plugins/darwin_amd64/terraform-provider-kubernetes_v1.11.3_x4 pid=48631
2020-07-09T13:15:46.551-0400 [DEBUG] plugin: plugin exited
2020-07-09T13:15:46.555-0400 [WARN] plugin: plugin failed to exit gracefully
2020-07-09T13:15:46.558-0400 [DEBUG] plugin: plugin process exited: path=/.terraform/plugins/darwin_amd64/terraform-provider-null_v2.1.2_x4 pid=48389
2020-07-09T13:15:46.558-0400 [DEBUG] plugin: plugin exited
That might happen because the lack of resources on your system (e.g RAM).
Related
On flutterfire configure command I am getting this error.
OS: Fedora 36
[debug] [2022-06-09T16:49:47.182Z] ----------------------------------------------------------------------
[debug] [2022-06-09T16:49:47.184Z] Command: /usr/local/bin/firebase /home/virendra/.cache/firebase/tools/lib/node_modules/firebase-tools/lib/bin/firebase projects:create my-notes-vcarp --json
[debug] [2022-06-09T16:49:47.185Z] CLI Version: 11.0.1
[debug] [2022-06-09T16:49:47.185Z] Platform: linux
[debug] [2022-06-09T16:49:47.185Z] Node Version: v16.15.0
[debug] [2022-06-09T16:49:47.186Z] Time: Thu Jun 09 2022 22:19:47 GMT+0530 (India Standard Time)
[debug] [2022-06-09T16:49:47.186Z] ----------------------------------------------------------------------
..
..
https://firebase.googleapis.com/v1beta1/projects/my-notes-vcarp:addFirebase {"error":{"code":403,"message":"The caller does not have permission","status":"PERMISSION_DENIED"}}
[debug] [2022-06-09T16:50:00.272Z] HTTP Error: 403, The caller does not have permission
[debug] [2022-06-09T16:50:00.277Z] FirebaseError: HTTP Error: 403, The caller does not have permission
at module.exports (/home/virendra/.cache/firebase/tools/lib/node_modules/firebase-tools/lib/responseToError.js:47:12)
at RetryOperation._fn (/home/virendra/.cache/firebase/tools/lib/node_modules/firebase-tools/lib/apiv2.js:286:39)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[error]
[error] Error: Failed to add Firebase to Google Cloud Platform project. See firebase-debug.log for more info.
Create a project first directly on Firebase and then select it from the CLI options. Most likely, Flutterfire does not have Firebase permissions.
Thanks to Tomas Radvansky for their help.
simply just run firbase login:ci to generate access key before you run flutterfire configure command.
I was run flutter build apk command then I am facing this exception below:
FAILURE: Build failed with an exception.
* What went wrong:
Could not dispatch a message to the daemon.
The message received from the daemon indicates that the daemon has disappeared.
Build request sent: Build{id=68f521a5-3aa3-4a37-be49-737d539a0090, currentDir=C:\Users\Lenovo\AndroidStudioProjects\subidha-pharmacy\android}
Attempting to read last messages from the daemon log...
Daemon pid: 10516
log file: C:\Users\Lenovo\.gradle\daemon\5.1.1\daemon-10516.out.log
----- Last 20 lines from daemon log file - daemon-10516.out.log -----
14:41:46.324 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 16627265536, Free: 448
6569984}
14:41:46.324 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 1662
7265536, Free: 4486569984}
14:41:46.324 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 1431830528, Committ
ed: 1229455360}
14:41:46.605 [DEBUG] [sun.rmi.transport.tcp] RMI TCP Connection(19)-127.0.0.1: (port 61852) connection closed
14:41:46.606 [DEBUG] [sun.rmi.transport.tcp] RMI TCP Connection(19)-127.0.0.1: close connection
14:41:47.590 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
14:41:47.594 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
14:41:47.595 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
14:41:47.595 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
14:41:47.596 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
14:41:47.597 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
14:41:47.597 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
14:41:47.598 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
14:41:47.599 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
14:41:47.599 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
14:41:50.130 [DEBUG] [sun.rmi.transport.tcp] RMI TCP Connection(20)-127.0.0.1: (port 61852) connection closed
14:41:50.130 [DEBUG] [sun.rmi.transport.tcp] RMI TCP Connection(20)-127.0.0.1: close connection
14:41:51.313 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 16627265536, Free: 448
3686400}
14:41:51.313 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 1662
7265536, Free: 4483686400}
14:41:51.314 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 1431830528, Committ
ed: 1229455360}
----- End of the daemon log --enter code here---
FAILURE: Build failed with an exception.
What went wrong:
Could not dispatch a message to the daemon.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full in
sights.
Get more help at https://help.gradle.org
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done 424.7s (!)
Gradle task assembleRelease failed with exit code 1
flutter clean
flutter build apk
I am try to learn flutter. but in first when I want to run default app in flutter(counter) I face to this error. can you help me how I can solve it?
Launching lib\main.dart on Android SDK built for x86 in debug mode…
Running Gradle task ‘assembleDebug’…
FAILURE: Build failed with an exception.
What went wrong:
Could not connect to the Gradle daemon.
Daemon uid: 7e121133-e94a-477f-b757-cb0b2f130b5e with diagnostics:
Daemon pid: 11244
log file: C:\Users\Morteza.gradle\daemon\5.6.2\daemon-11244.out.log
----- Last 20 lines from daemon log file - daemon-11244.out.log -----
23:51:11.367 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Is this a loopback interface? false
23:51:11.368 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP addresses for network interface Microsoft Wi-Fi Direct Virtual Adapter #2-Native WiFi Filter Driver-0000
23:51:11.371 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Is this a loopback interface? false
23:51:11.372 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP addresses for network interface Microsoft Wi-Fi Direct Virtual Adapter #2-QoS Packet Scheduler-0000
23:51:11.375 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Is this a loopback interface? false
23:51:11.376 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP addresses for network interface Microsoft Wi-Fi Direct Virtual Adapter #2-WFP 802.3 MAC Layer LightWeight Filter-0000
23:51:11.380 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Is this a loopback interface? false
23:51:11.383 [DEBUG] [org.gradle.internal.remote.internal.inet.TcpIncomingConnector] Listening on [dcd48d42-facd-4af7-9888-10006483df5b port:65384, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]].
23:51:11.388 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] Daemon starting at: Wed Sep 16 23:51:11 PDT 2020, with address: [dcd48d42-facd-4af7-9888-10006483df5b port:65384, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]]
23:51:11.389 [INFO] [org.gradle.launcher.daemon.server.DaemonRegistryUpdater] Advertising the daemon address to the clients: [dcd48d42-facd-4af7-9888-10006483df5b port:65384, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]]
23:51:11.389 [DEBUG] [org.gradle.launcher.daemon.server.DaemonRegistryUpdater] Advertised daemon context: DefaultDaemonContext[uid=7e121133-e94a-477f-b757-cb0b2f130b5e,javaHome=C:\Program Files\Android\Android Studio\jre,daemonRegistryDir=C:\Users\Morteza.gradle\daemon,pid=11244,idleTimeout=10800000,priority=NORMAL,daemonOpts=-Xmx1536M,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]
23:51:11.391 [DEBUG] [org.gradle.launcher.daemon.registry.PersistentDaemonRegistry] Storing daemon address: [dcd48d42-facd-4af7-9888-10006483df5b port:65384, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]], context: DefaultDaemonContext[uid=7e121133-e94a-477f-b757-cb0b2f130b5e,javaHome=C:\Program Files\Android\Android Studio\jre,daemonRegistryDir=C:\Users\Morteza.gradle\daemon,pid=11244,idleTimeout=10800000,priority=NORMAL,daemonOpts=-Xmx1536M,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]
23:51:11.405 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
23:51:11.411 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
23:51:11.420 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
23:51:11.420 [LIFECYCLE] [org.gradle.launcher.daemon.server.Daemon] Daemon server started.
23:51:11.423 [DEBUG] [org.gradle.launcher.daemon.bootstrap.DaemonStartupCommunication] Completed writing the daemon greeting. Closing streams…
23:51:11.433 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] stopOnExpiration() called on daemon
23:51:11.435 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] awaitExpiration() called on daemon
23:51:11.435 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] daemon is running. Sleeping until state changes.
----- End of the daemon log -----
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
Exception: Gradle task assembleDebug failed with exit code 1
What you can try is flutter clean flutter upgrade and Invalidate caches and restart. If you are using Android Studio/IntelliJ
I am trying to spin up Concourse using "bosh create-env concourse-lite.yml".
I am using a VM with Ubuntu to setup Concourse. Below are the sytem details and the command output.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Command Output:bosh create-env concourse-lite.yml
Deployment manifest: '/root/concourse-lite.yml'
Deployment state: '/root/concourse-lite-state.json'
Started validating
Downloading release 'concourse'... Skipped [Found in local cache] (00:00:00)
Validating release 'concourse'... Finished (00:00:03)
Downloading release 'garden-runc'... Skipped [Found in local cache] (00:00:00)
Validating release 'garden-runc'... Finished (00:00:03)
Downloading release 'bosh-virtualbox-cpi'... Skipped [Found in local cache] (00:00:00)
Validating release 'bosh-virtualbox-cpi'... Finished (00:00:03)
Validating cpi release... Finished (00:00:00)
Validating deployment manifest... Finished (00:00:00)
Downloading stemcell... Skipped [Found in local cache] (00:00:00)
Validating stemcell... Finished (00:00:03)
Finished validating (00:00:13)
Started installing CPI
Compiling package 'golang-1.8-linux/c97f9a00c26b34a3f59ca15b0f5a079d7f7e27c334cc8100248143c5dc0d4c0a'... Finished (00:00:00)
Compiling package 'golang-1.8-darwin/ee2bb46a25872469cd8fe0f4b0804bab5c39cc5512bbcc4335c8691a038d3e73'... Finished (00:00:00)
Compiling package 'virtualbox_cpi/cb3116b9b6c2111a873bb4ea14a1f3544ccdd2af'... Finished (00:00:00)
Installing packages... Finished (00:00:12)
Rendering job templates... Finished (00:00:00)
Installing job 'virtualbox_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:12)
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-trusty-go_agent/3468.1'... Skipped [Stemcell already uploaded] (00:00:00)
Started deploying
Creating VM for instance 'concourse/0' from stemcell 'sc-6196df8a-6e26-411f-70b5-0cc0466a5adf'... Failed (00:01:19)
Failed deploying (00:01:19)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
Creating instance 'concourse/0':
Creating VM:
Creating vm with stemcell cid 'sc-6196df8a-6e26-411f-70b5-0cc0466a5adf':
CPI 'create_vm' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Creating VM with agent ID '{{559adf3b-c06e-4af0-5564-6e86f5d95d81}}': Starting VM: Retried '30' times: Running command: 'VBoxManage startvm vm-e9498e46-c2ef-4772-69f0-627f95044b4a --type headless', stdout: 'Waiting for VM \"vm-e9498e46-c2ef-4772-69f0-627f95044b4a\" to power on...\n', stderr: 'VBoxManage: error: The virtual machine 'vm-e9498e46-c2ef-4772-69f0-627f95044b4a' has terminated unexpectedly during startup with exit code 1 (0x1)\nVBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine\n': exit status 1","ok_to_retry":false}
Exit code 1
Seems like an issue with VirtualBox on your machine. Some folks running on Ubuntu have also reported seeing this same error here
I have written a custom vagrant plugin (https://github.com/cthrax/guest-tinycore) that when packaged as a gem and installed with 'vagrant plugin install /path/to/gem', states that it is installed successfully. However, when attempting to run any other vagrant command against the box, the plugin functionality is not available and I get the message:
The plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via vagrant plugin. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use plugin install with a 1.0.x plugin.
However, if I take this plugin and move it into the Vagrant application itself, as a core plugin, Vagrant picks it up successfully and all functionality works.
I'm looking for some guidance as to why the packaged version is not picked up by Vagrant correctly. Below is the debug log from running 'vagrant up'. (I've removed the output from the "guest-capabilities" call, so that I can get under the character limit.
Thanks in advance for any help!
INFO global: Vagrant version: 1.3.5
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/opensuse/plugin.rb
INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#<Vagrant::Environment:0x00000100a0f928>)
INFO environment: - cwd: /Users/mbostwick/workspace/poseidon/app/vm
INFO environment: Home path: /Users/mbostwick/.vagrant.d
INFO environment: Local data path: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant
DEBUG environment: Creating: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant
DEBUG environment: Loading plugins from: /Users/mbostwick/.vagrant.d/plugins.json
INFO environment: Loading plugin from JSON: guest-tinycore
ERROR root: Failed to load plugin: guest-tinycore
ERROR root: -- Error: #<LoadError: cannot load such file -- guest-tinycore>
ERROR root: -- Backtrace:
ERROR root: /Applications/Vagrant/embedded/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/Applications/Vagrant/embedded/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant.rb:193:in `require_plugin'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:744:in `block in load_plugins'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:741:in `each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:741:in `load_plugins'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:132:in `initialize'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/bin/vagrant:74:in `new'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/bin/vagrant:74:in `<top (required)>'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `load'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>'
INFO interface: error: The plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via `vagrant plugin`. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use `plugin install` with a 1.0.x plugin.
[31mThe plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via `vagrant plugin`. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use `plugin install` with a 1.0.x plugin.
[0m
INFO environment: Running hook: environment_load
INFO environment: Initializing config...
INFO loader: Set :default = "/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb"
DEBUG loader: Populating proc cache for "/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb"
DEBUG loader: Load procs for pathname: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb
INFO loader: Set :root = #<Pathname:/Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile
INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG provisioner: Provisioner defined: shell
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostWindows::Host, VagrantPlugins::HostSlackware::Host, VagrantPlugins::HostRedHat::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins::HostArch::Host, VagrantPlugins::HostBSD::Host, VagrantPlugins::HostLinux::Host]
INFO hosts: Host class: VagrantPlugins::HostBSD::Host
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100a69a68>
INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command: -- names: []
DEBUG command: -- options: {:provider=>nil}
DEBUG command: Loading all machines...
INFO command: Active machine found with name default. Using provider: virtualbox
INFO environment: Getting machine: default (virtualbox)
INFO environment: Uncached load of machine.
INFO loader: Set :vm_default = []
INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
INFO box_collection: Searching for box: poseidon (virtualbox) in /Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/metadata.json
INFO box_collection: Box found: poseidon (virtualbox)
INFO environment: Box exists with Vagrantfile. Reloading machine config.
INFO loader: Set :box_poseidon_virtualbox = #<Pathname:/Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile
INFO loader: Loading configuration in order: [:default, :box_poseidon_virtualbox, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: box_poseidon_virtualbox (evaluating)
DEBUG loader: Upgrading config from version 1 to 2
DEBUG loader: Upgrading config to version 2
DEBUG loader: Upgraded to version 2 with 0 warnings and 0 errors
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
INFO machine: Initializing machine: default
INFO machine: - Provider: VagrantPlugins::ProviderVirtualBox::Provider
INFO machine: - Box: #<Vagrant::Box:0x00000100d4d7e8>
INFO machine: - Data dir: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant/machines/default/virtualbox
DEBUG virtualbox: Instantiating the driver for machine ID: "0dd96364-f3ae-4bbd-a116-279894338e3f"
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Name: vm_default_1382672231
Groups: /
Guest OS: Linux 2.6
UUID: 0dd96364-f3ae-4bbd-a116-279894338e3f
INFO command: With machine: default (VirtualBox (0dd96364-f3ae-4bbd-a116-279894338e3f))
INFO interface: info: Bringing machine 'default' up with 'virtualbox' provider...
INFO batch_action: Enabling parallelization by default.
INFO batch_action: Disabling parallelization because provider doesn't support it: virtualbox
INFO batch_action: Batch action will parallelize: false
INFO batch_action: Starting action: #<Vagrant::Machine:0x00000100a0b3c8> up {:destroy_on_error=>true, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
INFO machine: Calling action: up on provider VirtualBox (0dd96364-f3ae-4bbd-a116-279894338e3f)
INFO runner: Running action: #<Vagrant::Action::Builder:0x000001009ed2d8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4fe0>
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "list", "hostonlyifs"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000100ba4fb8>
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100e53a20>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x00000100e50910>
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f", "--machinereadable"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="vm_default_1382672231"
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x000001018e6f78>
INFO runner: Running action: #<Vagrant::Action::Warden:0x000001009edeb8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4ec8>
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "list", "hostonlyifs"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4ea0>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000100ba4e78>
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100cbe8b8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::IsRunning:0x00000100cbd1c0>
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f", "--machinereadable"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="vm_default_1382672231"
groups="/"
ostype="Linux 2.6"
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::IsRunning:0x00000100cbd1c0>
INFO runner: Running action: #<Vagrant::Action::Warden:0x00000100d5ea48>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::MessageAlreadyRunning:0x00000100d5e9a8>
INFO interface: info: VirtualBox VM is already running.
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::MessageAlreadyRunning:0x00000100d5e9a8>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4e78>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4ea0>
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4ec8>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4f18>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4f40>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4fb8>
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4fe0>
INFO environment: Running hook: environment_unload
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100e170c0>
This appears to have fixed itself by magic. After blowing away and cloning fresh from github the install works exactly as expected and all functionality works.