On Windows, "Ping failed socket" errors

[ghost]

Just want to report an issue.

Pingbeat on Windows does not work. When starting the service the logs fill up immediately with the following error:

"CRIT Error: Ping failed socket: The requested protocol has not been configured into the system, or no implementation for it exists."

Error occurs on Windows 10 build 1511 PC, Windows Server 2008 R2 with SP1 server (fully updated), and on Windows 2012 R2 server (fully updated).

Pingbeat was built today on my Windows 10 PC. Followed standard go installation and git install instructions. I'm using the YML config from the sample provided just trying to ping google.com as a test. I tried adding in my own internal IP addresses for a few servers in the network but the same error occurs.

[joshuar]

Hi @joedissmeyer thanks for reporting! I don't actually test on Windows as I don't have easy access to that OS.

Just out of curiosity, is this error occurring whether you run pingbeat as a privileged user or not?

[ghost]

Good morning @joshuar! My pleasure.

Yes the error still occurs when manually running pingbeat.exe from an elevated prompt (by running CMD as an administrator).