Security Compliance
FS Logga collector remains in “Waiting for Collector restart after update” status in ARM
First published date
Last published date
Overview
An FS Logga collector may remain in “Waiting for Collector restart after update..” status even when the ARM server and collector versions match and network connectivity is available.
Product section
Cause
An expired certificate is bound to the file server’s WinRM HTTPS listener. This prevents ARM from completing the collector update or configuration workflow.
Resolution
-
On the file server hosting the collector, inspect the WinRM listeners:
-- Scripts are not supported under any SolarWinds support program or service. -- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, any damages for loss of business profits, -- business interruption, loss of business information, or other pecuniary loss) -- arising out of the use of or inability to use the scripts or documentation. winrm enumerate winrm/config/listener -
Check the certificate assigned to the HTTPS listener. Confirm that it is not expired, matches the collector’s FQDN, is trusted, and is valid for Server Authentication.
-
Renew and rebind the listener to a valid certificate. If the expired certificate is obsolete and is not used by another service, remove it according to your organization’s certificate-management process.
-
From the ARM server, test WinRM HTTPS connectivity to the collector:
Test-WSMan <Collector-FQDN> -UseSSL -
In ARM Configuration, open Collectors, right-click the affected collector, and select Restart Service.
-
Confirm that the collector reconnects and no longer remains in the waiting state.
NOTE: If the collector still reports no client certificate after the WinRM certificate is corrected, verify the collector registration and certificate details in ARM Connection Security. Manually installed collectors may require registration with an Init-Code.