Hi, if you want to try this branch: https://github.com/hardyoyo/vagrant-dspace/tree/force-librarian-puppet-to-use-v3-api I've tested it and it still works for me. According to the Librarian-Puppet readme: https://github.com/voxpupuli/librarian-puppet if you use the following command to install puppet modules, it will use v3 of the PuppetForge API. It is my hope that this will help with your problem. Please let me know if it does work, and if so, I'll make a PR using the branch I linked above. Thanks!
librarian-puppet install --no-use-v1-api On Tue, Nov 22, 2016 at 9:39 AM, Hardy Pottinger <[email protected]> wrote: > > ==> vagrant-dspace: Unable to connect to https://forgeapi.puppetlabs.com: > end of file reached > > ==> vagrant-dspace: ( > > ==> vagrant-dspace: Faraday::ConnectionFailed > > ==> vagrant-dspace: ) > > I think this may be the clue I needed. I'll consult with the > librarian-puppet people on IRC and see if they have a suggestion. I know > (thanks to a tip from fellow committer Kim Shepherd) that the forge API > seems to require a user agent: https://forgeapi.puppetlabs. > com/#user-agent-required and that might be at play here. > > --Hardy > > On Mon, Nov 21, 2016 at 4:07 PM, Darryn Brooking < > [email protected]> wrote: > >> I'm struggling to; hence my question: where can I find more error >> messages? >> >> More to go on... >> >> Git for Windows - Git Bash reports version 2.8.1.windows.1 >> >> I think the SSH error is a red herring - i.e. it's just how vagrant is >> communicating with the VM to run the script on the VM. >> >> In trying to get it installed, so far I've encountered the following >> issues and fixed them as follows: >> >>> cable connected:off >>> >>> Insert into Vagrantfile from line 83 >>> >>> # Bugfix for "Cable connected: off" >>> config.vm.provider :virtualbox do |vm| >>> vm.customize [ >>> "modifyvm", :id, >>> "--cableconnected1", "on", >>> ] >>> end >>> >>> [edit >>> <http://www.waikato.ac.nz/wiki/isg/index.php?title=User:Darrynb/dspace&action=edit§ion=4> >>> ]Too many virtual memory requests >>> >>> disable TrendMicro Antivirus >>> [edit >>> <http://www.waikato.ac.nz/wiki/isg/index.php?title=User:Darrynb/dspace&action=edit§ion=5> >>> ]SSH error connecting to GitHubWindowsPer Windows hack in the >>> Vagrantfile line ~173, use Git Bash to create a github_rsa ssh keypair >>> in ~/.ssh and add the public key to your GitHub account. >> >> >> Full debug log attached. >> >> Here's the full (non-debug) log: >> >> D:\Dev\dspace\vagrant-dspace>vagrant up >> Bringing machine 'vagrant-dspace' up with 'virtualbox' provider... >> ==> vagrant-dspace: Importing base box 'box-cutter/ubuntu1604'... >> ==> vagrant-dspace: Matching MAC address for NAT networking... >> ==> vagrant-dspace: Checking if box 'box-cutter/ubuntu1604' is up to >> date... >> ==> vagrant-dspace: Setting the name of the VM: dspace-dev >> ==> vagrant-dspace: Clearing any previously set network interfaces... >> ==> vagrant-dspace: Preparing network interfaces based on configuration... >> vagrant-dspace: Adapter 1: nat >> vagrant-dspace: Adapter 2: hostonly >> ==> vagrant-dspace: Forwarding ports... >> vagrant-dspace: 8080 (guest) => 8080 (host) (adapter 1) >> vagrant-dspace: 5432 (guest) => 5432 (host) (adapter 1) >> vagrant-dspace: 22 (guest) => 2222 (host) (adapter 1) >> ==> vagrant-dspace: Running 'pre-boot' VM customizations... >> ==> vagrant-dspace: Booting VM... >> ==> vagrant-dspace: Waiting for machine to boot. This may take a few >> minutes... >> vagrant-dspace: SSH address: 127.0.0.1:2222 >> vagrant-dspace: SSH username: vagrant >> vagrant-dspace: SSH auth method: private key >> vagrant-dspace: >> vagrant-dspace: Vagrant insecure key detected. Vagrant will >> automatically replace >> vagrant-dspace: this with a newly generated keypair for better >> security. >> vagrant-dspace: >> vagrant-dspace: Inserting generated public key within guest... >> vagrant-dspace: Removing insecure key from the guest if it's >> present... >> vagrant-dspace: Key inserted! Disconnecting and reconnecting using >> new SSH key... >> ==> vagrant-dspace: Machine booted and ready! >> ==> vagrant-dspace: Checking for guest additions in VM... >> vagrant-dspace: The guest additions on this VM do not match the >> installed version of >> vagrant-dspace: VirtualBox! In most cases this is fine, but in rare >> cases it can >> vagrant-dspace: prevent things such as shared folders from working >> properly. If you see >> vagrant-dspace: shared folder errors, please make sure the guest >> additions within the >> vagrant-dspace: virtual machine match the version of VirtualBox you >> have installed on >> vagrant-dspace: your host and reload your VM. >> vagrant-dspace: >> vagrant-dspace: Guest Additions Version: 5.1.6 >> vagrant-dspace: VirtualBox Version: 5.0 >> ==> vagrant-dspace: Setting hostname... >> ==> vagrant-dspace: Configuring and enabling network interfaces... >> ==> vagrant-dspace: Mounting shared folders... >> vagrant-dspace: /vagrant => D:/Dev/dspace/vagrant-dspace >> vagrant-dspace: /tmp/vagrant-puppet/manifests- >> 5058f1af8388633f609cadb75a75dc9d => D:/Dev/dspace/vagrant-dspace >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: Setting locale to UTF-8 (en_US.UTF-8)... >> ==> vagrant-dspace: Generating locales (this might take a while)... >> ==> vagrant-dspace: en_AG.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_AU.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_BW.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_CA.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_DK.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_GB.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_HK.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_IE.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_IN.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_NG.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_NZ.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_PH.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_SG.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_US.ISO-8859-1 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_US.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_ZA.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_ZM.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: en_ZW.UTF-8 >> ==> vagrant-dspace: ... >> ==> vagrant-dspace: done >> ==> vagrant-dspace: Generation complete. >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: Turning off console beeps... >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: Windows-specific: Copying local GitHub SSH Key to VM >> for provisioning... >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: Testing SSH connection to GitHub on VM... >> ==> vagrant-dspace: Hi darrynb! You've successfully authenticated, but >> GitHub does not provide shell access. >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: > > > running default increase-swap.sh scripte to >> ensure enough memory is available, via a swap file. >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: C:/Users/darrynb/AppData/Local >> /Temp/vagrant-shell20161115-5540-163msjb.sh >> ==> vagrant-dspace: swapfile not found. Adding swapfile. >> ==> vagrant-dspace: Setting up swapspace version 1, size = 7.8 GiB >> (8388603904 bytes) >> ==> vagrant-dspace: no label, UUID=ec43315b-d0cc-43bc-a24d-a592e2e92693 >> ==> vagrant-dspace: Filesystem >> Size Used Avail Use% Mounted on >> ==> vagrant-dspace: udev >> 982M 0 982M 0% /dev >> ==> vagrant-dspace: tmpfs >> 201M 3.2M 197M 2% /run >> ==> vagrant-dspace: /dev/mapper/vagrant--vg-root >> 62G 9.0G 50G 16% / >> ==> vagrant-dspace: tmpfs >> 1001M 0 1001M 0% /dev/shm >> ==> vagrant-dspace: tmpfs >> 5.0M 0 5.0M 0% /run/lock >> ==> vagrant-dspace: tmpfs >> 1001M 0 1001M 0% /sys/fs/cgroup >> ==> vagrant-dspace: /dev/sda1 >> 472M 55M 393M 13% /boot >> ==> vagrant-dspace: tmpfs >> 100K 0 100K 0% /run/lxcfs/controllers >> ==> vagrant-dspace: tmpfs >> 201M 0 201M 0% /run/user/1000 >> ==> vagrant-dspace: vagrant >> 1.9T 641G 1.2T 35% /vagrant >> ==> vagrant-dspace: tmp_vagrant-puppet_manifests-5 >> 058f1af8388633f609cadb75a75dc9d 1.9T 641G 1.2T 35% >> /tmp/vagrant-puppet/manifests-5058f1af8388633f609cadb75a75dc9d >> ==> vagrant-dspace: Filename Type >> Size Used Priority >> ==> vagrant-dspace: /dev/dm-1 partition >> 524284 0 -1 >> ==> vagrant-dspace: /swapfile file >> 8191996 0 -2 >> ==> vagrant-dspace: SwapCached: 0 kB >> ==> vagrant-dspace: SwapTotal: 8716280 kB >> ==> vagrant-dspace: SwapFree: 8716280 kB >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: inline script >> ==> vagrant-dspace: > > > running default apt-spy2 to locate a nearby >> mirror (for quicker installs). Do not worry if it shows an error, it will >> be OK, there is a fallback. >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: C:/Users/darrynb/AppData/Local >> /Temp/vagrant-shell20161115-5540-93epw9.sh >> ==> vagrant-dspace: Initial apt-get update... >> ==> vagrant-dspace: Installing 'apt-spy2'. This tool lets us >> autoconfigure your 'apt' sources.list to a nearby location. >> ==> vagrant-dspace: This may take a while... >> ==> vagrant-dspace: dpkg-preconfigure: unable to re-open stdin: No such >> file or directory >> ==> vagrant-dspace: Updating RubyGems... >> ==> vagrant-dspace: Successfully installed rubygems-update-2.6.8 >> ==> vagrant-dspace: 1 gem installed >> ==> vagrant-dspace: Installing apt-spy2 (and prerequisites)... >> ==> vagrant-dspace: Successfully installed mini_portile2-2.1.0 >> ==> vagrant-dspace: Building native extensions. This could take a >> while... >> ==> vagrant-dspace: Successfully installed nokogiri-1.6.8.1 >> ==> vagrant-dspace: Successfully installed colored-1.2 >> ==> vagrant-dspace: Successfully installed thor-0.19.1 >> ==> vagrant-dspace: Successfully installed apt-spy2-0.5.0 >> ==> vagrant-dspace: 5 gems installed >> ==> vagrant-dspace: ... apt-spy2 installed! >> ==> vagrant-dspace: ... Setting 'apt' sources.list for closest mirror to >> country=NZ >> ==> vagrant-dspace: Mirror: http://ucmirror.canterbury.ac.nz/ubuntu/ - UP >> ==> vagrant-dspace: Mirror: http://ftp.citylink.co.nz/ubuntu/ - UP >> ==> vagrant-dspace: Mirror: http://nz.archive.ubuntu.com/ubuntu/ - UP >> ==> vagrant-dspace: Mirror: http://archive.ubuntu.com/ubuntu/ - UP >> ==> vagrant-dspace: The closest mirror is: >> ==> vagrant-dspace: Updating /etc/apt/sources.list >> ==> vagrant-dspace: Updated '/etc/apt/sources.list' with >> ==> vagrant-dspace: Run `apt-get update` to update >> ==> vagrant-dspace: Re-running apt-get update after sources updated... >> ==> vagrant-dspace: E >> ==> vagrant-dspace: : >> ==> vagrant-dspace: Malformed entry 2 in list file /etc/apt/sources.list >> (URI parse) >> ==> vagrant-dspace: E >> ==> vagrant-dspace: : >> ==> vagrant-dspace: The list of sources could not be read. >> ==> vagrant-dspace: Initial apt-get update failed. Trying a different >> mirror as a fallback... >> ==> vagrant-dspace: The closest mirror is: http://ucmirror.canterbury.ac. >> nz/ubuntu/ >> ==> vagrant-dspace: Updating /etc/apt/sources.list >> ==> vagrant-dspace: Updated '/etc/apt/sources.list' with >> http://ucmirror.canterbury.ac.nz/ubuntu/ >> ==> vagrant-dspace: Run `apt-get update` to update >> ==> vagrant-dspace: Re-running apt-get update after sources updated >> (again)... >> ==> vagrant-dspace: Running provisioner: shell... >> vagrant-dspace: Running: C:/Users/darrynb/AppData/Local >> /Temp/vagrant-shell20161115-5540-q9o8rq.sh >> ==> vagrant-dspace: Installing wget... >> ==> vagrant-dspace: Installing Puppet... >> ==> vagrant-dspace: Puppet installed! >> ==> vagrant-dspace: Installing Git... >> ==> vagrant-dspace: dpkg-preconfigure: unable to re-open stdin: No such >> file or directory >> ==> vagrant-dspace: Git installed! >> ==> vagrant-dspace: Installing librarian-puppet... >> ==> vagrant-dspace: librarian-puppet installed! >> ==> vagrant-dspace: Installing third-party Puppet modules (via >> librarian-puppet)... >> ==> vagrant-dspace: /usr/local/bin/librarian-puppet >> ==> vagrant-dspace: : >> ==> vagrant-dspace: Unable to connect to https://forgeapi.puppetlabs.com: >> end of file reached >> ==> vagrant-dspace: ( >> ==> vagrant-dspace: Faraday::ConnectionFailed >> ==> vagrant-dspace: ) >> 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. >> >> D:\Dev\dspace\vagrant-dspace>==> vagrant-dspace: ) >> 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. >> >> D:\Dev\dspace\vagrant-dspace> >> >> On Tue, Nov 22, 2016 at 10:33 AM, Hardy Pottinger < >> [email protected]> wrote: >> >>> Hi, Darryn, can you give us more to go on? >>> >>> --Hardy >>> >>> On Nov 21, 2016 2:11 PM, "Darryn Brooking" < >>> [email protected]> wrote: >>> >>>> Any thoughts on why librarian-puppet is failing? places to find more >>>> error messages? >>>> >>>> On Tue, Nov 22, 2016 at 5:02 AM, Hardy Pottinger < >>>> [email protected]> wrote: >>>> >>>>> Done: https://github.com/DSpace/vagrant-dspace/blob/master/R >>>>> EADME.md#requirements >>>>> >>>>> On Mon, Nov 21, 2016 at 9:26 AM, Tim Donohue <[email protected]> >>>>> wrote: >>>>> >>>>>> Yes, glad to hear the solution was found. It *sounds* like this may >>>>>> be directly related to the fact that vagrant-dspace is now using Ubuntu >>>>>> 16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered, >>>>>> OpenSSH 7 *disallows* DSA keys by default: >>>>>> http://viryagroup.com/what-we-do/our-blog-posts/hosting-and- >>>>>> linux-server-managment-blog/ssh-keys-failing-in-ubuntu-16-04 >>>>>> -xenial-with-permission-denied-publickey >>>>>> >>>>>> So, if others are hitting this issue, you should make sure you are >>>>>> using an *RSA* SSH Key >>>>>> >>>>>> BTW, Hardy or Andrea, could you post an updated note to the >>>>>> vagrant-dspace setup/installation instructions about this? It sounds >>>>>> like >>>>>> it may be something worth noting in the README at >>>>>> https://github.com/DSpace/vagrant-dspace >>>>>> >>>>>> - Tim >>>>>> >>>>>> >>>>>> On 11/20/2016 5:02 PM, Andrea Schweer wrote: >>>>>> >>>>>>> Hi Hardy, all, >>>>>>> >>>>>>> On 11/19/2016 06:49 AM, Hardy Pottinger wrote: >>>>>>> >>>>>>>> OK, here's a shot in the dark, and it will require you taking a >>>>>>>> leap back as it were, if in addition to destroying your vagrant >>>>>>>> environment >>>>>>>> you also delete the box image Vagrant has cached away for you: >>>>>>>> >>>>>>>> in your Vagrant-DSpace folder, run: >>>>>>>> >>>>>>>> vagrant box remove box-cutter/ubuntu1604 >>>>>>>> vagrant destroy -f >>>>>>>> >>>>>>> >>>>>>> Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest >>>>>>> installed, running on Ubuntu 16.04 with ssh agent that has a key in it >>>>>>> that >>>>>>> lets it pull from DSpace/DSpace via git. >>>>>>> >>>>>>> When I vagrant ssh to the box, I see the ssh key (via ssh-add -L). >>>>>>> >>>>>>> ssh -T -oStrictHostKeyChecking=no [email protected] >>>>>>> still gets >>>>>>> Permission denied (publickey). >>>>>>> >>>>>>> Same command on the host gets >>>>>>> Hi [username]! You've successfully authenticated, but GitHub does >>>>>>> not provide shell access. >>>>>>> >>>>>>> Aha -- I may have solved the mystery? My key is an old one (dsa). On >>>>>>> the host, my ssh config has >>>>>>> Host github.com >>>>>>> PubkeyAcceptedKeyTypes +ssh-dss >>>>>>> >>>>>>> When I add that on the vagrant box, I get the successful auth >>>>>>> message just like on the host. >>>>>>> >>>>>>> So, I then generated an rsa key and added that to my github profile >>>>>>> + the ssh agent on the host. This does indeed get me past the ssh >>>>>>> problem, >>>>>>> and through to a successful vagrant up - yay! I guess the alternative to >>>>>>> generating a new key would be to make sure the ssh config option ends >>>>>>> up on >>>>>>> the vagrant box. >>>>>>> >>>>>>> [I still need to work out how to build the 5.x branch but I'm >>>>>>> guessing the problems I ran into there are from the build.properties -> >>>>>>> local.cfg change.] >>>>>>> >>>>>>> cheers, >>>>>>> Andrea >>>>>>> >>>>>>> >>>>>> -- >>>>>> Tim Donohue >>>>>> Technical Lead for DSpace & DSpaceDirect >>>>>> DuraSpace.org | DSpace.org | DSpaceDirect.org >>>>>> >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "DSpace Technical Support" group. >>>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>>> pic/dspace-tech/rv9GNuoGsvo/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "DSpace Technical Support" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
