Hello again. vagrant version 1.8.1
C++ installed Log file attached. Thanks. Gerard On Sunday, 13 March 2016 18:29:46 UTC+11, Alvaro Miranda Aguilera wrote: > > Hello, > > Can you check you are on current versions: > > vagrant version > > Seems you are in windows, so please install the C++ redistributable > package: > https://www.microsoft.com/en-nz/download/details.aspx?id=5555 > > And try again. > > If still fail, please run this: > > set VAGRANT_LOG=debug > vagrant up > > And share the log generated in the console > > Thanks > Alvaro > > On Sun, Mar 13, 2016 at 12:16 AM, [email protected] > <javascript:> <[email protected] <javascript:>> wrote: > >> Many thanks Alvaro. >> >> I tried both precise32 and precise64 and they both failed with SSL >> Certificate errors as shown here: >> >> [image: Inline images 1] >> >> What is my best next step? >> >> Can I bypass the security? >> >> Many thanks. >> Gerard >> >> On 12 March 2016 at 21:49, Alvaro Miranda Aguilera <[email protected] >> <javascript:>> wrote: >> >>> Hello Gerard. >>> >>> If you are in windows, the command should be: >>> >>> set VAGRANT_LOG=debug >>> >>> not the capital >>> >>> then when you run vagrant up will generate logs of log in the command >>> line, is not that will generate a file >>> >>> For Windows, check this package is installed: >>> https://www.microsoft.com/en-nz/download/details.aspx?id=5555 >>> >>> Then, the best way to troubleshoot is in the following order: >>> >>> mkdir precise32 >>> cd precise32 >>> vagrant init -m hashicorp/precise32 >>> vagrant up >>> >>> If this VM fails, then the best will be reinstall virtualbox and >>> vagrant, and reboot. >>> >>> If this command works, then test a 64 bit box is the next step >>> >>> cd .. >>> mkdir precise64 >>> cd precise64 >>> vagrant init -m hashicorp/precise64 >>> vagrant up >>> >>> If this command fails, the best is open Virtualbox, stop and star the VM >>> here and see what the message is. >>> >>> >>> Let me know how you go with those 2 test. >>> >>> Alvaro. >>> >>> >>> On 12/03/2016, at 11:05 PM, Gerard Green <[email protected] >>> <javascript:>> wrote: >>> >>> Hello. >>> >>> I am unable to SSH into my vagrant installation due to an SSH error. I >>> want to create a log file that I can post and ask for support on how to >>> resolve this issue. >>> I need to understand what commands to use in a windows 7 command prompt >>> window to get the log to go to a file rather than just displaying on the >>> screen. >>> I currently use these commands: >>> >>> >>> set vagrant_log=debug >>> >>> set stderr=vagrant.log >>> >>> vagrant up >>> >>> I am unable to locate the vagrant.log file anywhere. >>> >>> Can someone please provide suitable vagrant commands to create a log >>> file of my vagrant up command? Thanks. >>> >>> >>> >>> -- >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/80d93568-83a1-4960-b774-405d54cd9e6c%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/vagrant-up/80d93568-83a1-4960-b774-405d54cd9e6c%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> 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 a topic in the >>> Google Groups "Vagrant" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/vagrant-up/dQDheQ_b2G4/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/C8059C0D-D383-46F1-884E-4CB50A714C79%40gmail.com >>> >>> <https://groups.google.com/d/msgid/vagrant-up/C8059C0D-D383-46F1-884E-4CB50A714C79%40gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Cheers for now. >> Gerard Green >> 0413 191 512 >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/CAAyW%3DXNf2z9b-7-XyLV2aORnsraxoDYkijP%3D2dYNCLaP9PeyMg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/vagrant-up/CAAyW%3DXNf2z9b-7-XyLV2aORnsraxoDYkijP%3D2dYNCLaP9PeyMg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0407912c-178d-4940-a3b5-78f173e99b90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
nt.d/data/vagrant_login_token INFO warden: Calling OUT action: #<VagrantPlugins::LoginCommand::AddAuthenticat ion:0x42fa380> INFO box_add: Downloading box: https://atlas.hashicorp.com/hashicorp/precise32 => C:/Users/GGLaptop/.vagrant.d/tmp/boxdeb900558e30e555d08742f6e47fbcf902a8a099 INFO downloader: HEAD: https://atlas.hashicorp.com/hashicorp/precise32 INFO subprocess: Starting process: ["C:\\HashiCorp\\Vagrant\\embedded\\bin/curl .EXE", "-I", "-q", "--fail", "--location", "--max-redirs", "10", "--user-agent", "Vagrant/1.8.1 (+https://www.vagrantup.com; ruby2.2.3)", "--continue-at", "-", "-H", "Accept: application/json", "https://atlas.hashicorp.com/hashicorp/precise 32"] DEBUG subprocess: Selecting on IO DEBUG subprocess: stderr: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0cu rl: (60) SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31997 DEBUG subprocess: Exit status: 60 WARN downloader: Downloader exit code: 60 ERROR warden: Error occurred: The box 'hashicorp/precise32' could not be found o r could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. INFO warden: Beginning recovery process... INFO warden: Recovery complete. ERROR warden: Error occurred: The box 'hashicorp/precise32' could not be found o r could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. INFO warden: Beginning recovery process... INFO warden: Recovery complete. ERROR warden: Error occurred: The box 'hashicorp/precise32' could not be found o r could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. INFO warden: Beginning recovery process... INFO warden: Recovery complete. ERROR warden: Error occurred: The box 'hashicorp/precise32' could not be found o r could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. INFO warden: Beginning recovery process... INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x34b1f98> INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO warden: Recovery complete. INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO environment: Released process lock: machine-action-dbc5e5a18839842c94108f5 a74fb39af INFO environment: Running hook: environment_unload INFO runner: Preparing hooks for middleware sequence... INFO runner: 1 hooks defined. INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x41 8bdf8> ERROR vagrant: Vagrant experienced an error! Details: ERROR vagrant: #<Vagrant::Errors::BoxAddShortNotFound: The box 'hashicorp/precis e32' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.> ERROR vagrant: The box 'hashicorp/precise32' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant /action/builtin/box_add.rb:89:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder .rb:116:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `block in run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1 9:in `busy' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin /handle_box.rb:82:in `handle_box' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin /handle_box.rb:42:in `block in call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin /handle_box.rb:36:in `synchronize' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin /handle_box.rb:36:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:95:in `block in finalize_action' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder .rb:116:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `block in run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1 9:in `busy' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin /call.rb:53:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualb ox/action/check_virtualbox.rb:17:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden. rb:34:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder .rb:116:in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `block in run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1 9:in `busy' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner. rb:66:in `run' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:224 :in `action_raw' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:199 :in `block in action' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb :561:in `lock' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185 :in `call' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185 :in `action' C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/batch_action.r b:82:in `block (2 levels) in run' INFO interface: error: The box 'hashicorp/precise32' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. The box 'hashicorp/precise32' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/hashicorp/precise32";] Error: SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. INFO interface: Machine: error-exit ["Vagrant::Errors::BoxAddShortNotFound", "T he box 'hashicorp/precise32' could not be found or\ncould not be accessed in the remote catalog. If this is a private\nbox on HashiCorp's Atlas, please verify y ou're logged in via\n`vagrant login`. Also, please double-check the name. The ex panded\nURL and error message are shown below:\n\nURL: [\"https://atlas.hashicor p.com/hashicorp/precise32\"]\nError: SSL certificate problem: unable to get loca l issuer certificate\r\nMore details here: http://curl.haxx.se/docs/sslcerts.htm l\r\n\r\ncurl performs SSL certificate verification by default, using a \"bundle \"\r\n of Certificate Authority (CA) public keys (CA certs). If the default\r\n bundle file isn't adequate, you can specify an alternate file\r\n using the --ca cert option.\r\nIf this HTTPS server uses a certificate signed by a CA represent ed in\r\n the bundle, the certificate verification probably failed due to a\r\n problem with the certificate (it might be expired, or the name might\r\n not mat ch the domain name in the URL).\r\nIf you'd like to turn off curl's verification of the certificate, use\r\n the -k (or --insecure) option."] C:\adapt_authoring-master\precise32>
