Differences

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

--- en:release:3.08_release_notes [2018/12/13 05:40] – [SIGPIPE errors when building a collection] anupama
+++ en:release:3.08_release_notes [2018/12/14 04:03] – [SIGPIPE errors when building a collection] anupama
@@ Line 242: / Line 242: @@
 ==== Troubleshooting ====
 === SIGPIPE errors when building a collection ===
-  - **If your indexer is set to ''solr''**, a newer version of the solr extension has been fixed to circumvent this error (it's a problem in one of Java's HttpURLConnection related classes). You can try one of the following:
+  - **If your indexer is set to ''solr''**, a newer version of the solr extension has been fixed to circumvent a SIGPIPE error caused by a problem in one of Java's HttpURLConnection related classes. You can try one of the following:
     * You could grab a newer version of Greenstone 3. Greenstone 3.09 (still to be released at the time of writing) will contain this fix, as do nightly binaries from http://www.greenstone.org/caveat-emptor/?latest=latest
     * Get a newer version of the solr extension from SVN that contains the fix from http://trac.greenstone.org/browser/gs3-extensions/solr/trunk/src?rev=32088. SVN checkout this folder into the GS3 ''ext'' subfolder as ''solr'', after removing the old ''ext/solr'' folder. Then use a terminal to go into the ''ext/solr'' folder and run ''ant del-service add-service''.
     * Or you can update just the affected files in your solr extension, by following the instructions in the sequence of Greenstone mailing list exchanges with Martín Williman under the subject "SolR bugs".
-  - If your indexer is not solr or if updating the solr extension didn't fix the problem **and if your collection is using ''jdbm'' as the database type**, then either
+  - **If your indexer is not solr or if updating the solr extension didn't fix the problem and if your collection is using ''jdbm'' as the database type** and the error messages surrounding the SIGPIPE mention issues with "transaction commit", then either
      * change the database type to ''gdbm''
      * or leave the database type at jdbm and move your GS3's bundled JRE (the GS3.08'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.