Greenstone Wiki

User Tools

Site Tools

You are here: index » en » release » 3.09_release_notes
en:release:3.09_release_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
en:release:3.09_release_notes [2019/07/10 03:42] – anupamaen:release:3.09_release_notes [2019/09/05 07:10] – [SIGPIPE errors when building a collection] anupama
Line 319: Line 319:
 For ease of access this section has been brought across from the [[en:release:3.08_release_notes|3.08 Release Notes]], but not all of it may be relevant to the 3.09 release. For ease of access this section has been brought across from the [[en:release:3.08_release_notes|3.08 Release Notes]], but not all of it may be relevant to the 3.09 release.
  
-==== Troubleshooting ==== +==== Patches to 3.09 ====
- +
-=== Patches to 3.09 ===+
 These are corrections to a 3.09 installation that should be easy for Greenstone users to make. These are corrections to a 3.09 installation that should be easy for Greenstone users to make.
  
Line 332: Line 330:
 Download the file [[http://trac.greenstone.org/browser/gs3-extensions/solr/trunk/src/perllib/solrserver.pm?rev=33315&format=txt|solrserver.pm revision version 33315]] and put it into your GS3.09's ext/solr/perllib folder, replacing the existing file by that name. Download the file [[http://trac.greenstone.org/browser/gs3-extensions/solr/trunk/src/perllib/solrserver.pm?rev=33315&format=txt|solrserver.pm revision version 33315]] and put it into your GS3.09's ext/solr/perllib folder, replacing the existing file by that name.
  
 +
 +==== Troubleshooting ====
  
 === Content Encoding Error when visiting the local solr servlet page ===  === Content Encoding Error when visiting the local solr servlet page === 
Line 343: Line 343:
 We've added a work around to one kind of SIGPIPE errors which could occur with large collections when using ''solr'' as indexer. However, a couple of people on the mailing list encountered SIGPIPE errors on occasions when solr was not the indexer. **If your collection is using ''jdbm'' as the database type** and the error messages surrounding the SIGPIPE mention issues with "transaction commit", then Mariana Pichinini on the mailing list found that the following helped: We've added a work around to one kind of SIGPIPE errors which could occur with large collections when using ''solr'' as indexer. However, a couple of people on the mailing list encountered SIGPIPE errors on occasions when solr was not the indexer. **If your collection is using ''jdbm'' as the database type** and the error messages surrounding the SIGPIPE mention issues with "transaction commit", then Mariana Pichinini on the mailing list found that the following helped:
   * change the database type from ''jdbm'' to ''gdbm''   * change the database type from ''jdbm'' to ''gdbm''
-  * or leave the database type at ''jdbm'' and move your GS3's bundled JRE (the GS3's ''packages/jre'' subfolder) outside your GS3 installation. Next install a newer Java on your system so that GS3.08 can find that. If on Linux, ensure you open a new terminal before running GLI or command line building your collection.+  * or leave the database type at ''jdbm'' and move your GS3's bundled JRE (the GS3's ''packages/jre'' subfolder) outside your GS3 installation. Next install a newer Java on your system so that GS3.09 can find that. If on Linux, ensure you open a new terminal before running GLI or command line building your collection.
 === Your browser doesn't remember you being logged into greenstone === === Your browser doesn't remember you being logged into greenstone ===
 **The issue:** **The issue:**
en/release/3.09_release_notes.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1