Communication problem

[Thaynara Soares]

Lately I'm noticing to "Update" for example if the agent is active or disconnected I need to restart my Worker01 and Worker02, até mesmo para receber novos agent preciso da um restart tem alguma configuração que preciso realizar para melhorar meu desempenho ? Even to receive new agents I need a restart, do I have any configuration I need to perform to improve my performance?It seems that there is no automatic update of the agent needs whenever update example was with 500 agent Active then I did a restart and updated to 900

My environment is currently in Cluster:

Index01    -----

Index02               -----

Master                            -- >    Proxy   ->  The machines

Worker01            ------

Worker02   -----

I currently own Agents (1,381)

[Thaynara Soares]

wazuh-master:/home/# tail -f /var/ossec/logs/cluster.log
2025/11/26 15:54:10 INFO: [Worker wazuh-worker02] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 15:54:10 INFO: [Worker wazuh-worker01] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 15:54:11 INFO: [Worker wazuh-worker01] [Integrity check] Starting.
2025/11/26 15:54:11 INFO: [Worker wazuh-worker01] [Integrity check] Finished in 0.006s. Received metadata of 308 files. Sync not required.
2025/11/26 15:54:11 INFO: [Master] [Local integrity] Starting.
2025/11/26 15:54:11 INFO: [Master] [Local integrity] Finished in 0.011s. Calculated metadata of 308 files.
2025/11/26 15:54:14 INFO: [Worker wazuh-worker02] [Integrity check] Starting.
2025/11/26 15:54:14 INFO: [Worker wazuh-worker02] [Integrity check] Finished in 0.007s. Received metadata of 308 files. Sync not required.
2025/11/26 15:54:15 INFO: [Worker wazuh-worker02] [Agent-info sync] Starting.
2025/11/26 15:54:15 INFO: [Worker wazuh-worker02] [Agent-info sync] Finished in 0.008s. Updated 1 chunks.
2025/11/26 15:54:19 INFO: [Master] [Local integrity] Starting.
2025/11/26 15:54:19 INFO: [Master] [Local integrity] Finished in 0.010s. Calculated metadata of 308 files.
2025/11/26 15:54:19 INFO: [Worker wazuh-worker01] [Agent-info sync] Starting.
2025/11/26 15:54:19 INFO: [Worker wazuh-worker01] [Agent-info sync] Finished in 0.009s. Updated 1 chunks.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker01] [Integrity check] Starting.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker01] [Integrity check] Finished in 0.005s. Received metadata of 308 files. Sync not required.
2025/11/26 15:54:20 INFO: [Master] [Local agent-groups] Starting.
2025/11/26 15:54:20 INFO: [Master] [Local agent-groups] Finished in 0.001s.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker02] [Agent-groups send] Starting.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker01] [Agent-groups send] Starting.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker02] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 15:54:20 INFO: [Worker wazuh-worker01] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 15:54:23 INFO: [Worker wazuh-worker02] [Integrity check] Starting.
2025/11/26 15:54:23 INFO: [Worker wazuh-worker02] [Integrity check] Finished in 0.005s. Received metadata of 308 files. Sync not required.
2025/11/26 15:54:25 INFO: [Worker wazuh-worker02] [Agent-info sync] Starting.
2025/11/26 15:54:25 INFO: [Worker wazuh-worker02] [Agent-info sync] Finished in 0.006s. Updated 1 chunks.
2025/11/26 15:54:27 INFO: [Master] [Local integrity] Starting.
2025/11/26 15:54:27 INFO: [Master] [Local integrity] Finished in 0.010s. Calculated metadata of 308 files.
2025/11/26 15:54:29 INFO: [Worker wazuh-worker01] [Integrity check] Starting.
2025/11/26 15:54:29 INFO: [Worker wazuh-worker01] [Integrity check] Finished in 0.006s. Received metadata of 308 files. Sync not required.
2025/11/26 15:54:29 INFO: [Worker wazuh-worker01] [Agent-info sync] Starting.
2025/11/26 15:54:29 INFO: [Worker wazuh-worker01] [Agent-info sync] Finished in 0.009s. Updated 1 chunks.
2025/11/26 15:54:30 INFO: [Master] [Local agent-groups] Starting.
2025/11/26 15:54:30 INFO: [Master] [Local agent-groups] Finished in 0.001s.
2025/11/26 15:54:30 INFO: [Worker wazuh-worker02] [Agent-groups send] Starting.
2025/11/26 15:54:30 INFO: [Worker wazuh-worker01] [Agent-groups send] Starting.
2025/11/26 15:54:30 INFO: [Worker wazuh-worker02] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 15:54:30 INFO: [Worker wazuh-worker01] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.

[Jorge Eduardo Molas]

Hi,if possible, could you please write your next message entirely in English? This will help ensure we fully understand your issue and provide the most accurate assistance.

Understanding your problem:

• Are you saying that the agent status (Active/Disconnected) doesn't update in the Wazuh Dashboard unless you restart Worker01 and Worker02?
• Do new agents fail to appear in the dashboard until you restart the workers?
• What Wazuh version are you running?

Additional information needed:

1. When you restart the workers, does the agent count/status update immediately in the dashboard?
2. Are the agents themselves functioning correctly (sending alerts, logs) even when shown as disconnected?
3. Have you checked the logs on your worker nodes for any errors?

bash

tail -f /var/ossec/logs/cluster.log

tail -f /var/ossec/logs/ossec.log

​

Initial recommendations:

• Verify cluster synchronization status from your Master node:

bash

/var/ossec/bin/cluster_control -l

• Check if there are any connection issues between Master and Workers

Please provide this information so we can help you identify the root cause and improve your cluster performance.

[Thaynara Soares]

1. • Are you saying that the agent status (Active/Disconnected) doesn't update in the Wazuh Dashboard unless you restart Worker01 and Worker02? Yes, lately it's been like that. I noticed I have quite a few disconnected agents, and when I restart, it also shows "updating the active agents," increasing the number.
   • Do new agents fail to appear in the dashboard until you restart the workers? Yes, if I don't restart it, it doesn't appear; it might appear eventually, but it takes hours and hours.
   • What Wazuh version are you running?   4.14.1
     
     
     
2. 1. When you restart the workers, does the agent count/status update immediately in the dashboard?  Yes, restarting the workers updates the agents immediately, and if there are new agents, it will also update them.
3. Are the agents themselves functioning correctly (sending alerts, logs) even when shown as disconnected? When the agent is disconnected, I can't receive the real-time logs.
4. Have you checked the logs on your worker nodes for any errors?    So far I haven't found an error log for this to explain why it's happening.

tail -f /var/ossec/logs/ossec.log

2025/11/26 15:51:25 wazuh-authd: INFO: Received request for a new agent (XXXXX) from: XX.XX.XX.XX
2025/11/26 15:51:25 wazuh-authd: WARNING: Duplicate name 'XXXXX', rejecting enrollment. Agent '1540' key already exists on the manager.
2025/11/26 15:52:04 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 15:52:16 wazuh-authd: INFO: Received request for a new agent (XXXXXX) from:  XX.XX.XX.XX
2025/11/26 15:52:16 wazuh-authd: WARNING: Duplicate name 'XXXXX', rejecting enrollment. Agent '1633' has not been disconnected long enough to be replaced.
2025/11/26 15:53:22 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 15:54:35 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 15:55:58 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 15:57:17 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 16:00:05 wazuh-modulesd: WARNING: Response buffer size limit reached.
2025/11/26 16:03:49 wazuh-authd: INFO: Received request for a new agent (XXXXXX) from:  XX.XX.XX.XX
2025/11/26 16:03:49 wazuh-authd: WARNING: Duplicate name 'XXXXX', rejecting enrollment. Agent '525' key already exists on the manager.
2025/11/26 16:03:49 wazuh-authd: INFO: Received request for a new agent (XXXXX) from:  XX.XX.XX.XX
2025/11/26 16:03:49 wazuh-authd: WARNING: Duplicate name 'XXXXXX', rejecting enrollment. Agent '370' has not been disconnected long enough to be replaced.

--------------------------------------------------------

tail -f /var/ossec/logs/cluster.log

2025/11/26 16:02:09 INFO: [Worker wazuh-worker01] [Integrity check] Starting.
2025/11/26 16:02:09 INFO: [Worker wazuh-worker01] [Integrity check] Finished in 0.005s. Received metadata of 308 files. Sync not required.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker01] [Agent-info sync] Starting.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker01] [Agent-info sync] Finished in 0.009s. Updated 1 chunks.
2025/11/26 16:02:10 INFO: [Master] [Local agent-groups] Starting.
2025/11/26 16:02:10 INFO: [Master] [Local agent-groups] Finished in 0.001s.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker02] [Agent-groups send] Starting.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker01] [Agent-groups send] Starting.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker02] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 16:02:10 INFO: [Worker wazuh-worker01] [Agent-groups send] Finished in -14399.994s. Updated 1 chunks.
2025/11/26 16:02:12 INFO: [Master] [Local integrity] Starting.
2025/11/26 16:02:12 INFO: [Master] [Local integrity] Finished in 0.012s. Calculated metadata of 308 files.
2025/11/26 16:02:13 INFO: [Worker wazuh-worker02] [Integrity check] Starting.
2025/11/26 16:02:13 INFO: [Worker wazuh-worker02] [Integrity check] Finished in 0.006s. Received metadata of 308 files. Sync not required.
2025/11/26 16:02:16 INFO: [Worker wazuh-worker02] [Agent-info sync] Starting.
2025/11/26 16:02:16 INFO: [Worker wazuh-worker02] [Agent-info sync] Finished in 0.008s. Updated 1 chunks.
2025/11/26 16:02:18 INFO: [Worker wazuh-worker01] [Integrity check] Starting.
2025/11/26 16:02:18 INFO: [Worker wazuh-worker01] [Integrity check] Finished in 0.006s. Received metadata of 308 files. Sync not required.
2025/11/26 16:02:20 INFO: [Master] [Local integrity] Starting.
2025/11/26 16:02:20 INFO: [Master] [Local integrity] Finished in 0.011s. Calculated metadata of 308 files.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker01] [Agent-info sync] Starting.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker01] [Agent-info sync] Finished in 0.009s. Updated 1 chunks.
2025/11/26 16:02:20 INFO: [Master] [Local agent-groups] Starting.
2025/11/26 16:02:20 INFO: [Master] [Local agent-groups] Finished in 0.001s.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker02] [Agent-groups send] Starting.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker01] [Agent-groups send] Starting.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker01] [Agent-groups send] Finished in -14399.997s. Updated 1 chunks.
2025/11/26 16:02:20 INFO: [Worker wazuh-worker02] [Agent-groups send] Finished in -14399.996s. Updated 1 chunks.
2025/11/26 16:02:22 INFO: [Worker wazuh-worker02] [Integrity check] Starting.
2025/11/26 16:02:22 INFO: [Worker wazuh-worker02] [Integrity check] Finished in 0.006s. Received metadata of 308 files. Sync not required.

-----------------------------------------------------------------------

/var/ossec/bin/cluster_control -l

NAME            TYPE    VERSION  ADDRESS        
wazuh-master    master  4.14.1   XX.XX.XX.XX  
wazuh-worker02  worker  4.14.1    XX.XX.XX.XX    
wazuh-worker01  worker  4.14.1    XX.XX.XX.XX

[Thaynara Soares]

Before restarting Worker01 and Worker02

After restarting Worker01 and Worker02

[Jorge Eduardo Molas]

Hi, since you mentioned agents appear as disconnected and only update after a worker restart, this could be related to:

• Agents that shutdown/startup at specific times (user workstations)
• Connection issues between agents and managers
• Agent status not properly updating on the manager side

Step 1: Verify agent connection status on the Master

Run these commands on your Master node (in /var/ossec/bin/):# Count currently connected agents

# Count currently connected agents ./agent_control -lc | wc -l # Count disconnected agents ./agent_control -ln | wc -l # List all active connections ./agent_control -lc

​

Compare these numbers with what you see in the Wazuh Dashboard. Do they match?

• If numbers match → the issue is between Manager and Dashboard/Indexer
• If numbers don't match → the issue is at the agent-manager connection level

Step 2: Monitor a specific disconnected agent

Identify one agent that shows as "disconnected" in the dashboard:

# Check agent status on manager ./agent_control -i AGENT_ID # Monitor real-time connections for that specific agent tail -f /var/ossec/logs/ossec.log | grep "AGENT_ID\|AGENT_NAME"

​

Step 3: Request agent-side logs

If the agent shows as disconnected on the manager side, please provide:

From the disconnected agent machine:

• Windows: C:\Program Files (x86)\ossec-agent\ossec.log
• Linux: /var/ossec/logs/ossec.log

Step 4: Check manager logs for that specific agent

grep "AGENT_NAME\|AGENT_ID" /var/ossec/logs/ossec.log | tail -50

​

[Thaynara Soares]

As the image shows, the information doesn't match up.

./agent_control -lc | wc -l
885

./agent_control -ln | wc -l
506

I am verifying the other requested information.

[Thaynara Soares]

What can I do in these cases to improve these situations? I need my agents to stay active continuously; they are becoming deactivated, and when I restart the Workers, they come back online but then crash again.

[Jorge Eduardo Molas]

Thank you for providing the agent count information. I can see the numbers match between the manager and dashboard (880 active, 502 disconnected), which confirms the agents are genuinely disconnecting from the managers - this is not a synchronization or display issue.

Before we can recommend solutions to keep your agents active, we need to understand why they are disconnecting. This is crucial because the solution will depend on the root cause.

Could you please help us identify the problem by providing the following information:

1. Nature of the disconnections:

• Are these agents on user workstations that shutdown at the end of the workday?
• Or are they servers/systems that should remain online 24/7?
• Do the disconnections happen at specific times, or randomly throughout the day?

2. Agent-side logs (critical):

Please select 2-3 agents that are currently showing as "Disconnected" and share their logs:

For Windows agents:

C:\Program Files (x86)\ossec-agent\ossec.log

​

For Linux agents:

/var/ossec/logs/ossec.log

​

3. Manager-side logs for specific agents:

On the Master node, check logs for those same disconnected agents:

grep "AGENT_NAME" /var/ossec/logs/ossec.log | tail -100

​

Please, replace AGENT_NAME with the actual agent hostname.

4. Network/Firewall considerations:

• Is there any firewall or network device between agents and managers?
• Have there been any recent network changes?
• Are agents connecting through NAT or load balancers?

Once you provide this information, we can determine the specific root cause and give you targeted recommendations to keep your agents connected reliably.

[Thaynara Soares]

• • Are these agents on user workstations that shutdown at the end of the workday?  The user can indeed shut down, but this happens frequently while the machine is on. As soon as I restart the workers, they reappear active. They may or may not shut down again, but more than 200 agents always do.
  • 
    
  • Or are they servers/systems that should remain online 24/7? No, they are user-owned machines.
  • Do the disconnections happen at specific times, or randomly throughout the day?  randomly

• Is there any firewall or network device between agents and managers? Yes, it has a firewall, but the ports are already open and there are rules for Wazuh communication.
• Have there been any recent network changes? No
• Are agents connecting through NAT or load balancers? Yes, it has NGINX; this is my load balancer configuration.

stream {
   upstream master {
       server IPMASTER:1515;
   }
   upstream mycluster {
   hash $remote_addr consistent;
       server IPWORKER01:1514;
       server  IPWORKER02 :1514;
   }
   server {
       listen 1515;
       proxy_pass master;
   }
   server {
       listen 1514;
       proxy_pass mycluster;
   }
}

 Manager-side logs for specific agents:

2025/11/28 14:51:17 wazuh-authd: INFO: Received request for a new agent (RP0*****) from: IPPROXY
2025/11/28 14:51:17 wazuh-authd: WARNING: Duplicate name 'RP0***', rejecting enrollment. Agent '1662' has not been disconnected long enough to be replaced.

 Agent-side logs:

2025/11/28 14:49:37 wazuh-agent: INFO: Requesting a key from server: wazuh-proxy
2025/11/28 14:49:37 wazuh-agent: ERROR: SSL error (1). Connection refused by the manager. Maybe the port specified is incorrect.
2025/11/28 14:49:47 wazuh-agent: WARNING: (4101): Waiting for server reply (not started). Tried: 'wazuh-proxy'. Ensure that the manager version is 'v4.14.1' or higher.
2025/11/28 14:49:47 wazuh-agent: WARNING: Unable to connect to any server.
2025/11/28 14:49:47 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:49:47 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:49:57 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:49:57 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:07 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:07 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:17 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:17 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:27 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:27 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:27 wazuh-agent: INFO: Requesting a key from server: wazuh-proxy
2025/11/28 14:50:27 wazuh-agent: ERROR: SSL error (1). Connection refused by the manager. Maybe the port specified is incorrect.
2025/11/28 14:50:37 wazuh-agent: WARNING: (4101): Waiting for server reply (not started). Tried: 'wazuh-proxy'. Ensure that the manager version is 'v4.14.1' or higher.
2025/11/28 14:50:37 wazuh-agent: WARNING: Unable to connect to any server.
2025/11/28 14:50:37 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:37 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:47 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:47 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:57 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:50:57 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:07 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:07 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:17 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:17 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:17 wazuh-agent: INFO: Requesting a key from server: wazuh-proxy
2025/11/28 14:51:17 wazuh-agent: INFO: No authentication password provided
2025/11/28 14:51:17 wazuh-agent: INFO: Using agent name as: RP0****
2025/11/28 14:51:17 wazuh-agent: INFO: Waiting for server reply
2025/11/28 14:51:17 wazuh-agent: ERROR: Duplicate agent name: RP0****. Unable to add agent (from manager)
2025/11/28 14:51:27 wazuh-agent: WARNING: (4101): Waiting for server reply (not started). Tried: 'wazuh-proxy'. Ensure that the manager version is 'v4.14.1' or higher.
2025/11/28 14:51:27 wazuh-agent: WARNING: Unable to connect to any server.
2025/11/28 14:51:27 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:27 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:37 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:37 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:47 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:47 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:57 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:51:57 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:07 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:07 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:07 wazuh-agent: INFO: Requesting a key from server: wazuh-proxy
2025/11/28 14:52:07 wazuh-agent: ERROR: SSL error (1). Connection refused by the manager. Maybe the port specified is incorrect.
2025/11/28 14:52:09 unset: INFO: Trust verification of a module failed by using the signature method. No signature found for 'C:\Program Files\NDDigital\nddPrint\Agent\nddPrint.Agent.SpoolMonitor32.dll'.
2025/11/28 14:52:09 unset: INFO: Trust verification of a module failed by using the hash method. CryptCATAdminEnumCatalogFromHash failed with error 1168 for 'C:\Program Files\NDDigital\nddPrint\Agent\nddPrint.Agent.SpoolMonitor32.dll': Elemento n o encontrado.
2025/11/28 14:52:09 unset: WARNING: The file 'C:\Program Files\NDDigital' is not signed or its signature is invalid.
2025/11/28 14:52:17 wazuh-agent: WARNING: (4101): Waiting for server reply (not started). Tried: 'wazuh-proxy'. Ensure that the manager version is 'v4.14.1' or higher.
2025/11/28 14:52:17 wazuh-agent: WARNING: Unable to connect to any server.
2025/11/28 14:52:17 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:17 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:27 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:27 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:37 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:37 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:47 wazuh-agent: INFO: Closing connection to server ([wazuh-proxy]:1514/tcp).
2025/11/28 14:52:47 wazuh-agent: INFO: Trying to connect to server ([wazuh-proxy]:1514/tcp).