19215: Add -o pipefail to installer.sh

[arvados.git] / doc / admin / maintenance-and-upgrading.html.textile.liquid

diff --git a/doc/admin/maintenance-and-upgrading.html.textile.liquid b/doc/admin/maintenance-and-upgrading.html.textile.liquid
index 7d0ca84d25fca5a37d3a27b6e6fc10a22d1d1fa0..480f5114ea135625754e03410a2a20501521f48f 100644 (file)
--- a/doc/admin/maintenance-and-upgrading.html.textile.liquid
+++ b/doc/admin/maintenance-and-upgrading.html.textile.liquid
@@ -20,7 +20,7 @@ h2(#commercial_support). Commercial support
 
 Arvados is "100% open source software":{{site.baseurl}}/user/copying/copying.html. Anyone can download, install, maintain and upgrade it. However, if this is not something you want to spend your time and energy doing, "Curii Corporation":https://curii.com provides managed Arvados installations as well as commercial support for Arvados. Please contact "info@curii.com":mailto:info@curii.com for more information.
 
-If you'd prefer to do things yourself, a few starting points for a maintaining and upgrading Arvados can be found below.
+If you'd prefer to do things yourself, a few starting points for maintaining and upgrading Arvados can be found below.
 
 h2(#maintaining). Maintaining Arvados
 
@@ -42,14 +42,16 @@ Run @arvados-server config-check@ to make sure the configuration file has no err
 
 h3(#distribution). Distribute the configuration file
 
-We recommend to keep the @config.yml@ file in sync between all the Arvados system nodes, to avoid issues with services running on different versions of the configuration.
+It is very important to keep the @config.yml@ file in sync between all the Arvados system nodes, to avoid issues with services running on different versions of the configuration.
 
-Distribution of the configuration file can be done in many ways, e.g. scp, configuration management software, etc.
+We provide "installer.sh":../install/salt-multi-host-install.html#installation to distribute config changes.  You may also do your own orchestration e.g. @scp@, configuration management software, etc.
 
 h3(#restart). Restart the services affected by the change
 
 If you know which Arvados service uses the specific configuration that was modified, restart those services. When in doubt, restart all Arvados system services.
 
+To check for services that have not restarted since the configuration file was updated, run the @arvados-server check@ command on each system node.
+
 h2(#upgrading). Upgrading Arvados
 
 Upgrading Arvados typically involves the following steps:
@@ -61,4 +63,6 @@ Upgrading Arvados typically involves the following steps:
 # rebuild and deploy the "compute node image":{{site.baseurl}}/install/crunch2-cloud/install-compute-node.html (cloud only)
 # Install new packages using @apt-get upgrade@ or @yum upgrade@.
 # Wait for package installation scripts as they perform any necessary data migrations.
+# Run @arvados-server config-check@ to detect configuration errors or deprecated entries.
 # Verify that the Arvados services were restarted as part of the package upgrades.
+# Run @arvados-server check@ to detect services that did not restart properly.