<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Those MySQL errors look like the ones already reported and are probably not causing any problems. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9">https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9</a><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Turn the mysql error logging thing off and set the other loglevel errors to debug and look for any FATAL or ERROR in the logs.</div>
<div>
<div id="Signature">
<div>
<div id="divtagdefaultwrapper" dir="ltr" style="color:rgb(0,0,0); background-color:rgb(255,255,255)">
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Mark Cyzyk
<mcyzyk@jhu.edu><br>
<b>Sent:</b> Wednesday, March 3, 2021 10:20 AM<br>
<b>To:</b> Rachel Aileen Searcy <rachel.searcy@nyu.edu>; Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Containers not being associated with their resources</font>
<div> </div>
</div>
<div><br>
More:<br>
<br>
In our development environment, I configured full error logging. I then ran one of our queries that is failing, stopped ASpace, then began scrutiny of archivesspace.out.<br>
<br>
Here are my disturbing findings:<br>
<br>
<blockquote>
<blockquote>E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: DESCRIBE `agent_relationship_associative`<br>
E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1<br>
E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1<br>
E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: DESCRIBE `agent_relationship_earlierlater`<br>
E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1<br>
E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: SELECT * FROM `agent_relationship_earlierlater` LIMIT 1<br>
E, [2021-03-03T09:47:30.000084 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: DESCRIBE `agent_relationship_parentchild`<br>
E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1<br>
E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT * FROM `agent_relationship_parentchild` LIMIT 1<br>
E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: DESCRIBE `agent_relationship_subordinatesuperior`<br>
E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT
1<br>
E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT
1<br>
<br>
<br>
<br>
E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: DESCRIBE `container_location`<br>
E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1<br>
E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM `container_location` LIMIT 1<br>
<br>
<br>
<br>
E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: DESCRIBE `note_bibliography`<br>
E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1<br>
E, [2021-03-03T09:47:30.606147 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM `note_bibliography` LIMIT 1<br>
E, [2021-03-03T09:47:30.635130 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: DESCRIBE `note_digital_object`<br>
E, [2021-03-03T09:47:30.638129 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1<br>
E, [2021-03-03T09:47:30.645140 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_digital_object' doesn't exist: SELECT * FROM `note_digital_object` LIMIT 1<br>
E, [2021-03-03T09:47:30.651197 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'archivesspaceDevelopment.note_index' doesn't exist: DESCRIBE `note_index`E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException:
Table 'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT * FROM `agent_relationship_associative` LIMIT 1<br>
</blockquote>
</blockquote>
<br>
<br>
I took a look directly in the database and these tables are indeed missing.<br>
<br>
At this point, I am stumped. I don't understand why, with these tables missing, one of our three Repositories would be working just fine -- the other two, not so much. How could whole tables get deleted from our ASpace? I'm guessing this happened a couple
weeks ago.<br>
<br>
Any advice greatly appreciated,<br>
<br>
Mark<br>
<pre class="x_moz-signature" cols="72"><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
<a class="x_moz-txt-link-abbreviated" href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a>
Verba volant, scripta manent.
</pre>
<div class="x_moz-cite-prefix">On 3/1/21 5:18 PM, Mark Cyzyk wrote:<br>
</div>
<blockquote type="cite"><br>
Thanks, Rachel!<br>
<br>
I've now completely reindexed everything (a "hard reindex") and still no joy. <br>
<br>
I am noticing there is no "location.dat" file in our /indexer_pui_state/:<br>
<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 3_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 4_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_archival_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_classification_term.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object_component.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_digital_object.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 5_resource.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 _deletes_deletes.dat<br>
-rw-r--r--. 1 archivesspace archivesspace 11 Mar 1 17:13 repositories_repositories.dat<br>
<br>
Should there be?<br>
<br>
Our two problem repositories here are 4 and 5. The Staff interface reports "0" Resources for both. Yet when I run the Resources List Report I do indeed get back a report with Resources. Puzzling.<br>
<br>
It's like something in the backend DB has become disconnected, but just for these two repositories. Not sure how.<br>
<br>
If anyone has any suggestions, I would greatly appreciate hearing them!<br>
<br>
Mark<br>
<br>
<pre class="x_moz-signature" cols="72"><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
<a class="x_moz-txt-link-abbreviated" href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a>
Verba volant, scripta manent.
</pre>
<div class="x_moz-cite-prefix">On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi Mark</div>
<div><br>
</div>
We ran into a similar issue recently, where newly created containers were not being properly associated with the resource record, and updates to locations or barcodes were not showing up in searches or the Manage Top Containers view. We looked at the timestamp
files for the indexer, and noticed that there was no location.dat file. We performed a
<a href="https://github.com/archivesspace/tech-docs/blob/master/administration/indexes.md">
soft re-index</a>, after which our containers, barcodes, and locations resumed behaving as expected. We also have recurring monthly system restarts (which will now include a soft re-index going forward) built into our schedule, which seems to help with maintaining
overall performance.<br>
<div><br>
</div>
<div>I'm not sure if this is exactly what you're experiencing, but I hope it's helpful. Take care,</div>
<div>Rachel</div>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk <<a href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px
0.8ex; border-left:1px solid
rgb(204,204,204); padding-left:1ex">
<br>
Dear ASpace list,<br>
<br>
From one of our Archivists:<br>
<br>
> When I create a new container, either manually or by spreadsheet <br>
> ingest, the container appears properly in the Instance field of the <br>
> record. From the resource, I can open the container record and it <br>
> appears to be associated with the resource correctly. However, in the <br>
> container management module, when I search for all containers <br>
> associated with the collection, the recently created container is not <br>
> listed. If I search for the new container's barcode, the container <br>
> appears in the search results but with no associated resource. I can <br>
> also locate the new containers by searching for unassociated containers.<br>
<br>
It seems like some linkage is not happening here.<br>
<br>
More, this is only happening in his Repository, not our other, larger <br>
Repository.<br>
<br>
Has anyone else run into this?<br>
<br>
Mark<br>
<br>
-- <br>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><br>
Mark Cyzyk, M.A., M.L.S.<br>
Library Applications Group<br>
The Sheridan Libraries<br>
The Johns Hopkins University<br>
<a href="mailto:mcyzyk@jhu.edu" target="_blank">mcyzyk@jhu.edu</a><br>
<br>
Verba volant, scripta manent.<br>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=SmteiGvtNVMomV11nXFZu2vgQ88h7aapUFt6H55qk9o&s=mbxfqYRQtAZn2xsehm9iyXz5ZA-q1Evo07_25hxNzk0&e=</a>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="x_gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Rachel Searcy<br>
Accessioning Archivist, Archival Collections Management<br>
<div><span style="font-size:12.8px">New York University Libraries</span><br>
</div>
<div><a value="+12129982631">212.998.2539</a> | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">
rachel.searcy@nyu.edu</a> <br>
</div>
</div>
<div>My pronouns are she/her/hers</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</blockquote>
<br>
</div>
</body>
</html>