> On Dez. 24, 2015, 9:23 nachm., Andreas Kotes wrote: > > Fedora doesn't seem to be so lucky :( > > > > $ vagrant up fedora > > Bringing machine 'fedora' up with 'virtualbox' provider... > > ==> fedora: Importing base box 'fedora/23-cloud-base'... > > ==> fedora: Matching MAC address for NAT networking... > > ==> fedora: Checking if box 'fedora/23-cloud-base' is up to date... > > ==> fedora: Setting the name of the VM: Apache Wave dev - Fedora > > ==> fedora: Clearing any previously set network interfaces... > > ==> fedora: Preparing network interfaces based on configuration... > > fedora: Adapter 1: nat > > ==> fedora: Forwarding ports... > > fedora: 9898 (guest) => 9898 (host) (adapter 1) > > fedora: 9898 (guest) => 9898 (host) (adapter 1) > > fedora: 22 (guest) => 2222 (host) (adapter 1) > > ==> fedora: Running 'pre-boot' VM customizations... > > ==> fedora: Booting VM... > > ==> fedora: Waiting for machine to boot. This may take a few minutes... > > fedora: SSH address: 127.0.0.1:2222 > > fedora: SSH username: vagrant > > fedora: SSH auth method: private key > > fedora: > > fedora: Vagrant insecure key detected. Vagrant will automatically > > replace > > fedora: this with a newly generated keypair for better security. > > fedora: > > fedora: Inserting generated public key within guest... > > fedora: Removing insecure key from the guest if it's present... > > fedora: Key inserted! Disconnecting and reconnecting using new SSH > > key... > > ==> fedora: Machine booted and ready! > > ==> fedora: Checking for guest additions in VM... > > fedora: No guest additions were detected on the base box for this VM! > > Guest > > fedora: additions are required for forwarded ports, shared folders, > > host only > > fedora: networking, and more. If SSH fails on this machine, please > > install > > fedora: the guest additions and repackage the box to continue. > > fedora: > > fedora: This is not an error message; everything may continue to work > > properly, > > fedora: in which case you may ignore this message. > > ==> fedora: Rsyncing folder: /home/count/incubator-wave/ => /vagrant > > There was an error when attempting to rsync a synced folder. > > Please inspect the error message below for more info. > > > > Host path: /home/count/incubator-wave/ > > Guest path: /vagrant > > Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX > > --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o > > ControlMaster=auto -o ControlPath=C:/cygwin64/tmp/ssh.903 -o > > ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o > > UserKnownHostsFile=/dev/null -i > > 'C:/cygwin64/home/count/incubator-wave/.vagrant/machines/fedora/virtualbox/private_key' > > --exclude .vagrant/ /home/count/incubator-wave/ vagrant@127.0.0.1:/vagrant > > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of > > known hosts. > > mm_receive_fd: no message header > > process_mux_new_session: failed to receive fd 0 from slave > > mux_client_request_session: read from master failed: Connection reset by > > peer > > Failed to connect to new control master > > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > > rsync error: error in rsync protocol data stream (code 12) at io.c(226) > > [sender=3.1.1] > > > > > > $ > > Evan Hughes wrote: > Looks like this is a vagrant side issue with not being able to bind to > the host, you may want to try again or `vagrant provision fedora` to see if > it can continue.
vagrant provision has other issues: ==> fedora: Complete! ==> fedora: /tmp/vagrant-shell: line 29: ./gradlew: No such file or directory ==> fedora: /tmp/vagrant-shell: line 30: cd: distributions: No such file or directory ==> fedora: tar: ==> fedora: apache-wave-bin-0.4.tar: Cannot open ==> fedora: : No such file or directory ==> fedora: tar: ==> fedora: Error is not recoverable: exiting now ==> fedora: cp: ==> fedora: cannot stat ‘scripts/vagrant/application.conf’ ==> fedora: : No such file or directory The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. vagrant up fails reliably ;) Root cause is Windows-specific and known, https://github.com/mitchellh/vagrant/issues/6702 which was introduced to Vagrant 1.8.0 per https://github.com/mitchellh/vagrant/commit/6e6172ee775c875101171991f41930076d23c77e With the fix mentioned in the Vagrant issue in place it works perfectly fine, Apache Wave server can be started and serves as expected! \o/ - Andreas ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/41700/#review111879 ----------------------------------------------------------- On Dez. 25, 2015, 11:11 vorm., Evan Hughes wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/41700/ > ----------------------------------------------------------- > > (Updated Dez. 25, 2015, 11:11 vorm.) > > > Review request for wave, Ali Lown and Yuri Zelikov. > > > Repository: wave > > > Description > ------- > > Adds vagrant config for linux and windows vm's > > > Diffs > ----- > > .gitignore b8ef753 > README.md 3be1780 > Vagrantfile PRE-CREATION > release/artifact-sign.sh 004d5f0 > scripts/release/artifact-sign.sh PRE-CREATION > scripts/vagrant/application.conf PRE-CREATION > scripts/vagrant/setup-fedora.sh PRE-CREATION > scripts/vagrant/setup-ubuntu.sh PRE-CREATION > scripts/vagrant/setup-win-choco.cmd PRE-CREATION > scripts/vagrant/setup-win.cmd PRE-CREATION > wave/build.gradle ca39a6d > wave/config/reference.conf 04753c4 > > Diff: https://reviews.apache.org/r/41700/diff/ > > > Testing > ------- > > Can run server in all vm's (fedora, ubuntu, win 10) > > > Thanks, > > Evan Hughes > >
