-
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
Unexpected token at '' (JSON::ParserError) #10863
Comments
Hi there @andythsu - It looks like the debug log you provided does not contain the error mentioned. Do you have the debug log showing the JSON error? Also do you have a Vagrantfile? Thanks. |
Hi Brian, the debug log does not show the JSON error unfortunately, and I am not able to provide a vagrant file as it contains sensitive information. Do you really need to see the Vagrantfile? |
@briancain Also, I have updated the gist, it should show the JSON error now |
@andythsu Have you tried removing the local |
@briancain ya.. I deleted it and re-ran the command. It's proceeding without the error anymore. Hopefully it doesn't happen again. Thank you |
@andythsu - thanks! Sounds good. Sometimes that file gets corrupted but it isn't really clear how it happens. The best fix is usually just removing it and Vagrant is typically good to go! If it happens again and you figure out how it happens feel free to open another issue. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Vagrant version
Vagrant 2.2.4
Host operating system
Windows 10
Debug output
https://gist.github.com/andythsu/e7fe6c3411853413252bfee43093ffb0
Expected behavior
It should run the command without error
Actual behavior
Steps to reproduce
Notes
I have tried to uninstall vagrant, delete ~/.vagrand.d folder, and install vagrant again. The error still persists
The text was updated successfully, but these errors were encountered: