Agent not showing as online in manager

Tags:

#1 nervevector
Hello, We've deployed NXLog EE agents on numerous Windows servers, and we're facing a strange issue with just one agent. It does not, and we're unable to get it to, show as online within the NXLog Manager. The agent's log states that it was able to successfully connect to the manager, but it's still showing as offline in the UI. I have tried the following: * Upgraded agent to the latest version * Verified that the agent's logs said it was able to connect to the manager (10.40.1.90) * Removed the agent from the manager interface * Removed the agent off of the server * Reinstalled the agent on the server, and reconfigured the certificate and managed.conf file * Verified that it connected to the manager in the agent's logs And even after all of that, the agent is still showing as offline on the manager's UI. 2022-09-23 16:22:40 WARNING [CORE|main] no functional input modules! 2022-09-23 16:22:40 INFO [CORE|main] nxlog-5.6.7727 (50b2a4353@REL_v5.6) started on Windows 2022-09-23 16:22:40 INFO [xm_admin|agent_management] connecting to 192.168.1.1:4041 2022-09-23 16:23:01 ERROR [xm_admin|agent_management] couldn't connect to 192.168.1.1:4041; A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022-09-23 16:23:01 INFO [xm_admin|agent_management] reconnecting to 192.168.1.1:4041 in 1 sec 2022-09-23 16:23:02 INFO [xm_admin|agent_management] connecting to 192.168.1.1:4041 2022-09-23 16:23:21 WARNING [CORE|main] stopping nxlog service 2022-09-23 16:23:21 WARNING [CORE|main] nxlog received a termination request signal, exiting... 2022-09-23 16:23:23 ERROR [xm_admin|agent_management] couldn't connect to 192.168.1.1:4041; A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022-09-23 16:23:23 INFO [xm_admin|agent_management] reconnecting to 192.168.1.1:4041 in 2 sec 2022-09-23 16:23:24 WARNING [CORE|main] no functional input modules! 2022-09-23 16:23:24 INFO [CORE|main] nxlog-5.6.7727 (50b2a4353@REL_v5.6) started on Windows 2022-09-23 16:23:24 INFO [xm_admin|agent_management] connecting to 10.40.1.90:4041
#2 secdef

We have the same issue.  Were you ever able to get it resolved?