[Archivesspace_Users_Group] v1.1.0 maintenance plugin
Chris Fitzpatrick
Chris.Fitzpatrick at lyrasis.org
Tue Nov 11 17:14:08 EST 2014
Hi Brent,
So, what's happened is the database migrator is starting at migration 031, which it's actually already done, at least partially. I've seen this once before, and I'm still not sure what happened...something interrupted the migration process part way.
Can I ask if you're running Windows or Linux?
I can walk you through how to fix this or if you'd rather can you send me a database dump and I can quickly run the migrations and verify that all the tables are completed?
b,chris.
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: Brent Ellingson <brent_ellingson at byu.edu>
Sent: Tuesday, November 11, 2014 3:56 PM
To: Chris Fitzpatrick; Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)
Cc: Brent Ellingson (bellingson at byu.edu)
Subject: RE: v1.1.0 maintenance plugin
Chris,
I ran the setup-database.sh script and got the following error:
Loading ArchivesSpace configuration file from path: /opt/archivesspace/config/config.rb
Loading ArchivesSpace configuration file from path: /opt/archivesspace/config/config.rb
Running migrations against jdbc:mysql://localhost:3306/archivesspace100?user=XXXXX&password=XXXXX&useUnicode=true&characterEncoding=UTF-8
Sequel::DatabaseError: Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'related_accession_rlshp' already exists
raise_error at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/database/misc.rb:313
statement at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:563
statement at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:561
execute at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:255
hold at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/connection_pool/threaded.rb:104
hold at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/connection_pool/threaded.rb:93
synchronize at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/database/connecting.rb:240
execute at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:254
execute_ddl at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:277
create_table_from_generator at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/database/schema_methods.rb:532
create_table at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/database/schema_methods.rb:169
(root) at file:/opt/archivesspace-1.1.0/lib/common.jar!/db/migrations/031_add_accession_relationships.rb:12
instance_eval at org/jruby/RubyBasicObject.java:1536
apply at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:94
run at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:519
checked_transaction at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:456
run at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:518
each at org/jruby/RubyArray.java:1613
run at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:514
run at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/extensions/migration.rb:381
setup_database at file:/opt/archivesspace-1.1.0/lib/common.jar!/db/db_migrator.rb:184
(root) at ../scripts/rb/migrate_db.rb:43
connect at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/database/connecting.rb:80
connect at /opt/archivesspace-1.1.0/gems/gems/sequel-3.41.0/lib/sequel/core.rb:147
(root) at ../scripts/rb/migrate_db.rb:28
Any ideas on what to try next?
Thank you for your help.
Regards,
__________________________
Brent Ellingson
Software Developer
2750 Harold B. Lee Library
Brigham Young University
(801)422-6148
From: Chris Fitzpatrick [mailto:Chris.Fitzpatrick at lyrasis.org]
Sent: Sunday, November 09, 2014 10:54 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)
Cc: Brent Ellingson (bellingson at byu.edu)
Subject: Re: v1.1.0 maintenance plugin
Hi Cory,
It sounds like when you did the upgrade you skipped the "setup-database.sh" step? The "accession_parts_relator" is added to the database as part of the migration process. Can you try and run the "scripts/setup-database.sh/.bat" step and see if that resolves it?
b,chris.
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Cory Nimer <cory_nimer at byu.edu<mailto:cory_nimer at byu.edu>>
Sent: Saturday, November 08, 2014 12:14 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>)
Cc: Brent Ellingson (bellingson at byu.edu<mailto:bellingson at byu.edu>)
Subject: [Archivesspace_Users_Group] FW: v1.1.0 maintenance plugin
We recently upgraded our development server environment from 1.0.9 to 1.1, and afterward have not been able to update Accession records. The records can be viewed, but when clicking on Edit we receive the "We're sorry, something's gone wrong" message. Our technical support staff don't know what is causing the error, but forwarded the following entry from the error log:
|ActionView::Template::Error (key not found: accession_parts_relator):| 1: <%= setup_context(:object => @accession, :title => @accession.display_string) %>| 2: | 3: <%= form_for @accession, :as => "accession", :url => {:action => :update}, :html => {:class => 'form-horizontal aspace-record-form', :id => "accession_form"}.merge(update_monitor_params(@accession)) do |f| %>| 4: <%= form_context :accession, @accession do |form| %>| 5: <div class="row-fluid">| 6: <div class="span3">| 7: <%= render_aspace_partial :partial => "sidebar" %>| app/helpers/aspace_form_helper.rb:628:in `jsonmodel_enum_for'| app/helpers/aspace_form_helper.rb:595:in `options_for'| app/helpers/aspace_form_helper.rb:392:in `possible_options_for'| app/views/interrelated_accessions/_template.html.erb:30:in `_app_views_interrelated_accessions__template_html_erb__1847228019_33474'| app/helpers/aspace_form_helper.rb:696:in `templates_for_js'| app/helpers/aspace_form_helper.rb:682:in `templates_for_js'| app/helpers/aspace_form_helper.rb:520:in `form_context'| app/views/accessions/edit.html.erb:4:in `_app_views_accessions_edit_html_erb__139972669_27306'| app/views/accessions/edit.html.erb:3:in `_app_views_accessions_edit_html_erb__139972669_27306'|||
Has anyone else run across this, or know what might be done to correct it?
Thanks,
Cory Nimer
Technical Services Archivist
Brigham Young University
801-422-6091
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141111/6c9824df/attachment.html>
More information about the Archivesspace_Users_Group
mailing list