Do you mean try and run "vagrant up" for the phpfun vagrant folder (its the hostname I'm using for that machine as well)?
Should I run git bash with admin rights or not? P On Friday, March 27, 2015 at 7:19:47 PM UTC-5, Alvaro Miranda Aguilera wrote: > > Ok, lets try the workaround first, then we can go to the formal > explanation. > > Can you run phpfun from the git bash ? > > > On Sat, Mar 28, 2015 at 1:10 PM, Paul Lukitsch <neuroza...@gmail.com > <javascript:>> wrote: > > There is an admin escalation during install of Vagrant, and then when > you > > run "vagrant up", but you may be right....and it doesn't require admin > > rights after the first time you run it, i.e., after vbox has already > been > > setup for the first time. In that case I am running "vagrant up" in an > > admin git bash shell. > > > > But, I did learn something that was helpful... When I install Vagrant, > it > > adds on C:\HashiCorp\Vagrant\bin; to the end of the PATH... this results > in > > the following error in Git Bash: > > > > sh.exe": /c/HashiCorp/Vagrant/embedded/gems/bin/vagrant: > > C:/Users/Administrator/12c3yemv.nal/embedded/bin/ruby.exe: bad > interpreter: > > No such file or directory > > > > AND if I run it in the Windows Command prompt (although I don't know if > this > > is due to the fact that it was run with admin rights), I would get the > > errors seen before: > > > > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:296:in > > `to_specs': Could not find 'vagrant' (>= 0) among 8 total gem(s) > > (Gem::LoadError) from > > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:307:in > > `to_spec' from > > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:47:in > > > > `gem' from C:/HashiCorp/Vagrant/embedded/gems/bin/vagrant:22:in `<main>' > > > > But in my PATH, if I make sure to move C:\HashiCorp\Vagrant\bin to a > > position before the other vagrant paths, the git paths, and the > virtualbox > > path, then I do not have those errors. > > > > However, when I am in PHPstorm and try to run vagrant up (from within > that > > application) I get a popup dialog with the exact same error as the one > above > > (the longer one).... See screenshot here: http://imgur.com/c9XZkJa > > > > I am not running PHPstorm as admin...but I am not sure it didn't ask for > any > > during install. > > > > This error is really perplexing. > > > > Thanks for all of your help!! > > > > > > On Friday, March 27, 2015 at 2:44:10 PM UTC-5, Alvaro Miranda Aguilera > > wrote: > >> > >> Hello, > >> > >> I use Windows, vagrant + virtualbox as normal user. > >> > >> Other than during install or when you create a new Virtualbox network > >> segment, it doesn't require UAC or pop ups. > >> > >> That is with the normal UAC configuration.. not sure if you are under > >> an Microsoft Active Directory environment and they have a more > >> restricted UAC? > >> > >> If you become administrator on git, what is the user you see? your own > >> or Administrator? > >> > >> In your previous email after reinstall, please send an screenshot or > >> logs of what errors do you see. > >> > >> Thanks > >> > >> On Sat, Mar 28, 2015 at 6:45 AM, Paul Lukitsch <neuroza...@gmail.com> > >> wrote: > >> > Thank you for your reply.... I did get it to work after uninstalling > >> > everything and then reinstalling it but installing vbox after > Vagrant. > >> > But > >> > that seemed like dumb luck success...but at least "vagrant up" was > >> > working > >> > and I had my environment. > >> > > >> > However, I then tried to run/configure Vagrant in PHPstorm, and when > I > >> > tried > >> > to add a box, I got the identical error. So there is an error here I > do > >> > not > >> > understand. > >> > > >> > I am going to reinstall again pursuant to your instructions right > now. > >> > However, I am installing Vagrant normally...not "Run as > Administrator" > >> > or > >> > anything. (My user has administrator privileges however). > >> > > >> > The only thing I Run as Administrator is Git Bash—which is required > so > >> > when > >> > I run "vagrant up" from within git bash, vbox doesn't prompt me 2 > times. > >> > This was recommended from what I read (probably someone on > >> > stackoverflow). > >> > > >> > In any event, I want to provide you my PATH in advance as I am > assuming > >> > I > >> > will have problems. [I ended up removing the > >> > C:\HashiCorp\Vagrant\embedded\mingw\bin; which I mention in my > original > >> > post.] > >> > > >> > PATH: > >> > > >> > > >> > > %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\wbem;C:\ProgramData\Oracle\Java\javapath;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program > > > >> > Files\Intel\WiFi\bin;C:\Program Files\Common > >> > Files\Intel\WirelessCommon;C:\Program Files > >> > (x86)\QuickTime\QTSystem;C:\Anaconda\DLLs;C:\Anaconda\LIB;C:\Program > >> > Files\Calibre2;C:\Program > >> > > >> > > Files\ImageMagick-6.8.7-Q16;C:\opt\gtk\bin;C:\Users\caleb\Desktop\Nirlauncher\SYSINTERNALS;C:\Program > > > >> > Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files > >> > (x86)\Intel\OpenCL > >> > SDK\2.0\bin\x64;C:\Android\Sdk\platform-tools;C:\Program > >> > > >> > > Files\VideoLAN\VLC;C:\HashiCorp\Vagrant\bin;C:\HashiCorp\Vagrant\embedded\bin;C:\HashiCorp\Vagrant\embedded\gems\bin;C:\Program > > > >> > Files (x86)\Git;C:\Program Files (x86)\Git\bin;C:\Program > >> > Files\Oracle\VirtualBox; > >> > > >> > > >> > I will post back whether my re-install works. > >> > > >> > Thank you!! > >> > > >> > On Tuesday, March 24, 2015 at 4:27:12 AM UTC-5, Alvaro Miranda > Aguilera > >> > wrote: > >> >> > >> >> Hello, > >> >> > >> >> Vagrant just run fine as your user, so no need to become > administrator. > >> >> > >> > > >> >> > >> >> delete c:/hashicorp and in your home delete .vagrant.d > >> >> > >> >> once that is done, log out, log in.. and as your user, install > vagrant > >> >> > >> >> After the installation, you are ask to reboot, do that. > >> >> > >> >> and in the next reboot, you should have a working environment. > >> >> > >> >> if after that you still have problems.. can you paste your full PATH > >> >> variable? > >> >> > >> >> > >> >> On Mon, Mar 23, 2015 at 9:35 PM, Paul Lukitsch <neuroza...@gmail.com> > > >> >> wrote: > >> >> > On my Windows 7 Ultimate laptop, I had Vagrant, and a couple of > >> >> > development > >> >> > environments working just fine... This wa sabout a week ago, and > then > >> >> > either > >> >> > virtualbox or Git released an updated version... Then things > seemed > >> >> > off, > >> >> > so > >> >> > I decided to uninstall everything (virtualbox, Vagrant, Git, and > >> >> > everything > >> >> > in between I could think of) and reinstall. > >> >> > > >> >> > However, for a week now I have not been able to run Vagrant... not > >> >> > bring > >> >> > up > >> >> > a box.... or do a vagrant init.... BUT ANY VAGRANT COMMAND. > >> >> > > >> >> > I have uninstalled Vagrant thoroughly... just short of > reinstalling > >> >> > Windows! > >> >> > Then I reboot, and reinstall. Then I reboot. > >> >> > > >> >> > > >> >> > I check my path... I have heard a number of different things that > >> >> > need > >> >> > to be > >> >> > in the WINDOWS Environment PATH, and some may be obsolete, but > these > >> >> > are > >> >> > the > >> >> > Vagrant related items in my path: > >> >> > > >> >> > > >> >> > C:\HashiCorp\Vagrant\embedded\bin; > >> >> > > >> >> > C:\HashiCorp\Vagrant\embedded\gems\bin; > >> >> > > >> >> > C:\HashiCorp\Vagrant\bin; > >> >> > > >> >> > C:\HashiCorp\Vagrant\embedded\mingw\bin; > >> >> > > >> >> > > >> >> > Also, before anyone asks, when installing vbox (which I do first), > I > >> >> > have > >> >> > downloaded the last version (4.3.22-09236). There is a newer > release > >> >> > as > >> >> > of a > >> >> > few days ago, but I am trying keep constants alive. I also > install > >> >> > the > >> >> > correct guest extensions. > >> >> > > >> >> > The following item is in my Windows Environment PATH: > >> >> > > >> >> > C:\Program Files\Oracle\VirtualBox; > >> >> > > >> >> > > >> >> > when I open a windows command prompt as admin, i run vboxmanage > and I > >> >> > get > >> >> > the correct response. After reboot (after Vagrant install), I > type: > >> >> > > >> >> > vagrant -version (or vagrant --version...not sure which is the > >> >> > correct > >> >> > command). But the right command (the one that should return the > >> >> > current > >> >> > version of Vagrant gives the following error: > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:296:in > >> >> > `to_specs': Could not find 'vagrant' (>= 0) among 8 total gem(s) > >> >> > (Gem::LoadError) from > >> >> > > >> >> > > >> >> > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:307:in > >> >> > `to_spec' from > >> >> > > >> >> > > >> >> > > C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:47:in > > > >> >> > `gem' from C:/HashiCorp/Vagrant/embedded/gems/bin/vagrant:22:in > >> >> > `<main>' > >> >> > > >> >> > > >> >> > What is strange about this is that rubygems is looking for > Vagrant. > >> >> > But > >> >> > right in the documentation at the Vagrant site, it states that > >> >> > Vagrant > >> >> > at > >> >> > one time was a gem file. Now it is not installed as a gem file > >> >> > unless > >> >> > you > >> >> > wish to create a development environment for a vagrant plugin. > >> >> > > >> >> > > >> >> > So why is it looking for vagrant as a gem file????? I have > searched > >> >> > for > >> >> > days on Google and I see that there is some similar problem with > >> >> > Chef. > >> >> > But > >> >> > I am not even at the point where I can start using a provisioner. > >> >> > > >> >> > > >> >> > Anyone have ANY idea what is happening? > >> >> > > >> >> > > >> >> > NB: One added piece of information.... I am sure all of you know > that > >> >> > in > >> >> > the > >> >> > last year or so, you are able to use ssh right from Git Bash, so > >> >> > instead > >> >> > of > >> >> > installing CYGWIN or use PuTTY for ssh, I just install (and only > >> >> > install) > >> >> > the Git Bash part of the Git for Windows binaries at git-scm.com > >> >> > > >> >> > > >> >> > In fact, this is why I have the line > >> >> > "C:\HashiCorp\Vagrant\embedded\mingw\bin;" in my windows PATH. I > saw > >> >> > it > >> >> > on > >> >> > Stack Overflow... it was some helpful tip to get Git to work with > >> >> > Vagrant..... but I am starting to suspect that since GIt is > written > >> >> > in > >> >> > Rails > >> >> > with Ruby that maybe this is the problem. Git is ok, but maybe > that > >> >> > line in > >> >> > the Windows PATH should not be there. Previously I used Git (a > week > >> >> > ago) > >> >> > and > >> >> > everything worked fine. I could go into Git Bash navigate to my > >> >> > synced > >> >> > folder or clone a box to a folder in a specific directory. Most > >> >> > people > >> >> > use > >> >> > Windows command line for perhaps running vagrant up or vagrant > >> >> > init... > >> >> > But > >> >> > before, I was doing everything in Git Bash. With that said... if > I > >> >> > launch > >> >> > Git Bash and run Vagrant -version, this is my error: > >> >> > > >> >> > > >> >> > sh.exe": /c/HashiCorp/Vagrant/embedded/gems/bin/vagrant: > >> >> > C:/Users/Administrator/12c3yemv.nal/embedded/bin/ruby.exe: bad > >> >> > interpreter: > >> >> > No such file or directory > >> >> > > >> >> > And I have been around enough to know that this shell command > attempt > >> >> > by > >> >> > GIt > >> >> > Bash is having issues with CRLF.... Maybe Git Bash just uses CR, > but > >> >> > since > >> >> > we are in windows, and Vagrant is designed to be installed in > WIndows > >> >> > (with > >> >> > the appropriate installer), it has all of its scripts or text > files > >> >> > with > >> >> > EOLs of CRLF. When I go into the "sh.exe" file in Git, the first > >> >> > line > >> >> > is > >> >> > commented out... and that line is > >> >> > C:/Users/Administrator/12c3yemv.nal/embedded/bin/ruby.exe —tjos is > >> >> > the > >> >> > line > >> >> > above that is Git is trying to execute... This is why I am getting > >> >> > the > >> >> > "bad > >> >> > interpreter" and the "no such file or directory"... because of the > >> >> > EOL > >> >> > encoding. WTF?? > >> >> > > >> >> > > >> >> > Anyway... I am about a week behind in having some development > >> >> > environments > >> >> > setup and am starting to twitch with frustration. > >> >> > > >> >> > > >> >> > Can anyone offer any ideas??? > >> >> > > >> >> > -- > >> >> > 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. > >> >> > For more options, visit https://groups.google.com/d/optout. > >> > > >> > -- > >> > 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. > >> > For more options, visit https://groups.google.com/d/optout. > > > > -- > > 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:>. > > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
