Hello,
I'm having trouble providing you with service logs.
When the problem occurs and we run the command, it restarts the service and it works... I'll try leaving the debugger running for several days on a machine.
Regards,
The search returned 3 results
- April 12, 2019 - 10:44
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Reporting errors by agents
- Answers: 3
- Views : 5271
- April 3, 2019 - 7:54 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Reporting errors by agents
- Answers: 3
- Views : 5271
Re: Reporting agents' error
Hello,
I've tried to make some progress on this issue.
It seems the agents are opening a lot of sockets to the server, and at some point, there are no more ports available for communication. I thought this was due to the listening ports on the server, but it seems to be related to the...
I've tried to make some progress on this issue.
It seems the agents are opening a lot of sockets to the server, and at some point, there are no more ports available for communication. I thought this was due to the listening ports on the server, but it seems to be related to the...
- April 1, 2019 - 2:08 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Reporting errors by agents
- Answers: 3
- Views : 5271
Reporting of error by agents
Hello,
Since the middle of last week, nearly a third of our machines have been showing as disconnected in WAPT, although they are accessible from the network.
In the agent logs, I find the following:
2019-04-01 13:49:16,072 WARNING Websocket connect params: HTTPSConnectionPool(host ...
Since the middle of last week, nearly a third of our machines have been showing as disconnected in WAPT, although they are accessible from the network.
In the agent logs, I find the following:
2019-04-01 13:49:16,072 WARNING Websocket connect params: HTTPSConnectionPool(host ...
