You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Info (please complete the following information):
OS: Ubuntu 20.04.3 LTS
Browser: Chrome Version 95.0.4638.69 (64-bit)
RMM Version (as shown in top left of web UI): 0.10.1
Installation Method:
Standard
Docker
Agent Info (please complete the following information):
Agent version (as shown in the 'Summary' tab of the agent from web UI): Agent v1.7.0
Agent OS: Windows Server 2012 R2 Std.
Describe the bug
Occasionally receiving this error during a ping check. Pinging the destination shows the destination manually works.
read ip4 0.0.0.0: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
To Reproduce
Steps to reproduce the behavior:
Create a ping test.
Verify ping results are shown in the UI.
Shut down the destination machine to make it "unreachable". The error happens sporadically when the machine is up. Shutting it down is only to reproduce the problem.
Check the ping results.
Expected behavior
I expect the ping results to work if the host is up.
Screenshots
Additional context I'm opening this on behalf of some Discord users.
5am79 and Hugo on Discord had an error message exactly like issue #168 for go-ping/ping. The rmmagent code uses exec but I understand the rmmagent repo is not up to date. It's possible it uses go-ping/ping for ping.
The text was updated successfully, but these errors were encountered:
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
Occasionally receiving this error during a ping check. Pinging the destination shows the destination manually works.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect the ping results to work if the host is up.
Screenshots
![image](https://user-images.githubusercontent.com/7763429/142736319-1d9ae93b-7256-4dd2-be20-a646d3fec8d6.png)
![image](https://user-images.githubusercontent.com/7763429/142736331-57032560-2707-46d2-98a5-b613af994bc8.png)
Additional context
I'm opening this on behalf of some Discord users.
5am79 and Hugo on Discord had an error message exactly like issue #168 for go-ping/ping. The rmmagent code uses exec but I understand the rmmagent repo is not up to date. It's possible it uses go-ping/ping for ping.
The text was updated successfully, but these errors were encountered: