TimWillemstein2 (Customer) asked a question.
I have a new server that on which I'm trying to install a new Remote AveksaAgent (i have like 5 already on other servers working). However I keep getting this error when I start the Remote Agent:
04/04/2024 11:03:02.188 INFO (main) [com.aveksa.client.datacollector.agent.AgentConfiguration] Aveksa Product Version: 7.5.2
04/04/2024 11:03:02.226 INFO (main) [com.aveksa.client.component.communication.DefaultCommunicationManager] DCM82: Initiating handshake with server
04/04/2024 11:03:02.637 FATAL (main) [com.aveksa.client.datacollector.startup.Bootstrap] Error occurred while Bootstrap command start was executing.
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_402]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_402]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_402]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_402]
at com.aveksa.client.datacollector.startup.Bootstrap.start(Bootstrap.java:356) ~[bootstrap.jar:?]
at com.aveksa.client.datacollector.startup.Bootstrap.main(Bootstrap.java:788) ~[bootstrap.jar:?]
Caused by: com.aveksa.client.datacollector.agent.FatalAgentException: com.aveksa.client.datacollector.agent.ServerUnavailableException: com.aveksa.server.agent.message.ConnectionException: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at com.aveksa.client.component.communication.DefaultCommunicationManager.<init>(DefaultCommunicationManager.java:133) ~[components.jar:?]
at com.aveksa.client.component.communication.DefaultCommunicationManager.getInstance(DefaultCommunicationManager.java:348) ~[components.jar:?]
at com.aveksa.client.component.DefaultComponentManager.createCommunicationManager(DefaultComponentManager.java:243) ~[components.jar:?]
at com.aveksa.client.datacollector.agent.Agent.doWork(Agent.java:82) ~[datacollectoragent.jar:?]
at com.aveksa.client.datacollector.startup.agent.AgentService.start(AgentService.java:26) ~[datacollectoragent.jar:?]
... 6 more
Caused by: com.aveksa.client.datacollector.agent.ServerUnavailableException: com.aveksa.server.agent.message.ConnectionException: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at com.aveksa.client.datacollector.agent.ServiceManager.initiateHandshake(ServiceManager.java:255) ~[datacollectoragent.jar:?]
at com.aveksa.client.component.communication.DefaultCommunicationManager.<init>(DefaultCommunicationManager.java:108) ~[components.jar:?]
at com.aveksa.client.component.communication.DefaultCommunicationManager.getInstance(DefaultCommunicationManager.java:348) ~
04/04/2024 11:03:02.648 INFO (Thread-1) [com.aveksa.client.datacollector.startup.agent.AgentShutDownHook] Executing ShutDownHook. Please wait...
04/04/2024 11:03:02.648 INFO (Thread-1) [com.aveksa.client.datacollector.agent.Agent] A172: Agent is shutting down
Does anyone have an idea on what could be the issue here? The forums / KB articles haven't listed any similar issue as far as I could tell. The remote server can reach my frontend server normally without any issue's on port 8444.
Let me update that for any future references..
So it turns out the issue was in my networking. So even though the port was apparently open the agent and afx both failed with the error as seen above. It turns out that a load balancer in between was accepting the connection but another firewall after that dropped the connection. For some reason this resulted in successful port ping checks but failure overall.
I was able to figure this out by checking the certificate being returned by my server:
openssl s_client -showcerts -connect yourhost:8444 </dev/null
If this doesn't return the certificate from your server (in my case it was empty) you know your connection is not setup correctly.