Discussion:
mtr on 8.0_RC1
(too old to reply)
Havard Eidnes
2018-06-06 07:25:07 UTC
Permalink
Hi,

it appears that "something" changed between 8.0_BETA of March 14
2018 and 8.0_RC1 of June 5 2018. "mtr" when tracing towards an
IPv6 destination now all too often (and pretty quickly) exits
with

mtr: Unexpected mtr-packet error

Ktracing this reveals:

1557 1 mtr-packet CALL sendto(5,0x7f7fff2ac6d0,0x18,0,0x759ea6b050d8,0x1c)
1557 1 mtr-packet MISC msghdr: [name=0x759ea6b050d8, namelen=28, iov=0xffff80013a5daf50, iovlen=1, control=0x0, controllen=2168972952, flags=0]
1557 1 mtr-packet MISC mbsoname: [2001:700:xxxx:xxxx:xx:xx:xx:xx]
1557 1 mtr-packet RET sendto -1 errno 55 No buffer space available
1557 1 mtr-packet CALL write(1,0x759ea6b01000,0x20)
1557 1 mtr-packet GIO fd 1 wrote 32 bytes
"33008 unexpected-error errno 55\n"
1557 1 mtr-packet RET write 32/0x20

Is this somehow related to the addition of ENOBUFS as a new error
on certain receive operations?

"Please make it stop, at least by default!"

Regards,

- Håvard

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Roy Marples
2018-06-06 08:42:59 UTC
Permalink
Hi Havard
Post by Havard Eidnes
it appears that "something" changed between 8.0_BETA of March 14
2018 and 8.0_RC1 of June 5 2018. "mtr" when tracing towards an
IPv6 destination now all too often (and pretty quickly) exits
with
mtr: Unexpected mtr-packet error
1557 1 mtr-packet CALL sendto(5,0x7f7fff2ac6d0,0x18,0,0x759ea6b050d8,0x1c)
1557 1 mtr-packet MISC msghdr: [name=0x759ea6b050d8, namelen=28, iov=0xffff80013a5daf50, iovlen=1, control=0x0, controllen=2168972952, flags=0]
1557 1 mtr-packet MISC mbsoname: [2001:700:xxxx:xxxx:xx:xx:xx:xx]
1557 1 mtr-packet RET sendto -1 errno 55 No buffer space available
1557 1 mtr-packet CALL write(1,0x759ea6b01000,0x20)
1557 1 mtr-packet GIO fd 1 wrote 32 bytes
"33008 unexpected-error errno 55\n"
1557 1 mtr-packet RET write 32/0x20
Is this somehow related to the addition of ENOBUFS as a new error
on certain receive operations?
"Please make it stop, at least by default!"
Can you test the attached patch please?
It seperates receive errors from general socket errors so should fix this.

Roy
Havard Eidnes
2018-06-06 09:34:38 UTC
Permalink
Post by Roy Marples
Can you test the attached patch please?
It seperates receive errors from general socket errors so should fix this.
It fixes the situation for "mtr", thanks!

Regards,

- Håvard

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Roy Marples
2018-06-06 09:47:19 UTC
Permalink
Post by Havard Eidnes
Post by Roy Marples
Can you test the attached patch please?
It seperates receive errors from general socket errors so should fix this.
It fixes the situation for "mtr", thanks!
Committed!
Thanks for testing.

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...