Hi, Monika, I was able to reproduce a problem with running vagrant up, and have created an issue for it:
https://jira.duraspace.org/browse/DS-2014 I've also managed to manually fix the problem, with a bit of tinkering, and have a reproducible solution in the works. I will make the PR for DS-2014 as soon as I confirm I've addressed the issue reliably. I will merge the PR myself, so, hopefully things should be working for you (after you pull the upstream version of Vagrant-DSpace)... some time tomorrow. In a nutshell, Tomcat 7 is currently trying to run with Java 1.6. Current DSpace won't work with Java 1.6. As a bit of troubleshooting advice, Vagrant-DSpace sets up a copy of PsiProbe[1], you can access it at http://localhost:808/probe. Psi Probe is a great tool for getting a peek at what's going on with Tomcat. That's how I spotted what version of Java was being used. It's so handy, I recommend running it wherever you run Tomcat. --Hardy [1] https://code.google.com/p/psi-probe/ ________________________________________ From: Monika Mevenkamp [moni...@princeton.edu] Sent: Tuesday, May 27, 2014 4:27 PM To: Pottinger, Hardy J.; Monika Mevenkamp; dspace-devel@lists.sourceforge.net Subject: Re: [Dspace-devel] vagrant up fails Now that I added a public key to GitHub vagrant does come up I can ssh into the box, I can see that tomcat is running, a postgres server is up, but >> wget http://localhost:8080/xmlui/ --2014-05-27 17:19:17-- http://localhost:8080/xmlui/ Resolving localhost... ::1, 127.0.0.1, fe80::1 Connecting to localhost|::1|:8080... failed: Connection refused. Connecting to localhost|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... 404 Not Found 2014-05-27 17:19:17 ERROR 404: Not Found. Running nmap on my local box says: >> nmap -p 8080 localhost Starting Nmap 6.40 ( http://nmap.org ) at 2014-05-27 17:23 EDT Nmap scan report for localhost (127.0.0.1) Host is up (0.00010s latency). PORT STATE SERVICE 8080/tcp open http-proxy -------- logging into the vagrant box tells me >> vagrant ssh Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.2.0-23-generic x86_64) * Documentation: https://help.ubuntu.com/ Welcome to your Vagrant-built virtual machine. Last login: Tue May 27 21:10:13 2014 from 10.0.2.2 >> nmap -p 8080 localhost Starting Nmap 5.21 ( http://nmap.org ) at 2014-05-27 21:26 UTC Nmap scan report for localhost (127.0.0.1) Host is up (0.00011s latency). PORT STATE SERVICE 8080/tcp open http-proxy Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds -------- after vagrant suspend - nmap tells me that the port is closed Any tips anybody ? Monika On 5/27/14, 3:17 PM, Pottinger, Hardy J. wrote: > Hi, I answered my own question by reading your entire e-mail, you did clone > Vagrant-DSpace from git, so, I assume you already have Git set up on your > machine. I read your log file you attached, and this line looks like it might > be the main symptom: > > [0m[0;32mInvalid module name 'tomcat', you should qualify it with > 'ORGANIZATION/tomcat' for resolution to work correctly > > I will see if I can reproduce this error, and if so, I'll let you know. > > --Hardy > ________________________________________ > From: Pottinger, Hardy J. > Sent: Tuesday, May 27, 2014 1:57 PM > To: Monika Mevenkamp; dspace-devel@lists.sourceforge.net > Subject: Re: [Dspace-devel] vagrant up fails > > Hi, Monika, just a quick question, do you already have Git installed on this > Mac, and have you already cloned DSpace somewhere on this Mac? I use > Vagrant-DSpace on my mac and it works quite well, so I'm sure we can work it > out. > > --Hardy > ________________________________________ > From: Monika Mevenkamp [moni...@princeton.edu] > Sent: Monday, May 26, 2014 1:49 PM > To: dspace-devel@lists.sourceforge.net > Subject: [Dspace-devel] vagrant up fails > > I tried to install dspace vargrant from git hub on my mac: > > git clone https://github.com/DSpace/vagrant-dspace.git > cd vagrant-dspace > vagrant up > > Even after vagrant destroy and vagrant up I get errors, see the > attached the first trace. > After trying this several times I guess that all problems start with > vagrant complaining: > > stdin: is not a tty > > and the later on > > Error: ssh -T -oStrictHostKeyChecking=no g...@github.com returned 255 > instead of one of [1] > > I'd appreciate any tips > > Monika > > > > > ------------------------------------------------------------------------------ > The best possible search technologies are now affordable for all companies. > Download your FREE open source Enterprise Search Engine today! > Our experts will assist you in its installation for $59/mo, no commitment. > Test it for FREE on our Cloud platform anytime! > http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Monika Mevenkamp phone: 609-258-4161 Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 08544 ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
