[Archivesspace_Users_Group] ArchivesSpace Installation Woes

Tue May 3 17:21:31 EDT 2016

> On May 3, 2016, at 5:14 PM, Majewski, Steven Dennis (sdm7g) <sdm7g at eservices.virginia.edu> wrote:
> 
> 
> I’m guessing from that error message that you are upgrading from a previous version of ArchivesSpace and you haven’t
> run the migration script:  scripts/setup-database.sh  as in the UPGRADING instructions. 
> When it tries to connect to the database, it’s seeing that it’s a previous version of the database schema:
> 
>> Schema Info Mismatch. Expected 59, received 68 for ASPACE version v1.4.2.
> 

I guess I read that backwards: are you trying to revert to 1.4.2 from a newer pre-release version ? 

> 
> — Steve Majewski
> 
> 
> 
>> On May 3, 2016, at 4:39 PM, Chelsea Lobdell <clobdel1 at swarthmore.edu> wrote:
>> 
>> Hi, 
>> 
>> I'm am trying to install the latest release of ArchivesSpace - 1.4.2. I am installing this on a CentOS server running Java 1.8. My first step was to configure the frontend_url, backend_url, public_url, solr_url, and indexer_url. So I uncommented those with the DNS of our server (triarchive.brynmawr.edu) and tried to start it using default values for everything else. It starts fine. 
>> 
>> When I uncomment the reset of config.rb because I know I will eventually need to configure the database and a few other things, this is when I see the error. And it does not start up fine. The errors start like this: 
>> 
>> 2016-05-03 14:05:13.314:WARN:/:ERROR: initialization failed
>> org.jruby.rack.RackInitializationException: Schema Info Mismatch. Expected 59, received 68 for ASPACE version v1.4.2. |?from /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:110:in `ArchivesSpaceService'|?from /usr/local/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1356:in `configure'|?from /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:70:in `ArchivesSpaceService'|?from /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:32:in `(root)'|?from org/jruby/RubyKernel.java:1040:in `require'|?from /usr/local/archivesspace/gems/gems/jruby-jars-1.7.21/lib/jruby-stdlib-1.7.21.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:54:in `require'|?from /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in `(root)'|?from org/jruby/RubyBasicObject.java:1574:in `instance_eval'|?from /root/ArchivesSpace/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in `(root)'|?from /usr/local/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:55:in `initialize'|?from launcher/launcher.rb:86:in `start_server'|?from launcher/launcher.rb:147:in `main'|?from launcher/launcher.rb:232:in `(root)'|
>>    at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29)
>>    at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104)
>>    at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50)
>>    at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766)
>>    at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406)
>>    at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758)
>> 
>> and continue like this: 
>> SEVERE: Unable to create core: collection1
>> org.apache.solr.common.SolrException: Error opening new searcher
>>    at org.apache.solr.core.SolrCore.<init>(SolrCore.java:721)
>>        at org.apache.solr.core.SolrCore.<init>(SolrCore.java:566)
>>    at org.apache.solr.core.CoreContainer.create(CoreContainer.java:850)
>> 
>> I am thinking I may just be doing something incorrectly in the configuration file. Though, I've left everything else default aside from the frontend_url, backend_url, public_url, solr_url, and indexer_url. I also wonder if this has anything to do with the jdt-compiler jar but I was unable to find that jar in archivesspace/lib.
>> 
>> If this is not the right forum to reach for troubleshooting issues please let me know the correct place to go from technical support.
>> 
>> Thanks
>> Chelsea
>> ---------------
>> Chelsea Lobdell
>> Library Web Developer/ Swarthmore College
>> clobdel1 at swarthmore.edu / (610)690-6818
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group