Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Ping check] A message sent on a datagram socket was larger than the internal message buffer #812

Closed
1 of 2 tasks
NiceGuyIT opened this issue Nov 20, 2021 · 4 comments
Closed
1 of 2 tasks
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@NiceGuyIT
Copy link
Contributor

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:

  1. Create a ping test.
  2. Verify ping results are shown in the UI.
  3. 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.
  4. Check the ping results.

Expected behavior
I expect the ping results to work if the host is up.

Screenshots
image
image

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.

@dinger1986
Copy link
Collaborator

Also an error I have seen, however haven't reported as it clears the next time the check runs

@wh1te909
Copy link
Member

yes we are using the go-ping library now. so until that issue you linked is fixed I would recommend just creating your own ping script check

@silversword411 silversword411 added bug Something isn't working help wanted Extra attention is needed labels Nov 22, 2021
@wh1te909
Copy link
Member

wh1te909 commented Jun 7, 2022

here a script check you can add that functions similar to a ping check:

import subprocess
import sys

if len(sys.argv) != 2:
    print("ERROR: Missing hostname or ip argument")
    sys.exit(1)

cmd = ["ping.exe", sys.argv[1], "-n", "5"]

r = subprocess.run(cmd, capture_output=True)

success = ["Reply", "bytes", "time", "TTL"]

print(r.stdout.decode())

if all (i in r.stdout.decode() for i in success):
    sys.exit(0)

sys.exit(1)

@silversword411
Copy link
Collaborator

For those that can't read python....that's python 😉

redanthrax pushed a commit to redanthrax/rmmagent that referenced this issue Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants