Merge pull request #1834 from mtmail/faq-invalid-page-in-block

FAQ entry for PostgreSQL -invalid page in block-

diff --git a/docs/admin/Faq.md b/docs/admin/Faq.md
index 126d79772459c1beb6209c9637c4a9fde7003305..2bf0e6bee793fda6703bf1b45fd6c22fd8879b17 100644 (file)
--- a/docs/admin/Faq.md
+++ b/docs/admin/Faq.md
@@ -22,6 +22,21 @@ then you can resume with the following command:
 If the reported rank is 26 or higher, you can also safely add `--index-noanalyse`.
 
 
+### PostgreSQL crashed "invalid page in block"
+
+Usually serious problem, can be a hardware issue, not all data written to disc
+for example. Check PostgreSQL log file and search PostgreSQL issues/mailing
+list for hints.
+
+If it happened during index creation you can try rerunning the step with
+
+```sh
+./utils/setup.php --create-search-indices --ignore-errors
+```
+
+Otherwise it's best to start the full setup from the beginning.
+
+
 ### PHP "open_basedir restriction in effect" warnings
 
     PHP Warning:  file_get_contents(): open_basedir restriction in effect.

diff --git a/utils/check_import_finished.php b/utils/check_import_finished.php
index 4529c69394b53c8cab1e50775c549fe516d942c5..42d834c870b2439cf3aff4a9b8c571fcff9fa535 100755 (executable)
--- a/utils/check_import_finished.php
+++ b/utils/check_import_finished.php
@@ -133,7 +133,8 @@ foreach ($aExpectedIndices as $sExpectedIndex) {
         $print_fail();
         echo <<< END
         Hints:
-        * Rerun the setup.php --create-search-indices step
+        * Run './utils/setup.php --create-search-indices --ignore-errors' to
+          create missing indices.
 
 END;
         exit(1);