Bug: Response data comes back with unknowns.

[DEV-DIBSTER]

System: Debian GNU/Linux 10 (buster) x86_64 Version: 0.4.2

Response:

{
  inputHost: 'dibster.live',
  host: 'unknown',
  alive: false,
  output: '',
  time: 'unknown',
  times: [],
  min: 'unknown',
  max: 'unknown',
  avg: 'unknown',
  stddev: 'unknown',
  packetLoss: 'unknown'
}

On my Windows 10 laptop I am able to get perfect responses with the same package version and same request code. Double checked with the website, it is up, double checked on my laptop, works fine. Assuming an issue with Linux specifically.

[mondwan]

It looks like the ping command cannot be run at all as output is an empty string.

Do you have system ping installed? Is it installed in system path?

I will suggest you try the ping command on your own terminal first On Sat, 24 Dec 2022, 03:20 DIBSTER, @.***> wrote:

System: Debian GNU/Linux 10 (buster) x86_64 Version: 0.4.2

Response:

{ inputHost: 'dibster.live', host: 'unknown', alive: false, output: '', time: 'unknown', times: [], min: 'unknown', max: 'unknown', avg: 'unknown', stddev: 'unknown', packetLoss: 'unknown' }

On my Windows 10 laptop I am able to get perfect responses with the same package version and same request code. Double checked with the website, it is up, double checked on my laptop, works fine. Assuming an issue with Linux specifically.

— Reply to this email directly, view it on GitHub https://github.com/danielzzz/node-ping/issues/156, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5YBIZZI4P77P3GTUVG24DWOZTYZANCNFSM6AAAAAATIHEZRA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[DEV-DIBSTER]

After some testing I was able to figure out that is wasn't installed for some reason, I appreciate the help!