commit 3e64e64098320fe121f503169432ada033d83fe3
parent 2afc27c9caee1712f120a76a88c41b19e76eb859
Author: Florian Dold <dold@taler.net>
Date: Tue, 8 Sep 2026 21:44:08 +0200
manpages: document service startup checks for finalization
Explain that service connections reject unfinished finalization for their
component, while administrative connections remain available for repair.
Clarify that startup checks do not replace stopping services for upgrades.
Diffstat:
3 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/manpages/taler-auditor-dbinit.1.rst b/manpages/taler-auditor-dbinit.1.rst
@@ -44,6 +44,11 @@ its writes. Pending finalization is recorded in ``_v.pending_finalizations``
before applying migrations and cleared only when finalization commits. Failed
finalization remains visible to ``--dry``, even without procedure files.
+Normal service connections reject pending finalization for their own component
+and failures to inspect that status. Administrative connections remain available
+so dbinit can finish the migration. These are startup checks; stop the services
+before running migrations.
+
Its options are as follows:
**--dry**
diff --git a/manpages/taler-exchange-dbinit.1.rst b/manpages/taler-exchange-dbinit.1.rst
@@ -47,6 +47,11 @@ its writes. Pending finalization is recorded in ``_v.pending_finalizations``
before applying migrations and cleared only when finalization commits. Failed
finalization remains visible to ``--dry``, even without procedure files.
+Normal service connections reject pending finalization for their own component
+and failures to inspect that status. Administrative connections remain available
+so dbinit can finish the migration. These are startup checks; stop the services
+before running migrations.
+
Its options are as follows:
**--dry**
diff --git a/manpages/taler-merchant-dbinit.1.rst b/manpages/taler-merchant-dbinit.1.rst
@@ -45,6 +45,11 @@ its writes. Pending finalization is recorded in ``_v.pending_finalizations``
before applying migrations and cleared only when finalization commits. Failed
finalization remains visible to ``--dry``, even without procedure files.
+Normal service connections reject pending finalization for their own component
+and failures to inspect that status. Administrative connections remain available
+so dbinit can finish the migration. These are startup checks; stop the services
+before running migrations.
+
Its options are as follows:
**--dry**
