2 Replies Latest reply on Aug 28, 2014 7:55 AM by gtrounds

    "Flapping" Agent becoming Available and Unavailable constantly

    gtrounds

      Ever since I upgraded from Orion 10.7 to 11.1 Yesterday, our main Agent (The one solarwinds is hosted on) has been reportedly becoming unavailable and available constantly. I have attempted to restart the services and reboot the server, and I have had no luck. I have not seen anyone else with this issue, and I am unsure of what to try next.

      Capture.PNG

        • Re: "Flapping" Agent becoming Available and Unavailable constantly
          rob.hock

          There could be quite a few reasons why the local agent is flapping. A support case is likely the best course of action. Barring that, agent logs may be found here:

           

          c:\ProgramData\Solarwinds\Logs\AgentManagement\
          c:\ProgramData\Solarwinds\Logs\Agent\

            • Re: "Flapping" Agent becoming Available and Unavailable constantly
              gtrounds

              Thank you rob, I've taken a look at the logs and have noticed a lot of errors and warnings. However, I really don't have any clue of what they actually mean. Here is an example of them:

              • 2014/08/26 09:28:34:368 PID: 15772 TID:  9340 [ERROR] SignalRClientBase::OnError() - SignalR error: Error in: WinHttpQueryDataAvaliable
              • 2014/08/26 09:29:59:131 PID: 15772 TID: 13224 [ERROR] ewAsyncRpcCommon::AsyncRpcClientLoopImpl::Loop -  ping() failed: client id [(400D4F78-6C1C-46E4-992F-E1223DE738F4.EWA) -> (2fd055f2-5e2d-4d9d-9b4b-d93375b4ca4f.AMS) UEMF-APP04.UEMF.local:17778], incomplete, error code [0x65b], message [w32_exception caught: Error [1627L], [ProvisionClientLib::SignalRClientBase::RegisterClient - continuation failed with exception], File: ..\AsyncRpcCommon\AsyncRpcClientLoopImpl.cpp, Line: 174]</li>
              • 2014/08/26 09:31:32:051 PID: 15772 TID: 11344 [ERROR] ProvisionClientLib::SignalRClientBase::begin_async_exchange::<lambda_55673ec5eed72fc54f09638561deb169>::operator ()- Exception calling Exchange on the server, deviceId [400D4F78-6C1C-46E4-992F-E1223DE738F4.EWA], callCounter [1] : std::exception caught: Description: [Exchange called from deviceId [400D4F78-6C1C-46E4-992F-E1223DE738F4.EWA] (ConnectionId [47b25962-244c-46b1-b26d-970136c5c49c], HubId [Messaging]) rejected, client is not registered.], File: SignalRClientBase.cpp, Line: 327
              • 2014/08/26 09:31:32:051 PID: 15772 TID: 13224 [ERROR] ewAsyncRpcCommon::AsyncRpcClientLoopImpl::Loop - begin_async_exchange() failed, client id [(400D4F78-6C1C-46E4-992F-E1223DE738F4.EWA) -> (2fd055f2-5e2d-4d9d-9b4b-d93375b4ca4f.AMS) UEMF-APP04.UEMF.local:17778], error code [0x65b], message [w32_exception caught: Error [1627L], [ProvisionClientLib::SignalRClientBase::begin_async_exchange - continuation failed with exception, Exchange #224, deviceId [400D4F78-6C1C-46E4-992F-E1223DE738F4.EWA]], File: ..\AsyncRpcCommon\AsyncRpcClientLoopImpl.cpp, Line: 96]

               

               

              These errors repeat a LOT throughout the log. Maybe I can remove and re-add the agent?