alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2016-12-04

Browse Source
This commit is contained in:
Alan Orth
2016-12-04 12:30:24 +02:00
parent e9faae906b
commit 7a4563de0d
5 changed files with 158 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
public/2016-12/index.html
View File

@ -30,7 +30,7 @@
<meta itemprop="dateModified" content="2016-12-02T10:43:00&#43;03:00" />
<meta itemprop="wordCount" content="573">
<meta itemprop="wordCount" content="722">
@ -245,6 +245,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
<li>Normally these stay uncompressed for a month just in case we need to look at them, so now I&rsquo;ve just compressed anything older than 2 weeks so we can get some disk space back</li>
</ul>
<h2 id="2016-12-04">2016-12-04</h2>
<ul>
<li>I got a weird report from the CGSpace checksum checker this morning</li>
<li>It says 732 bitstreams have potential issues, for example:</li>
</ul>
<pre><code>------------------------------------------------
Bitstream Id = 6
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
Result = Bitstream marked deleted in bitstream table
-----------------------------------------------
...
------------------------------------------------
Bitstream Id = 77581
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = 9959301aa4ca808d00957dff88214e38
Checksum Calculated =
Result = The bitstream could not be found
-----------------------------------------------
</code></pre>
<ul>
<li>The first one seems ok, but I don&rsquo;t know what to make of the second one&hellip;</li>
<li>I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in <code>[dspace-dir]/assetstore/99/59/30/...</code>)</li>
<li>For what it&rsquo;s worth, there is no item on DSpace Test or S3 backups with that checksum either&hellip;</li>
</ul>

32
public/index.xml
View File

@ -148,6 +148,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
&lt;li&gt;Also, the disk is nearly full because of log file issues, so I&amp;rsquo;m running some compression on DSpace logs&lt;/li&gt;
&lt;li&gt;Normally these stay uncompressed for a month just in case we need to look at them, so now I&amp;rsquo;ve just compressed anything older than 2 weeks so we can get some disk space back&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-12-04&#34;&gt;2016-12-04&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I got a weird report from the CGSpace checksum checker this morning&lt;/li&gt;
&lt;li&gt;It says 732 bitstreams have potential issues, for example:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;------------------------------------------------
Bitstream Id = 6
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
Result = Bitstream marked deleted in bitstream table
-----------------------------------------------
...
------------------------------------------------
Bitstream Id = 77581
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = 9959301aa4ca808d00957dff88214e38
Checksum Calculated =
Result = The bitstream could not be found
-----------------------------------------------
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;The first one seems ok, but I don&amp;rsquo;t know what to make of the second one&amp;hellip;&lt;/li&gt;
&lt;li&gt;I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in &lt;code&gt;[dspace-dir]/assetstore/99/59/30/...&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;For what it&amp;rsquo;s worth, there is no item on DSpace Test or S3 backups with that checksum either&amp;hellip;&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

32
public/post/index.xml
View File

@ -148,6 +148,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
&lt;li&gt;Also, the disk is nearly full because of log file issues, so I&amp;rsquo;m running some compression on DSpace logs&lt;/li&gt;
&lt;li&gt;Normally these stay uncompressed for a month just in case we need to look at them, so now I&amp;rsquo;ve just compressed anything older than 2 weeks so we can get some disk space back&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-12-04&#34;&gt;2016-12-04&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I got a weird report from the CGSpace checksum checker this morning&lt;/li&gt;
&lt;li&gt;It says 732 bitstreams have potential issues, for example:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;------------------------------------------------
Bitstream Id = 6
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
Result = Bitstream marked deleted in bitstream table
-----------------------------------------------
...
------------------------------------------------
Bitstream Id = 77581
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = 9959301aa4ca808d00957dff88214e38
Checksum Calculated =
Result = The bitstream could not be found
-----------------------------------------------
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;The first one seems ok, but I don&amp;rsquo;t know what to make of the second one&amp;hellip;&lt;/li&gt;
&lt;li&gt;I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in &lt;code&gt;[dspace-dir]/assetstore/99/59/30/...&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;For what it&amp;rsquo;s worth, there is no item on DSpace Test or S3 backups with that checksum either&amp;hellip;&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>

32
public/tags/notes/index.xml
View File

@ -147,6 +147,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
&lt;li&gt;Also, the disk is nearly full because of log file issues, so I&amp;rsquo;m running some compression on DSpace logs&lt;/li&gt;
&lt;li&gt;Normally these stay uncompressed for a month just in case we need to look at them, so now I&amp;rsquo;ve just compressed anything older than 2 weeks so we can get some disk space back&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;2016-12-04&#34;&gt;2016-12-04&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;I got a weird report from the CGSpace checksum checker this morning&lt;/li&gt;
&lt;li&gt;It says 732 bitstreams have potential issues, for example:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;------------------------------------------------
Bitstream Id = 6
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
Result = Bitstream marked deleted in bitstream table
-----------------------------------------------
...
------------------------------------------------
Bitstream Id = 77581
Process Start Date = Dec 4, 2016
Process End Date = Dec 4, 2016
Checksum Expected = 9959301aa4ca808d00957dff88214e38
Checksum Calculated =
Result = The bitstream could not be found
-----------------------------------------------
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;The first one seems ok, but I don&amp;rsquo;t know what to make of the second one&amp;hellip;&lt;/li&gt;
&lt;li&gt;I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in &lt;code&gt;[dspace-dir]/assetstore/99/59/30/...&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;For what it&amp;rsquo;s worth, there is no item on DSpace Test or S3 backups with that checksum either&amp;hellip;&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>