Hey all,
I ran through the install on Ubuntu 12.04 this morning and took a cleanup pass through the instructions, as well as checked Ed's last fix for the html5lib issue noted below. The install path should be back to a state where it's fully functional.
Best,
David.
-----Original Message-----
From: Data, API, website, and code of the Chronicling America website [mailto:[log in to unmask]] On Behalf Of Michael Beccaria
Sent: Wednesday, July 03, 2013 11:54 PM
To: [log in to unmask]
Subject: Re: Not quite
Chronam Developers,
I tried to install the latest and greatest again on Ubuntu to check out the problems Glenn had and ran into issues that seem to be related to more recent commits. Specifically,
https://github.com/LibraryOfCongress/chronam/commit/ae8711310d98a8eeee6a15d4232ebf4272bce693
The change to requirements.pip (html5lib) causes the installs to fail on Ubuntu. And somewhere along the way in the upgrade to solr 4.3 and the changes to the config files solr fails to load on Ubuntu as well. I didn't bother to troubleshoot the issues but just know that with the latest code base there are issues.
Glenn,
I would revert back to an older instance (I know around Jun 6th should work) and run the instructions found in that readme.txt file.
Hope that helps,
Mike
Mike Beccaria
Systems Librarian
Head of Digital Initiative
Paul Smith's College
518.327.6376
[log in to unmask]
Become a friend of Paul Smith's Library on Facebook today!
From: Data, API, website, and code of the Chronicling America website [mailto:[log in to unmask]] On Behalf Of Glenn Bunton
Sent: Wednesday, July 03, 2013 5:32 PM
To: [log in to unmask]
Subject: Re: Not quite
Solved the jetty/solr issue with the installation config files so that's good. Outstanding problem is still now the command
pip install -r requirements.pip
that fails with the error information already provided.
So close!!!
________________________________________
From: "Summers, Ed" <[log in to unmask]>
To: [log in to unmask]
Sent: Wednesday, June 26, 2013 8:12 AM
Subject: Re: Not quite
Hi Glenn,
Chronam doesn't care if Solr is running in a Jetty or Tomcat service container. However it is important that Solr is configured to use the chronam schema, which is independent of the container. You can find the schema xml here:
https://github.com/LibraryOfCongress/chronam/blob/master/conf/schema.xml
Let us know how it goes.
//Ed
From: Glenn Bunton [mailto:[log in to unmask]]
Sent: Tuesday, June 25, 2013 2:01 PM
To: Summers, Ed; [log in to unmask]
Subject: Re: Not quite
Hi Ed,
I haven't been able to figure out the relationship between the jetty and the solr yet.
Just as I test I wanted to see if I could install solr straight, apart from the chronam installation. I'm working on that right now and will let you know how that turns out.
Question - does chronam care if it's jetty or tomcat or would either work? I know it's configured for jetty but just wondered if there was anything jetty-specific that would not work with tomcat.
Will be back in touch with more info soon.
________________________________________
From: "Summers, Ed" <[log in to unmask]>
To: 'Glenn Bunton' <[log in to unmask]>; "[log in to unmask]" <[log in to unmask]>
Sent: Monday, June 24, 2013 12:02 PM
Subject: RE: Not quite
Hi Glenn,
Did you ever get any insight into what the jetty url was for the solr servlet? If you are still drawing a blank I would be willing to log in to the machine in question and take a look if you think it could help.
//Ed
From: Data, API, website, and code of the Chronicling America website [mailto:[log in to unmask]] On Behalf Of Glenn Bunton
Sent: Friday, June 14, 2013 1:36 PM
To: [log in to unmask]
Subject: Not quite
Hi Ed,
Thanks for the last suggestions. I did the git but I still get a 404 error when I do
http://localhost:8080/solr
Interesting comments about javac and what it's looking for. Would it make any difference if it's jdk/jre6 or jdk/jre7? I noticed both were on our server. We installed 6 with the installation instructions for chronam but it looks like the default is 7 for the basic installation. I took 7 off to see if that would make any difference but got the same error. The javac is in /usr/bin
Will keep looking around. Thanks for the continuing help.
|