Chapter 2. Troubleshooting Discovery
2.1. Determining the version of the Discovery server
Prerequisites
- You must be 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. Uninstalling Discovery
Prerequisites
- You must be logged in to the system that is running Discovery.
-
You will need sudo access to perform certain functions in
dnf.
Procedure
To uninstall Discovery server, use the following steps:
Run the uninstall command.
discovery-installer uninstall
Uninstall the installer package.
sudo dnf remove discovery-installer
Uninstall the command line interface, if installed.
sudo dnf remove discovery-cli
2.3. Getting help with the command line interface
Prerequisites
- You must be 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. 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 on the file system that enables access to the SSH keyfiles.
2.5. Log file locations
Prerequisites
- You must be logged in to the system that is running Discovery.
-
You will need sudo access to perform certain functions in
dnf.
Procedure
Log files for the Discovery server that are on the local file system are located in the following path: "{HOME}"/.local/share/discovery/log.
Log data is also copied to stdout and can be accessed through Podman logs. To follow the log output, include the -f option as shown in the following command:
podman logs -f discovery-server podman logs -f discovery-celery-worker
2.6. Backing up or restoring 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 must be logged in to the system that is running Discovery.
-
You will need 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. Restarting the Discovery server after a reboot
Prerequisites
- You must be logged in to the system that is running Discovery.
-
You will need sudo access to perform certain functions in
dnf.
If you installed Discovery using the standard process, the system should start automatically after a reboot. If it does not automatically restart, use the following procedure:
Procedure
- To restart the Discovery application after a reboot, use the following command:
systemctl --user restart discovery-app
