X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/a9ffac64364fafe598c1e6af0468b9139cdd8083..22f9af1104fa45e95ef3cd8b5a770fc0b9ed0fd3:/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 7d0ca84d25..3cc80a3560 100644 --- 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 @@ -50,6 +50,8 @@ 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.