Skip to content

Commit a70574e

Browse files
committed
Some updates
1 parent 8863bd1 commit a70574e

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

articles/operator-nexus/howto-kubernetes-cluster-log-collector-script.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ Furthermore, the script does network connectivity tests by pinging the default g
2121

2222
## Prerequisite
2323

24-
Before proceeding, ensure that you have [access to the Nexus Kubernetes cluster node](./howto-kubernetes-cluster-connect.md#azure-arc-for-servers).
24+
Before proceeding, ensure that you have [SSH access to the Nexus Kubernetes cluster node](./howto-kubernetes-cluster-connect.md#azure-arc-for-servers).
2525

2626

27-
## Execution Steps
27+
## Execution steps
2828

29-
- Navigate to any working directory.
30-
- Run the log collector script `sudo /opt/log-collector/collect.sh`.
29+
- Connect to the Nexus Kubernetes cluster node using SSH.
30+
- Run the log collector script by executing the command `sudo /opt/log-collector/collect.sh`.
3131

3232
Upon execution, you observe an output similar to:
3333

@@ -44,16 +44,14 @@ Trying to collect SELinux status...
4444
Trying to archive gathered information...
4545
Finishing up...
4646
47-
Done... your bundled logs are located in /var/log/node_name_date_time_2024-03-11_1942-UTC.tar.gz
47+
Done... your bundled logs are located in /var/log/<node_name_date_time-UTC>.tar.gz
4848
```
4949

50-
## How to Download the Log File
51-
Once the tar file is generated, exit your cluster and use the following command to download the generated log file from your cluster to local machine.
50+
## How to download the log file
5251

53-
> [!NOTE]
54-
> The following command will work only on Linux
52+
Once the log file is generated, you can download the generated log file from your cluster node to your local machine using various methods, including SCP, SFTP or Azure CLI. However, it is important to note that SCP or SFTP are only possible if you have direct IP reachability to the cluster node. If you do not have direct IP reachability, you can use Azure CLI to download the log file.
5553

56-
This command is familiar—it’s the same one you’ve used before to access the Nexus Kubernetes cluster node. Now, all you need to do is run it again to copy files from the node to your local machine, just by adding the cat command at the end.
54+
This command should look familiar to you, as it is the same command used to SSH into the Nexus Kubernetes cluster node. To download the generated log file from the node to your local machine, simply use this command again, with the addition of the `cat` command at the end to copy the file.
5755

5856
```azurecli
5957
az ssh arc --subscription $SUBSCRIPTION_ID \
@@ -64,7 +62,7 @@ az ssh arc --subscription $SUBSCRIPTION_ID \
6462
'sudo cat /var/log/node_name_date_time-UTC.tar.gz' > <Local machine path>/node_name_date_time-UTC.tar.gz
6563
```
6664

67-
In the preceding command, replace `node_name_date_time-UTC.tar.gz` with the name of the log file created in your cluster, and `<Local machine path>` with the location on your local machine where you want to save the file.
65+
In the preceding command, replace `node_name_date_time-UTC.tar.gz` with the name of the log file created in your cluster node, and `<Local machine path>` with the location on your local machine where you want to save the file.
6866

6967
## Next steps
7068

0 commit comments

Comments
 (0)