Stand Alone deployment document optimization

src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -142,7 +142,7 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 
 ### Start DataNode
@@ -311,7 +311,7 @@ sbin/remove-datanode.bat [datanode_id]
 ```
 ## Common Questions
 
-1. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+1. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/Master/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,7 +142,7 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 
 ### Activate Database
@@ -352,7 +352,7 @@ sbin/remove-datanode.bat [datanode_id]
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
     - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
 
-2. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+2. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -110,6 +110,7 @@ Enter the sbin directory of iotdb and start confignode
 ```Shell
 ./start-confignode.sh    -d      #The "- d" parameter will start in the background 
 ```
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### 4、Start DataNode
 
@@ -138,4 +139,41 @@ When the status is all running, it indicates that the service has started succes
 
 ![](https://alioss.timecho.com/docs/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg)
 
-> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+
+## Common Questions
+
+1. Confignode failed to start
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/Master/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md

@@ -114,6 +114,7 @@ Enter the sbin directory of iotdb and start confignode
 ```shell
 ./start-confignode.sh    -d      #The "- d" parameter will start in the background 
 ```
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### 4、Activate Database
 
@@ -182,4 +183,39 @@ When you see the display "Activated" on the far right, it indicates successful a
 ## Common Problem
 1. Multiple prompts indicating activation failure during deployment process
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
-    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+
+2. Confignode failed to start
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/V1.3.0-2/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -142,7 +142,7 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### Start DataNode
 
@@ -312,7 +312,7 @@ sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
 
 ## Common Questions
 
-1. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+1. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/V1.3.0-2/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,7 +142,7 @@ Start the first confignode of IoTDB-1 first, ensuring that the seed confignode n
 cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### Activate Database
 
@@ -353,7 +353,7 @@ sbin/remove-datanode.bat [dn_rpc_address:dn_rpc_port]
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
     - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
 
-2. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+2. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/V1.3.0-2/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -110,6 +110,7 @@ Enter the sbin directory of iotdb and start confignode
 ```Shell
 ./start-confignode.sh    -d      #The "- d" parameter will start in the background 
 ```
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### Start DataNode
 
@@ -138,4 +139,41 @@ When the status is all running, it indicates that the service has started succes
 
 ![](https://alioss.timecho.com/docs/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg)
 
-> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+
+## Common Questions
+
+1. Confignode failed to start
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/V1.3.0-2/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md

@@ -116,6 +116,7 @@ Enter the sbin directory of iotdb and start confignode
 ```shell
 ./start-confignode.sh    -d      #The "- d" parameter will start in the background 
 ```
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### Activate Database
 
@@ -183,4 +184,39 @@ When you see the display "Activated" on the far right, it indicates successful a
 ## Common Problem
 1. Multiple prompts indicating activation failure during deployment process
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
-    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+    - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
+
+2. Confignode failed to start
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```

src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_apache.md

@@ -142,7 +142,7 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 
 ### Start DataNode
@@ -311,7 +311,7 @@ sbin/remove-datanode.bat [datanode_id]
 ```
 ## Common Questions
 
-1. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+1. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/latest/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -142,7 +142,7 @@ cd sbin
 ./start-confignode.sh    -d      #"- d" parameter will start in the background
 ```
 
-If the startup fails, please refer to [Common Questions](#common-questions) for solutions.
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 
 ### Activate Database
@@ -352,7 +352,7 @@ sbin/remove-datanode.bat [datanode_id]
     - Use the `ls -al` command: Use the `ls -al` command to check if the owner information of the installation package root directory is the current user.
     - Check activation directory: Check all files in the `./activation` directory and whether the owner information is the current user.
 
-2. After starting the confignode command, does the node fail to start multiple times or receive prompts for running errors?
+2. Confignode failed to start
 
     Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
 

src/UserGuide/latest/Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md

@@ -110,6 +110,7 @@ Enter the sbin directory of iotdb and start confignode
 ```Shell
 ./start-confignode.sh    -d      #The "- d" parameter will start in the background 
 ```
+If the startup fails, please refer to [Common Questions](#common-questions).
 
 ### 4、Start DataNode
 
@@ -138,4 +139,41 @@ When the status is all running, it indicates that the service has started succes
 
 ![](https://alioss.timecho.com/docs/img/%E5%BC%80%E6%BA%90-%E5%8D%95%E6%9C%BAshow.jpeg)
 
-> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+> The appearance of 'Activated (W)' indicates passive activation, indicating that this Config Node does not have a license file (or has not issued the latest license file with a timestamp). At this point, it is recommended to check if the license file has been placed in the license folder. If not, please place the license file. If a license file already exists, it may be due to inconsistency between the license file of this node and the information of other nodes. Please contact Timecho staff to reapply.
+
+## Common Questions
+
+1. Confignode failed to start
+
+    Step 1: Please check the startup log to see if any parameters that cannot be changed after the first startup have been modified.
+
+    Step 2: Please check the startup log for any other abnormalities. If there are any abnormal phenomena in the log, please contact Timecho Technical Support personnel for consultation on solutions.
+
+    Step 3: If it is the first deployment or data can be deleted, you can also clean up the environment according to the following steps, redeploy, and restart.
+
+    Clean up the environment:
+
+   ​	Execute the following on all nodes:
+
+   1. Terminate all ConfigNode Node and DataNode processes.
+   ```Bash
+     # 1. Stop the ConfigNode and DataNode services
+     sbin/stop-standalone.sh
+
+     # 2. Check for any remaining processes
+     jps
+     # Or
+     ps -ef|gerp iotdb
+
+     # 3. If there are any remaining processes, manually kill the
+     kill -9 <pid>
+     # If you are sure there is only one iotdb on the machine, you can use the following command to clean up residual processes
+     ps -ef|grep iotdb|grep -v grep|tr -s '  ' ' ' |cut -d ' ' -f2|xargs kill -9
+   ```
+   2.  Delete the data and logs directories.
+
+   Explanation: Deleting the data directory is necessary, deleting the logs directory is for clean logs and is not mandatory.
+   ```Bash
+     cd /data/iotdb
+     rm -rf data logs
+   ```