mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2019-05-05
This commit is contained in:
@ -31,7 +31,7 @@ After running DSpace for over five years I’ve never needed to look in any
|
||||
This will save us a few gigs of backup space we’re paying for on S3
|
||||
Also, I noticed the checker log has some errors we should pay attention to:
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.55.3" />
|
||||
<meta name="generator" content="Hugo 0.55.5" />
|
||||
|
||||
|
||||
|
||||
@ -154,42 +154,40 @@ java.io.FileNotFoundException: /home/cgspace.cgiar.org/assetstore/64/29/06/64290
|
||||
<h2 id="2016-04-05">2016-04-05</h2>
|
||||
|
||||
<ul>
|
||||
<li>Reduce Amazon S3 storage used for logs from 46 GB to 6GB by deleting a bunch of logs we don’t need!</li>
|
||||
</ul>
|
||||
<li><p>Reduce Amazon S3 storage used for logs from 46 GB to 6GB by deleting a bunch of logs we don’t need!</p>
|
||||
|
||||
<pre><code># s3cmd ls s3://cgspace.cgiar.org/log/ > /tmp/s3-logs.txt
|
||||
# grep checker.log /tmp/s3-logs.txt | awk '{print $4}' | xargs s3cmd del
|
||||
# grep cocoon.log /tmp/s3-logs.txt | awk '{print $4}' | xargs s3cmd del
|
||||
# grep handle-plugin.log /tmp/s3-logs.txt | awk '{print $4}' | xargs s3cmd del
|
||||
# grep solr.log /tmp/s3-logs.txt | awk '{print $4}' | xargs s3cmd del
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>Also, adjust the cron jobs for backups so they only backup <code>dspace.log</code> and some stats files (.dat)</li>
|
||||
<li>Try to do some metadata field migrations using the Atmire batch UI (<code>dc.Species</code> → <code>cg.species</code>) but it took several hours and even missed a few records</li>
|
||||
<li><p>Also, adjust the cron jobs for backups so they only backup <code>dspace.log</code> and some stats files (.dat)</p></li>
|
||||
|
||||
<li><p>Try to do some metadata field migrations using the Atmire batch UI (<code>dc.Species</code> → <code>cg.species</code>) but it took several hours and even missed a few records</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-06">2016-04-06</h2>
|
||||
|
||||
<ul>
|
||||
<li>A better way to move metadata on this scale is via SQL, for example <code>dc.type.output</code> → <code>dc.type</code> (their IDs in the metadatafieldregistry are 66 and 109, respectively):</li>
|
||||
</ul>
|
||||
<li><p>A better way to move metadata on this scale is via SQL, for example <code>dc.type.output</code> → <code>dc.type</code> (their IDs in the metadatafieldregistry are 66 and 109, respectively):</p>
|
||||
|
||||
<pre><code>dspacetest=# update metadatavalue set metadata_field_id=109 where metadata_field_id=66;
|
||||
UPDATE 40852
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>After that an <code>index-discovery -bf</code> is required</li>
|
||||
<li>Start working on metadata migrations, add 25 or so new metadata fields to CGSpace</li>
|
||||
<li><p>After that an <code>index-discovery -bf</code> is required</p></li>
|
||||
|
||||
<li><p>Start working on metadata migrations, add 25 or so new metadata fields to CGSpace</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-07">2016-04-07</h2>
|
||||
|
||||
<ul>
|
||||
<li>Write shell script to do the migration of fields: <a href="https://gist.github.com/alanorth/72a70aca856d76f24c127a6e67b3342b">https://gist.github.com/alanorth/72a70aca856d76f24c127a6e67b3342b</a></li>
|
||||
<li>Testing with a few fields it seems to work well:</li>
|
||||
</ul>
|
||||
|
||||
<li><p>Testing with a few fields it seems to work well:</p>
|
||||
|
||||
<pre><code>$ ./migrate-fields.sh
|
||||
UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66
|
||||
@ -198,7 +196,8 @@ UPDATE metadatavalue SET metadata_field_id=202 WHERE metadata_field_id=72
|
||||
UPDATE 21420
|
||||
UPDATE metadatavalue SET metadata_field_id=203 WHERE metadata_field_id=76
|
||||
UPDATE 51258
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-08">2016-04-08</h2>
|
||||
|
||||
@ -211,23 +210,22 @@ UPDATE 51258
|
||||
|
||||
<ul>
|
||||
<li>Looking at the DOI issue <a href="https://www.yammer.com/dspacedevelopers/#/Threads/show?threadId=678507860">reported by Leroy from CIAT a few weeks ago</a></li>
|
||||
<li>It seems the <code>dx.doi.org</code> URLs are much more proper in our repository!</li>
|
||||
</ul>
|
||||
|
||||
<li><p>It seems the <code>dx.doi.org</code> URLs are much more proper in our repository!</p>
|
||||
|
||||
<pre><code>dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and text_value like 'http://dx.doi.org%';
|
||||
count
|
||||
count
|
||||
-------
|
||||
5638
|
||||
5638
|
||||
(1 row)
|
||||
|
||||
dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and text_value like 'http://doi.org%';
|
||||
count
|
||||
count
|
||||
-------
|
||||
3
|
||||
</code></pre>
|
||||
3
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I will manually edit the <code>dc.identifier.doi</code> in <a href="https://cgspace.cgiar.org/handle/10568/72509?show=full"><sup>10568</sup>⁄<sub>72509</sub></a> and tweet the link, then check back in a week to see if the donut gets updated</li>
|
||||
<li><p>I will manually edit the <code>dc.identifier.doi</code> in <a href="https://cgspace.cgiar.org/handle/10568/72509?show=full"><sup>10568</sup>⁄<sub>72509</sub></a> and tweet the link, then check back in a week to see if the donut gets updated</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-11">2016-04-11</h2>
|
||||
@ -240,38 +238,41 @@ dspacetest=# select count(*) from metadatavalue where metadata_field_id=74 and t
|
||||
<h2 id="2016-04-12">2016-04-12</h2>
|
||||
|
||||
<ul>
|
||||
<li>Looking at quality of WLE data (<code>cg.subject.iwmi</code>) in SQL:</li>
|
||||
</ul>
|
||||
<li><p>Looking at quality of WLE data (<code>cg.subject.iwmi</code>) in SQL:</p>
|
||||
|
||||
<pre><code>dspacetest=# select text_value, count(*) from metadatavalue where metadata_field_id=217 group by text_value order by count(*) desc;
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>Listings and Reports is still not returning reliable data for <code>dc.type</code></li>
|
||||
<li>I think we need to ask Atmire, as their documentation isn’t too clear on the format of the filter configs</li>
|
||||
<li>Alternatively, I want to see if I move all the data from <code>dc.type.output</code> to <code>dc.type</code> and then re-index, if it behaves better</li>
|
||||
<li>Looking at our <code>input-forms.xml</code> I see we have two sets of ILRI subjects, but one has a few extra subjects</li>
|
||||
<li>Remove one set of ILRI subjects and remove duplicate <code>VALUE CHAINS</code> from existing list (<a href="https://github.com/ilri/DSpace/pull/216">#216</a>)</li>
|
||||
<li>I decided to keep the set of subjects that had <code>FMD</code> and <code>RANGELANDS</code> added, as it appears to have been requested to have been added, and might be the newer list</li>
|
||||
<li>I found 226 blank metadatavalues:</li>
|
||||
</ul>
|
||||
<li><p>Listings and Reports is still not returning reliable data for <code>dc.type</code></p></li>
|
||||
|
||||
<li><p>I think we need to ask Atmire, as their documentation isn’t too clear on the format of the filter configs</p></li>
|
||||
|
||||
<li><p>Alternatively, I want to see if I move all the data from <code>dc.type.output</code> to <code>dc.type</code> and then re-index, if it behaves better</p></li>
|
||||
|
||||
<li><p>Looking at our <code>input-forms.xml</code> I see we have two sets of ILRI subjects, but one has a few extra subjects</p></li>
|
||||
|
||||
<li><p>Remove one set of ILRI subjects and remove duplicate <code>VALUE CHAINS</code> from existing list (<a href="https://github.com/ilri/DSpace/pull/216">#216</a>)</p></li>
|
||||
|
||||
<li><p>I decided to keep the set of subjects that had <code>FMD</code> and <code>RANGELANDS</code> added, as it appears to have been requested to have been added, and might be the newer list</p></li>
|
||||
|
||||
<li><p>I found 226 blank metadatavalues:</p>
|
||||
|
||||
<pre><code>dspacetest# select * from metadatavalue where resource_type_id=2 and text_value='';
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I think we should delete them and do a full re-index:</li>
|
||||
</ul>
|
||||
<li><p>I think we should delete them and do a full re-index:</p>
|
||||
|
||||
<pre><code>dspacetest=# delete from metadatavalue where resource_type_id=2 and text_value='';
|
||||
DELETE 226
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I deleted them on CGSpace but I’ll wait to do the re-index as we’re going to be doing one in a few days for the metadata changes anyways</li>
|
||||
<li>In other news, moving the <code>dc.type.output</code> to <code>dc.type</code> and re-indexing seems to have fixed the Listings and Reports issue from above</li>
|
||||
<li>Unfortunately this isn’t a very good solution, because Listings and Reports config should allow us to filter on <code>dc.type.*</code> but the documentation isn’t very clear and I couldn’t reach Atmire today</li>
|
||||
<li>We want to do the <code>dc.type.output</code> move on CGSpace anyways, but we should wait as it might affect other external people!</li>
|
||||
<li><p>I deleted them on CGSpace but I’ll wait to do the re-index as we’re going to be doing one in a few days for the metadata changes anyways</p></li>
|
||||
|
||||
<li><p>In other news, moving the <code>dc.type.output</code> to <code>dc.type</code> and re-indexing seems to have fixed the Listings and Reports issue from above</p></li>
|
||||
|
||||
<li><p>Unfortunately this isn’t a very good solution, because Listings and Reports config should allow us to filter on <code>dc.type.*</code> but the documentation isn’t very clear and I couldn’t reach Atmire today</p></li>
|
||||
|
||||
<li><p>We want to do the <code>dc.type.output</code> move on CGSpace anyways, but we should wait as it might affect other external people!</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-14">2016-04-14</h2>
|
||||
@ -315,8 +316,8 @@ DELETE 226
|
||||
<li>cg.livestock.agegroup: 9 items, in ILRI collections</li>
|
||||
<li>cg.livestock.function: 20 items, mostly in EADD</li>
|
||||
</ul></li>
|
||||
<li>Test metadata migration on local instance again:</li>
|
||||
</ul>
|
||||
|
||||
<li><p>Test metadata migration on local instance again:</p>
|
||||
|
||||
<pre><code>$ ./migrate-fields.sh
|
||||
UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66
|
||||
@ -332,95 +333,88 @@ UPDATE 3872
|
||||
UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108
|
||||
UPDATE 46075
|
||||
$ JAVA_OPTS="-Xms512m -Xmx512m -Dfile.encoding=UTF-8" ~/dspace/bin/dspace index-discovery -bf
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>CGSpace was down but I’m not sure why, this was in <code>catalina.out</code>:</li>
|
||||
</ul>
|
||||
<li><p>CGSpace was down but I’m not sure why, this was in <code>catalina.out</code>:</p>
|
||||
|
||||
<pre><code>Apr 18, 2016 7:32:26 PM com.sun.jersey.spi.container.ContainerResponse logException
|
||||
SEVERE: Mapped exception to response: 500 (Internal Server Error)
|
||||
javax.ws.rs.WebApplicationException
|
||||
at org.dspace.rest.Resource.processFinally(Resource.java:163)
|
||||
at org.dspace.rest.HandleResource.getObject(HandleResource.java:81)
|
||||
at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source)
|
||||
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
|
||||
at java.lang.reflect.Method.invoke(Method.java:606)
|
||||
at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
|
||||
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
|
||||
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
|
||||
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
|
||||
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
|
||||
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
|
||||
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
|
||||
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1511)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1442)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1391)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1381)
|
||||
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
|
||||
at org.dspace.rest.Resource.processFinally(Resource.java:163)
|
||||
at org.dspace.rest.HandleResource.getObject(HandleResource.java:81)
|
||||
at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source)
|
||||
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
|
||||
at java.lang.reflect.Method.invoke(Method.java:606)
|
||||
at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
|
||||
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
|
||||
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
|
||||
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
|
||||
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
|
||||
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
|
||||
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
|
||||
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1511)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1442)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1391)
|
||||
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1381)
|
||||
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
|
||||
...
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>Everything else in the system looked normal (50GB disk space available, nothing weird in dmesg, etc)</li>
|
||||
<li>After restarting Tomcat a few more of these errors were logged but the application was up</li>
|
||||
<li><p>Everything else in the system looked normal (50GB disk space available, nothing weird in dmesg, etc)</p></li>
|
||||
|
||||
<li><p>After restarting Tomcat a few more of these errors were logged but the application was up</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-19">2016-04-19</h2>
|
||||
|
||||
<ul>
|
||||
<li>Get handles for items that are using a given metadata field, ie <code>dc.Species.animal</code> (105):</li>
|
||||
</ul>
|
||||
<li><p>Get handles for items that are using a given metadata field, ie <code>dc.Species.animal</code> (105):</p>
|
||||
|
||||
<pre><code># select handle from item, handle where handle.resource_id = item.item_id AND item.item_id in (select resource_id from metadatavalue where resource_type_id=2 and metadata_field_id=105);
|
||||
handle
|
||||
handle
|
||||
-------------
|
||||
10568/10298
|
||||
10568/16413
|
||||
10568/16774
|
||||
10568/34487
|
||||
</code></pre>
|
||||
10568/10298
|
||||
10568/16413
|
||||
10568/16774
|
||||
10568/34487
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>Delete metadata values for <code>dc.GRP</code> and <code>dc.icsubject.icrafsubject</code>:</li>
|
||||
</ul>
|
||||
<li><p>Delete metadata values for <code>dc.GRP</code> and <code>dc.icsubject.icrafsubject</code>:</p>
|
||||
|
||||
<pre><code># delete from metadatavalue where resource_type_id=2 and metadata_field_id=96;
|
||||
# delete from metadatavalue where resource_type_id=2 and metadata_field_id=83;
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>They are old ICRAF fields and we haven’t used them since 2011 or so</li>
|
||||
<li>Also delete them from the metadata registry</li>
|
||||
<li>CGSpace went down again, <code>dspace.log</code> had this:</li>
|
||||
</ul>
|
||||
<li><p>They are old ICRAF fields and we haven’t used them since 2011 or so</p></li>
|
||||
|
||||
<li><p>Also delete them from the metadata registry</p></li>
|
||||
|
||||
<li><p>CGSpace went down again, <code>dspace.log</code> had this:</p>
|
||||
|
||||
<pre><code>2016-04-19 15:02:17,025 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
|
||||
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I restarted Tomcat and PostgreSQL and now it’s back up</li>
|
||||
<li>I bet this is the same crash as yesterday, but I only saw the errors in <code>catalina.out</code></li>
|
||||
<li>Looks to be related to this, from <code>dspace.log</code>:</li>
|
||||
</ul>
|
||||
<li><p>I restarted Tomcat and PostgreSQL and now it’s back up</p></li>
|
||||
|
||||
<li><p>I bet this is the same crash as yesterday, but I only saw the errors in <code>catalina.out</code></p></li>
|
||||
|
||||
<li><p>Looks to be related to this, from <code>dspace.log</code>:</p>
|
||||
|
||||
<pre><code>2016-04-19 15:16:34,670 ERROR org.dspace.rest.Resource @ Something get wrong. Aborting context in finally statement.
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>We have 18,000 of these errors right now…</li>
|
||||
<li>Delete a few more old metadata values: <code>dc.Species.animal</code>, <code>dc.type.journal</code>, and <code>dc.publicationcategory</code>:</li>
|
||||
</ul>
|
||||
<li><p>We have 18,000 of these errors right now…</p></li>
|
||||
|
||||
<li><p>Delete a few more old metadata values: <code>dc.Species.animal</code>, <code>dc.type.journal</code>, and <code>dc.publicationcategory</code>:</p>
|
||||
|
||||
<pre><code># delete from metadatavalue where resource_type_id=2 and metadata_field_id=105;
|
||||
# delete from metadatavalue where resource_type_id=2 and metadata_field_id=85;
|
||||
# delete from metadatavalue where resource_type_id=2 and metadata_field_id=95;
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>And then remove them from the metadata registry</li>
|
||||
<li><p>And then remove them from the metadata registry</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-20">2016-04-20</h2>
|
||||
@ -428,8 +422,8 @@ org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error
|
||||
<ul>
|
||||
<li>Re-deploy DSpace Test with the new subject and type fields, run all system updates, and reboot the server</li>
|
||||
<li>Migrate fields and re-deploy CGSpace with the new subject and type fields, run all system updates, and reboot the server</li>
|
||||
<li>Field migration went well:</li>
|
||||
</ul>
|
||||
|
||||
<li><p>Field migration went well:</p>
|
||||
|
||||
<pre><code>$ ./migrate-fields.sh
|
||||
UPDATE metadatavalue SET metadata_field_id=109 WHERE metadata_field_id=66
|
||||
@ -444,22 +438,23 @@ UPDATE metadatavalue SET metadata_field_id=215 WHERE metadata_field_id=106
|
||||
UPDATE 3872
|
||||
UPDATE metadatavalue SET metadata_field_id=217 WHERE metadata_field_id=108
|
||||
UPDATE 46075
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>Also, I migrated CGSpace to using the PGDG PostgreSQL repo as the infrastructure playbooks had been using it for a while and it seemed to be working well</li>
|
||||
<li>Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)</li>
|
||||
<li>Looking into the REST API errors again, it looks like these started appearing a few days ago in the tens of thousands:</li>
|
||||
</ul>
|
||||
<li><p>Also, I migrated CGSpace to using the PGDG PostgreSQL repo as the infrastructure playbooks had been using it for a while and it seemed to be working well</p></li>
|
||||
|
||||
<li><p>Basically, this gives us the ability to use the latest upstream stable 9.3.x release (currently 9.3.12)</p></li>
|
||||
|
||||
<li><p>Looking into the REST API errors again, it looks like these started appearing a few days ago in the tens of thousands:</p>
|
||||
|
||||
<pre><code>$ grep -c "Aborting context in finally statement" dspace.log.2016-04-20
|
||||
21252
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I found a recent discussion on the DSpace mailing list and I’ve asked for advice there</li>
|
||||
<li>Looks like this issue was noted and fixed in DSpace 5.5 (we’re on 5.1): <a href="https://jira.duraspace.org/browse/DS-2936">https://jira.duraspace.org/browse/DS-2936</a></li>
|
||||
<li>I’ve sent a message to Atmire asking about compatibility with DSpace 5.5</li>
|
||||
<li><p>I found a recent discussion on the DSpace mailing list and I’ve asked for advice there</p></li>
|
||||
|
||||
<li><p>Looks like this issue was noted and fixed in DSpace 5.5 (we’re on 5.1): <a href="https://jira.duraspace.org/browse/DS-2936">https://jira.duraspace.org/browse/DS-2936</a></p></li>
|
||||
|
||||
<li><p>I’ve sent a message to Atmire asking about compatibility with DSpace 5.5</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-21">2016-04-21</h2>
|
||||
@ -496,8 +491,8 @@ UPDATE 46075
|
||||
<ul>
|
||||
<li>I woke up to ten or fifteen “up” and “down” emails from the monitoring website</li>
|
||||
<li>Looks like the last one was “down” from about four hours ago</li>
|
||||
<li>I think there must be something with this REST stuff:</li>
|
||||
</ul>
|
||||
|
||||
<li><p>I think there must be something with this REST stuff:</p>
|
||||
|
||||
<pre><code># grep -c "Aborting context in finally statement" dspace.log.2016-04-*
|
||||
dspace.log.2016-04-01:0
|
||||
@ -527,15 +522,19 @@ dspace.log.2016-04-24:28775
|
||||
dspace.log.2016-04-25:28626
|
||||
dspace.log.2016-04-26:28655
|
||||
dspace.log.2016-04-27:7271
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I restarted tomcat and it is back up</li>
|
||||
<li>Add Spanish XMLUI strings so those users see “CGSpace” instead of “DSpace” in the user interface (<a href="https://github.com/ilri/DSpace/pull/222">#222</a>)</li>
|
||||
<li>Submit patch to upstream DSpace for the misleading help text in the embargo step of the item submission: <a href="https://jira.duraspace.org/browse/DS-3172">https://jira.duraspace.org/browse/DS-3172</a></li>
|
||||
<li>Update infrastructure playbooks for nginx 1.10.x (stable) release: <a href="https://github.com/ilri/rmg-ansible-public/issues/32">https://github.com/ilri/rmg-ansible-public/issues/32</a></li>
|
||||
<li>Currently running on DSpace Test, we’ll give it a few days before we adjust CGSpace</li>
|
||||
<li>CGSpace down, restarted tomcat and it’s back up</li>
|
||||
<li><p>I restarted tomcat and it is back up</p></li>
|
||||
|
||||
<li><p>Add Spanish XMLUI strings so those users see “CGSpace” instead of “DSpace” in the user interface (<a href="https://github.com/ilri/DSpace/pull/222">#222</a>)</p></li>
|
||||
|
||||
<li><p>Submit patch to upstream DSpace for the misleading help text in the embargo step of the item submission: <a href="https://jira.duraspace.org/browse/DS-3172">https://jira.duraspace.org/browse/DS-3172</a></p></li>
|
||||
|
||||
<li><p>Update infrastructure playbooks for nginx 1.10.x (stable) release: <a href="https://github.com/ilri/rmg-ansible-public/issues/32">https://github.com/ilri/rmg-ansible-public/issues/32</a></p></li>
|
||||
|
||||
<li><p>Currently running on DSpace Test, we’ll give it a few days before we adjust CGSpace</p></li>
|
||||
|
||||
<li><p>CGSpace down, restarted tomcat and it’s back up</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-04-28">2016-04-28</h2>
|
||||
@ -548,17 +547,15 @@ dspace.log.2016-04-27:7271
|
||||
<h2 id="2016-04-30">2016-04-30</h2>
|
||||
|
||||
<ul>
|
||||
<li>Logs for today and yesterday have zero references to this REST error, so I’m going to open back up the REST API but log all requests</li>
|
||||
</ul>
|
||||
<li><p>Logs for today and yesterday have zero references to this REST error, so I’m going to open back up the REST API but log all requests</p>
|
||||
|
||||
<pre><code>location /rest {
|
||||
access_log /var/log/nginx/rest.log;
|
||||
proxy_pass http://127.0.0.1:8443;
|
||||
}
|
||||
</code></pre>
|
||||
</code></pre></li>
|
||||
|
||||
<ul>
|
||||
<li>I will check the logs again in a few days to look for patterns, see who is accessing it, etc</li>
|
||||
<li><p>I will check the logs again in a few days to look for patterns, see who is accessing it, etc</p></li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user