Chapter 2. Analyze Red Hat Discovery system behavior and diagnose errors
Determine your Red Hat Discovery version, uninstall the server, get help with command-line interface commands, and configure Secure Shell (SSH) credentials. You can also locate log files, back up and restore encryption keys, and restart the server after a reboot.
2.1. Determine the version of the Red Hat Discovery server
Determine the version of the Red Hat Discovery server by using the command line interface to help with troubleshooting and support requests.
Prerequisites
- You are logged in to the command line interface as the Discovery server administrator.
Procedure
To determine the version of the Discovery server, use the following steps:
Enter the
dsc server statuscommand. The expected output provides the version of the server that you are using:"server_address": "127.0.0.1:9443", "server_id": "45a8ea20-2ec4-4113-b459-234fed505b0d", "server_version": "1.0.0.3e15fa8786a974c9eafe6376ff31ae0211972c36"If you cannot get the server status command to run, or you cannot log in to the server, use the following Podman images command:
podman images --filter 'reference=registry.redhat.io/discovery/discovery-server-rhel9' --format '{{.Labels.url}}'
2.2. Uninstall Red Hat Discovery
If you no longer need Discovery, you can uninstall the server and its associated packages from your system.
Prerequisites
- You are logged in to the system that is running Red Hat Discovery.
-
You have sudo access to perform certain functions in
dnf.
Procedure
- To uninstall Red Hat Discovery server, use the following steps:
Run the uninstall command.
discoveryctl uninstallUninstall the discoveryctl package.
sudo dnf remove discoveryctlOptional: Uninstall the command line interface, if installed.
sudo dnf remove discovery-cli
2.3. Get help with the command line interface
Access Discovery help through the man page and subcommand options to find usage details for the command line interface.
Prerequisites
- You are logged in to the command line interface as the Discovery server administrator.
Procedure
- For help on general topics, see the man page information.
For help on a specific subcommand, use the
-hoption. For example:dsc cred -h dsc source -h dsc scan -h
2.4. Secure Shell (SSH) credential configuration
If you receive an error message that includes text similar to not a valid file on the filesystem, that message might indicate an issue with the mount point. The mount point on the file system enables access to the SSH keyfiles.
2.5. Log file locations
Log files for the Discovery server are stored in specific directories that vary by component, helping you diagnose server and scanning issues.
| Location | Description |
|---|---|
|
| Log files on the local file system. |
|
|
Log data copied to |
|
| Log data for the Celery worker process. |
To follow the log output, include the -f option:
podman logs -f discovery-server
podman logs -f discovery-celery-worker2.6. Back up or restore the server encryption key
Passwords are not stored as plain text. They are encrypted and decrypted by using the content of the secret.txt file as a secret key. If you need to back up and restore the secret.txt file, use these steps.
Prerequisites
- You are logged in to the system that is running Red Hat Discovery.
-
You have sudo access to perform certain functions in
dnf.
Procedure
-
To back up the encrypted SSH credentials, navigate to
"${HOME}"/.local/share/discovery/datadirectory and copy thesecret.txtfile. To restore the
secret.txtfile, enter the following command, where path_to_backup is the path where thesecret.txtfile is backed up:cp -p __path_to_backup__/secret.txt "${HOME}"/.local/share/discovery/data/
2.7. Restart the Red Hat Discovery server after a reboot
If Discovery does not automatically restart after a system reboot, manually restart it by using the systemctl command.
Prerequisites
- You are logged in to the system that is running Red Hat Discovery.
-
You have sudo access to perform certain functions in
dnf.
Procedure
To restart the Discovery application after a reboot, use the following command:
systemctl --user restart discovery-app
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}