[Archivesspace_Users_Group] ASpace and Apache revisited

Kevin Clair Kevin.Clair at du.edu
Fri Jul 31 11:06:37 EDT 2015

When we first migrated, we also had timeout issues during the initial index round. We were able to add more memory to the VM ArchivesSpace runs on, which solved the problem for us, but if you can’t do that you can also adjust the number of CPU cores ArchivesSpace uses to index and the number of records it indexes at a time, which lengthens the amount of time the index takes but is less resource-intensive.

I think the :indexer_records_per_thread and :indexer_thread_count settings are 25 and 4 out of the box, respectively; I have it set to 20 and 2 on my test VMs because they have less memory and processing power than our production server.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suda, Phillip J
Sent: Friday, July 31, 2015 8:56 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace and Apache revisited

I confirmed that the ports are open. I do not see any errors but it still seems to be indexing (“running index round…”).

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steven Majewski
Sent: Friday, July 31, 2015 9:50 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ASpace and Apache revisited

Firewall settings ?  ( Always my first suspicion when using a non standard port # )
Can you access it from the localhost ?

Any errors in the logfile on startup ?

— Steve Majewski

On Jul 31, 2015, at 10:28 AM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:

Greetings all,

              We have ASpace 1.3.0 up and running on a dev server. We are able to get to localhost:8080 (staff interface) but we are unable to get localhost:8081 open. We are getting timeout errors, etc. The config settings are listed below:

AppConfig[:backend_url] = "http://localhost:8089<http://localhost:8089/>"
AppConfig[:frontend_url] = "http://localhost:8080<http://localhost:8080/>"
AppConfig[:frontend_prefix] = proc { "#{URI(AppConfig[:frontend_url]).path}/".gsub(%r{/+$}, "/") }
AppConfig[:solr_url] = "http://localhost:8090<http://localhost:8090/>"
AppConfig[:indexer_url] = "http://localhost:8091<http://localhost:8091/>"
AppConfig[:public_url] = "http://localhost:8081<http://localhost:8081/>"
AppConfig[:public_prefix] = proc { "#{URI(AppConfig[:public_url]).path}/".gsub(%r{/+$}, "/") }

The Apache config is

Ataspace.tulane.edu<http://ataspace.tulane.edu/>:8080 (staff)
Ataspace.tulane.edu<http://ataspace.tulane.edu/>:8081 (public)



Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150731/6f3a7482/attachment.html>

More information about the Archivesspace_Users_Group mailing list