I can't even get into the VM. It's going away before the error occurs. I 
monitored it in VirtualBox after I called vagrant up. It just vanishes 
before the errors.


On Tuesday, 17 October 2017 17:21:24 UTC+1, Alvaro Miranda Aguilera wrote:
>
> Did you check inside the VM
>
> vagrant ssh -c 'df -Ph'
>
> its something related to the VM either running out of space, or /tmp 
> getting read only
>
> sometimes /tmp is from ram, ie half of available ram.
>
> Alvaro.
>
> On Tue, Oct 17, 2017 at 11:11 AM, Al Rocker <alro...@gmail.com 
> <javascript:>> wrote:
>
>> I thought you might be onto something when you said: "perhaps out of 
>> space". I had put VB VMs on a separate disk, but Vagrant boxes were 
>> still on my C drive. I have now changed that - plenty of space, but still 
>> getting this issue.
>>
>> These lines before the red errors seems odd;
>> ==> default: Forcing shutdown of VM...
>> ==> default: Destroying VM and associated drives...
>>
>>
>> On Tuesday, 17 October 2017 04:35:36 UTC+1, Alvaro Miranda Aguilera wrote:
>>>
>>> Hello
>>>
>>> Seems to me the error is coming from the box you are using.
>>>
>>> perhaps it run out of space:
>>>
>>> /tmp/vagrant-insert-pubkey-1508165525: Read-only file system 
>>> (RuntimeError)
>>>
>>> On Mon, Oct 16, 2017 at 9:57 AM, Al Rocker <alro...@gmail.com> wrote:
>>>
>>>> I was using Vagrant on a Linux host until about a year ago. Had no 
>>>> major problems then. Now my host is Windows 10 (latest vagrant and Virtual 
>>>> box versions) and I am running Vagrant from within PHP Storm. I am getting 
>>>> some problem each time I run "up" and end with a code 1. Even when trying 
>>>> from scratch with a raw, default initiated Vagrant file via command line I 
>>>> still get the issue. Any help would be much appreciated. Here's the output.
>>>>
>>>>
>>>> vagrant up
>>>> Bringing machine 'default' up with 'virtualbox' provider...
>>>> ==> default: Importing base box 'ubuntu/trusty64'...
>>>> Progress: 90%==> default: Matching MAC address for NAT networking...
>>>> ==> default: Checking if box 'ubuntu/trusty64' is up to date...
>>>> ==> default: Setting the name of the VM: 
>>>> Vagranttest2_default_1508165455296_30086
>>>> ==> default: Clearing any previously set forwarded ports...
>>>> ==> default: Fixed port collision for 22 => 2222. Now on port 2200.
>>>> ==> default: Clearing any previously set network interfaces...
>>>> ==> default: Preparing network interfaces based on configuration...
>>>>     default: Adapter 1: nat
>>>> ==> default: Forwarding ports...
>>>>     default: 22 (guest) => 2200 (host) (adapter 1)
>>>> ==> default: Booting VM...
>>>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>>>     default: SSH address: 127.0.0.1:2200
>>>>     default: SSH username: vagrant
>>>>     default: SSH auth method: private key
>>>>     default: 
>>>>     default: Vagrant insecure key detected. Vagrant will automatically 
>>>> replace
>>>>     default: this with a newly generated keypair for better security.
>>>>     default: 
>>>>     default: Inserting generated public key within guest...
>>>> ==> default: Forcing shutdown of VM...
>>>> ==> default: Destroying VM and associated drives...
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-scp-1.2.1/lib/net/scp.rb:398:in
>>>>  
>>>> `await_response_state': scp: /tmp/vagrant-insert-pubkey-1508165525: 
>>>> Read-only file system (RuntimeError)
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-scp-1.2.1/lib/net/scp.rb:369:in
>>>>  
>>>> `block (3 levels) in start_command'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/channel.rb:320:in
>>>>  
>>>> `process'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:238:in
>>>>  
>>>> `block in ev_preprocess'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:529:in
>>>>  
>>>> `each'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:529:in
>>>>  
>>>> `each_channel'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:238:in
>>>>  
>>>> `ev_preprocess'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/event_loop.rb:99:in
>>>>  
>>>> `each'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/event_loop.rb:99:in
>>>>  
>>>> `ev_preprocess'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/event_loop.rb:27:in
>>>>  
>>>> `process'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:216:in
>>>>  
>>>> `process'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:178:in
>>>>  
>>>> `block in loop'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:178:in
>>>>  
>>>> `loop'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/session.rb:178:in
>>>>  
>>>> `loop'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/connection/channel.rb:269:in
>>>>  
>>>> `wait'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/net-scp-1.2.1/lib/net/scp.rb:284:in
>>>>  
>>>> `upload!'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:291:in
>>>>  
>>>> `block in upload'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:684:in
>>>>  
>>>> `block in scp_connect'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:332:in
>>>>  
>>>> `connect'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:682:in
>>>>  
>>>> `scp_connect'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:285:in
>>>>  
>>>> `upload'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/guests/linux/cap/public_key.rb:19:in
>>>>  
>>>> `block in insert_public_key'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/tempfile.rb:295:in 
>>>> `open'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/guests/linux/cap/public_key.rb:14:in
>>>>  
>>>> `insert_public_key'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/capability_host.rb:111:in
>>>>  
>>>> `call'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/capability_host.rb:111:in
>>>>  
>>>> `capability'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/guest.rb:43:in
>>>>  
>>>> `capability'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:187:in
>>>>  
>>>> `ready?'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:83:in
>>>>  
>>>> `block in wait_for_ready'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/timeout.rb:91:in 
>>>> `block in timeout'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/timeout.rb:33:in 
>>>> `block in catch'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/timeout.rb:33:in 
>>>> `catch'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/timeout.rb:33:in 
>>>> `catch'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.3.0/timeout.rb:106:in 
>>>> `timeout'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/communicators/ssh/communicator.rb:60:in
>>>>  
>>>> `wait_for_ready'
>>>> from 
>>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in
>>>>  
>>>> `block in call'
>>>>
>>>> Process finished with exit code 1
>>>>
>>>> -- 
>>>> This mailing list is governed under the HashiCorp Community Guidelines 
>>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in 
>>>> violation of those guidelines may result in your removal from this mailing 
>>>> list.
>>>>  
>>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>>> IRC: #vagrant on Freenode
>>>> --- 
>>>> 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 vagrant-up+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/vagrant-up/3f7b7bd8-b75f-4629-b198-f3d331792133%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/vagrant-up/3f7b7bd8-b75f-4629-b198-f3d331792133%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Alvaro
>>>
>>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> 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 vagrant-up+...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/f0433abb-0c82-4358-ae01-bfb74c075e1c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/f0433abb-0c82-4358-ae01-bfb74c075e1c%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/0ca64955-0728-4ac1-b0de-a9c6be1e570f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to