Skip to content

update exec commands w/ splunk user #329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 9, 2020
Merged

update exec commands w/ splunk user #329

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/TROUBLESHOOTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,9 @@ $ docker logs -f <container_name/container_id>
If your container is still running but in a bad state, you can try to debug by putting yourself within the context of that process.


To gain interactive shell access to the container's runtime, you can run:
To gain interactive shell access to the container's runtime as the splunk user, you can run:
```
$ docker exec -it <container_name/container_id> /bin/bash
$ docker exec -it -u splunk <container_name/container_id> /bin/bash
```

#### Debug variables
Expand Down Expand Up @@ -142,17 +142,17 @@ Generating a diag is only an option if:

To create this diag, run the following command:
```
$ docker exec -it <container_name/container_id> ${SPLUNK_HOME}/bin/splunk diag
$ docker exec -it -u splunk <container_name/container_id> "${SPLUNK_HOME}/bin/splunk diag"
```

Additionally, if your Docker container/hosts have access to https://www.splunk.com you can now send the file directly to Splunk Support by using the following command:
```
$ docker exec -it <container_name/container_id> ${SPLUNK_HOME}/bin/splunk diag --upload --case-number=<case_num> --upload-user=<your_splunk_id> --upload-password=<passwd> --upload-description="Monday diag, as requested"
$ docker exec -it -u splunk <container_name/container_id> "${SPLUNK_HOME}/bin/splunk diag --upload --case-number=<case_num> --upload-user=<your_splunk_id> --upload-password=<passwd> --upload-description='Monday diag, as requested'"
```

However, if you don't have direct access, you can manually copy the diag back to your host via `docker cp`:
```
$ docker cp <container_name/container_id>:/opt/splunk/var/run/diags/<filename> <location on your local machine>
$ docker cp <container_name/container_id>:/opt/splunk/<filename> <location on your local machine>
```

## Contact
Expand Down