20.15. kb-00014: Debug Sledgehammer Problems¶
20.15.1. Knowledge Base Article: kb-00014¶
20.15.2. Description¶
From time to time, a Machines environment, hostname, or other factors may cause the Sledgehammer (also called Discovery) BootEnv to fail to boot or start Workflow successfully. In these cases, you will need to log in to the Machines console, and debug the problem.
20.15.3. Solution¶
If the sledgehammer discovery image should fail to launch Runner jobs successfully, or other
issues arise with the start up sequences, you can debug start up via the systemd logging. Log
in to the console of the Machine in question (or if SSH is running and you have access-keys
setup, you can SSH in), and run the following command to output logging:
journalctl -u sledgehammer
20.15.4. Additional Information¶
Additional resources and information related to this Knowledge Base article.
20.15.4.1. See Also¶
20.15.4.2. Versions¶
all
20.15.4.3. Keywords¶
dr-provision, sledgehammer, discovery, discover, bootenv, debug
20.15.4.4. Revision Information¶
KB Article : kb-00014 initial release: Wed Jun 10 11:16:26 PDT 2020 updated release: Wed Jun 10 11:16:26 PDT 2020
