From e2ac5f3315647dade54d3a5333d5d30b6da93ce9 Mon Sep 17 00:00:00 2001 From: Michele Sollecito Date: Fri, 15 Jun 2018 13:44:35 +0100 Subject: [PATCH] [ENT-1876]: Make clear in documentation that you need to run db migration before starting node. (#1007) --- docs/source/deploying-a-node.rst | 16 +++++++++++----- docs/source/running-a-node.rst | 5 +++++ 2 files changed, 16 insertions(+), 5 deletions(-) diff --git a/docs/source/deploying-a-node.rst b/docs/source/deploying-a-node.rst index ed3e6d7816..f28488c6e3 100644 --- a/docs/source/deploying-a-node.rst +++ b/docs/source/deploying-a-node.rst @@ -163,14 +163,17 @@ handling, and ensures the Corda service is run at boot. 11. Provision the required certificates to your node. Contact the network permissioning service or see :doc:`permissioning` -12. **SystemD**: You can now start a node and its webserver and set the services to start on boot by running the +12. Depending on the versions of Corda and of the CorDapps used, database migration scripts might need to run before a node is able to start. + For more information refer to :doc:`database-management` + +13. **SystemD**: You can now start a node and its webserver and set the services to start on boot by running the following ``systemctl`` commands: * ``sudo systemctl daemon-reload`` * ``sudo systemctl enable --now corda`` * ``sudo systemctl enable --now corda-webserver`` -12. **Upstart**: You can now start a node and its webserver by running the following commands: +13. **Upstart**: You can now start a node and its webserver by running the following commands: * ``sudo start corda`` * ``sudo start corda-webserver`` @@ -264,11 +267,14 @@ at boot, and means the Corda service stays running with no users connected to th 10. Provision the required certificates to your node. Contact the network permissioning service or see :doc:`permissioning` -11. Run the batch file by clicking on it or from a command prompt +11. Depending on the versions of Corda and of the CorDapps used, database migration scripts might need to run before a node is able to start. + For more information refer to :doc:`database-management` -12. Run ``services.msc`` and verify that a service called ``cordanode1`` is present and running +12. Run the batch file by clicking on it or from a command prompt -13. Run ``netstat -ano`` and check for the ports you configured in ``node.conf`` +13. Run ``services.msc`` and verify that a service called ``cordanode1`` is present and running + +14. Run ``netstat -ano`` and check for the ports you configured in ``node.conf`` * You may need to open the ports on the Windows firewall diff --git a/docs/source/running-a-node.rst b/docs/source/running-a-node.rst index 3d646111c5..faef8eb2bf 100644 --- a/docs/source/running-a-node.rst +++ b/docs/source/running-a-node.rst @@ -90,3 +90,8 @@ After the nodes are started up, you can use ``docker ps`` command to see how the (Community Edition) is enough. Please refer to `Docker CE documentation `_ and `Docker Compose documentation `_ for installation instructions for all major operating systems. + +Database migrations +------------------- +Depending on the versions of Corda and of the CorDapps used, database migration scripts might need to run before a node is able to start. +For more information refer to :doc:`database-management`. \ No newline at end of file