-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.5.1 - JSON Parse Error #3192
Comments
That's really bizarre. I'm looking at the stack trace and can't actually see what is causing this. Can you attach a debug log? |
Is there a flag I need for that? I downgraded to 1.5.0 in order to continue working but I can upgrade in a bit to see if we can resolve this. |
|
https://gist.github.com/spiffyjr/9535607 Hopefully that's enough of a dump for you. |
Closing, wasn't prompted to restart but a restart seems to have fixed the issue. Restarts, the cure all for Windows. |
And, it's back. |
It looks like if I cancel an up mid-process then this error shows itself. Removing Vagrant, deleting ~/.vagrant.id/* and then installing vagrant again fixes it until I cancel the up process mid-way. |
It appears the return result from https://github.com/mitchellh/vagrant/blob/master/plugins/synced_folders/smb/synced_folder.rb#L133 |
The command array for https://github.com/mitchellh/vagrant/blob/master/lib/vagrant/util/powershell.rb#L20 is
and when I run it via command line I get the correct results of: {
"ip_addresses": [
"192.168.11.33",
"fe80::a00e:9dcf:92da:91c9",
"192.168.237.42",
"fe80::7515:8a1b:b806:aac2",
"192.168.255.1",
"fe80::dda1:5d27:d93e:8791",
"192.168.57.1",
"fe80::e8f8:359a:2bc7:e63c"
]
} It looks like, for whatever reason, powershell isn't executing that script correctly? |
@mitchellh Solution posted in #3100 too. #3100 caused this issue. I modified the line (without testing) to |
I am seeing this issue after updating to 1.5.1 on Windows 8.1 with VirtualBox 4.3.8. At the moment, I cannot
|
Fixed by #3210 |
When will this be available in an msi ? I have the exact same issue. |
Just updated to 1.5.1 and I'm receiving a JSON parse error. This Vagrant config was working properly in 1.5.0.
The text was updated successfully, but these errors were encountered: