-
Notifications
You must be signed in to change notification settings - Fork 105
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
missing error messages from stderr #158
Comments
Hello, errors reported here are too generic. Please include how you run the library, actual responses, and expected responses. As mentioned in louislam/uptime-kuma/issues/2896, please also include how your system behaved while running the system ping if you believed the errors are coming from the system instead. |
I updated the thread with outputs. We can know that |
Hopefully, #159 should resolve this bug |
Try release 0.4.4 |
Thank you for fixing! |
That's great.
Just wondering. Hopefully, you are using BusyBox or something like that.
Can you also show me the value of "os.platform()"?
The value in the numeric host field is bad. But, it is probably due to
picking a wrong parser. The library should pick a Mac base parser for your
case
…On Sat, 11 Mar 2023, 22:13 Raymond Hackley, ***@***.***> wrote:
{
inputHost: 'p.p',
host: 'bad',
alive: false,
output: "ping: bad address 'p.p'\n",
time: 'unknown',
times: [],
min: 'unknown',
max: 'unknown',
avg: 'unknown',
stddev: 'unknown',
packetLoss: 'unknown',
numeric_host: 'ddres'
}
{
inputHost: '1.1.1.1',
host: '1.1.1.1',
alive: false,
output: 'PING 1.1.1.1 (1.1.1.1): 56 data bytes\n' +
'ping: permission denied (are you root?)\n',
time: 'unknown',
times: [],
min: 'unknown',
max: 'unknown',
avg: 'unknown',
stddev: 'unknown',
packetLoss: 'unknown',
numeric_host: '1.1.1.1)'
}
Thank you for fixing!
—
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5YBIZQBLZTHPVQO7YKMVDW3T2I7ANCNFSM6AAAAAAVTNQMSI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I mean I would like to know the value from the module in node js In your captured sample, the value of the field Given that the format of ping's output depends on the underlying platform, there are 3 kinds of parsers in this library: MAC / LINUX / WINDOW. This library will pick the corresponding parser depends on the value from The problematic |
Otherwise, I need to fix the linux parser accordingly. lol |
Yes |
Reproduction steps
Ping something which returns errors.
Expected behavior
Messages from stderr are included in the responses.
Actual Behavior
The responses don't have messages from stderr included.
Relevant issue: louislam/uptime-kuma#2896
Operating System and Arch
Alpine 3.17 armv7
Ping
BusyBox v1.35.0
NodeJS Version
18.14.2
The text was updated successfully, but these errors were encountered: