Hermes Diagnostics Check logs show Problem getting cluster identifiers errorIssue Hermes Diagnostics Check errors appear in the logs even though the Hermes plugin is installed but not used in the instance. The log entries are similar to the following: SysLog SEVERE *** ERROR *** com.glide.hermes.HermesHealthStatus: Problem getting cluster identifiers. Will skip. Cluster: <cluster-name>: java.util.concurrent.TimeoutException The goal is to turn off these Hermes Diagnostics Check logs. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yokohama Resolution Turn off the Hermes Diagnostics Check job in the sysauto_script table by making the job inactive. 1.Find the Hermes Diagnostics Check job. 2.Make the Hermes Diagnostics Check job inactive. Related Links