Home | Devuan | Git | Forum | Packages | Popcon
Donate now!
Download

Devuan bug report logs - #774
traceroute: Exit code is not reliable nor documented

Package: traceroute; Severity: grave; Reported by: Alessandro Vesely <[email protected]>; Keywords: debian; Forwarded to https://bugs.debian.org/1050039; Maintainer for traceroute is (unknown).
Set bug forwarded-to-address to 'https://bugs.debian.org/1050039'. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Message received at [email protected]:


Received: (at 774) by bugs.devuan.org; 18 Aug 2023 19:04:32 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2a01:4f8:140:32a1::58c6:6473]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 18 Aug 2023 19:04:32 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id g4qEC6DA32SVHgAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 18 Aug 2023 19:04:00 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 232B85F5; Fri, 18 Aug 2023 19:04:00 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 179F527
	for <[email protected]>; Fri, 18 Aug 2023 19:03:54 +0000 (UTC)
Received: from hindley.org.uk (apollo.hindleynet [192.168.1.3])
	by mx.hindley.org.uk (Postfix) with SMTP id 6494BE0D;
	Fri, 18 Aug 2023 20:03:53 +0100 (BST)
Received: (nullmailer pid 31047 invoked by uid 1000);
	Fri, 18 Aug 2023 19:03:53 -0000
Date: Fri, 18 Aug 2023 20:03:53 +0100
From: Mark Hindley <[email protected]>
To: Alessandro Vesely <[email protected]>
Cc: [email protected]
Subject: Re: bug#774: traceroute: Exit code is not reliable nor documented
Message-ID: <ZN/[email protected]>
References: <169234611173.22998.13478232296979279263.reportbug@north.ext.tana.it>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: forwarded -1 https://bugs.debian.org/1050039

On Fri, Aug 18, 2023 at 08:23:23PM +0200, Alessandro Vesely wrote:
> Hm... I used reportbug.  Now I repeated the same using --bts=debian.

Thanks. Adding forwarded. 

> Wouldn't it have been possible to just forward the message somewhere?

Well, it wasn't *my* report. However, reportbug in daedalus tries to pick the
correct BTS by default.

Mark
Acknowledgement sent to Mark Hindley <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.
Information forwarded to [email protected], [email protected]:
bug#774; Package traceroute. Full text available.

Message received at [email protected]:


Received: (at 774) by bugs.devuan.org; 18 Aug 2023 18:24:02 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2a01:4f8:140:32a1::58c6:6473]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 18 Aug 2023 18:24:02 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id KlQjDiK332R/HAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 18 Aug 2023 18:23:30 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 23FAC5F5; Fri, 18 Aug 2023 18:23:30 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,NICE_REPLY_A,RCVD_IN_DNSWL_MED,SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=94.198.96.74; helo=wmail.tana.it; [email protected]; receiver=<UNKNOWN> 
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74])
	by email.devuan.org (Postfix) with ESMTPS id D070F27
	for <[email protected]>; Fri, 18 Aug 2023 18:23:27 +0000 (UTC)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it;
	s=epsilon; t=1692383004;
	bh=gW7sJHyDm6+UpFfujHUkEcAAwCCQsqlwbnjy5fVQXKM=;
	h=Author:Date:Subject:To:References:From:In-Reply-To;
	b=oukkAfUGIAmFhiDZxBE0Akd8ScmRpj/xALeV9Okpi9DWOOEesxdhDdHVyDX77Kwc8
	 +wH78x+Rwy/gGuaThtcBQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta;
	t=1692383004; bh=gW7sJHyDm6+UpFfujHUkEcAAwCCQsqlwbnjy5fVQXKM=;
	h=Date:Subject:To:References:From:In-Reply-To;
	b=BBGjxc5BwBhZx+AJAHLC3Zvn1p/1oqIalQ1yzC5VCuJE0IwkVEzdOU3oFIK7CigAh
	 EJA+tGHxMxpeCxtIBX/QA7nBVDtFHLQZn+W/3vmZ6izrDbR6iPZZHFKHxXG3w1Gn2s
	 Mm9a8ho+sZbM1SidbdYec8BKVArvLvY7FIiBVaXwT6jZSghs945sdcomIK8gd
Original-Subject: Re: bug#774: traceroute: Exit code is not reliable nor documented
Author: Alessandro Vesely <[email protected]>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111])
  (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3,128bits,ECDHE_RSA_AES_128_GCM_SHA256)
  by wmail.tana.it with ESMTPSA
  id 00000000005DC0D8.0000000064DFB71C.000048B4; Fri, 18 Aug 2023 20:23:24 +0200
Message-ID: <[email protected]>
Date: Fri, 18 Aug 2023 20:23:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: bug#774: traceroute: Exit code is not reliable nor documented
Content-Language: en-US, it-IT
To: Mark Hindley <[email protected]>, [email protected]
References: <169234611173.22998.13478232296979279263.reportbug@north.ext.tana.it>
 <[email protected]>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <[email protected]>
In-Reply-To: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On Fri 18/Aug/2023 19:04:30 +0200 Mark Hindley wrote:
> Control: tags -1 debian
> 
> Alessandro
> 
> On Fri, Aug 18, 2023 at 10:08:31AM +0200, Alessandro Vesely wrote:
>> Package: traceroute
>> Version: 1:2.1.0-2+deb11u1
>> Severity: grave
>> Justification: renders package unusable
> 
> Thanks for this. However, traceroute is not a forked package and Devuan uses
> Debian's packages directly without recompilation. Please report this to Debian's
> BTS to be addressed.


Hm... I used reportbug.  Now I repeated the same using --bts=debian.  Wouldn't 
it have been possible to just forward the message somewhere?

Best
Ale
Acknowledgement sent to Alessandro Vesely <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.
Information forwarded to [email protected], [email protected]:
bug#774; Package traceroute. Full text available.
Added tag(s) debian. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Message received at [email protected]:


Received: (at 774) by bugs.devuan.org; 18 Aug 2023 17:06:01 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2a01:4f8:140:32a1::58c6:6473]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 18 Aug 2023 17:06:01 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id HpCtAKWk32TqFAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 18 Aug 2023 17:04:37 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id E37705F5; Fri, 18 Aug 2023 17:04:36 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id CA6B327
	for <[email protected]>; Fri, 18 Aug 2023 17:04:31 +0000 (UTC)
Received: from hindley.org.uk (apollo.hindleynet [192.168.1.3])
	by mx.hindley.org.uk (Postfix) with SMTP id B92E8E0D;
	Fri, 18 Aug 2023 18:04:30 +0100 (BST)
Received: (nullmailer pid 32226 invoked by uid 1000);
	Fri, 18 Aug 2023 17:04:30 -0000
Date: Fri, 18 Aug 2023 18:04:30 +0100
From: Mark Hindley <[email protected]>
To: Alessandro Vesely <[email protected]>, [email protected]
Subject: Re: bug#774: traceroute: Exit code is not reliable nor documented
Message-ID: <[email protected]>
References: <169234611173.22998.13478232296979279263.reportbug@north.ext.tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <169234611173.22998.13478232296979279263.reportbug@north.ext.tana.it>
X-Debbugs-No-Ack: No Thanks

Control: tags -1 debian

Alessandro

On Fri, Aug 18, 2023 at 10:08:31AM +0200, Alessandro Vesely wrote:
> Package: traceroute
> Version: 1:2.1.0-2+deb11u1
> Severity: grave
> Justification: renders package unusable

Thanks for this. However, traceroute is not a forked package and Devuan uses
Debian's packages directly without recompilation. Please report this to Debian's
BTS to be addressed.

Thanks

Mark
Information forwarded to [email protected], [email protected]:
bug#774; Package traceroute. Full text available.

Message received at [email protected]:


Received: (at submit) by bugs.devuan.org; 18 Aug 2023 08:09:02 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2a01:4f8:140:32a1::58c6:6473]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 18 Aug 2023 08:09:02 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 4NGEHggn32SRdAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 18 Aug 2023 08:08:40 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 603D35F5; Fri, 18 Aug 2023 08:08:40 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS
	autolearn=ham autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=94.198.96.74; helo=wmail.tana.it; [email protected]; receiver=<UNKNOWN> 
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74])
	by email.devuan.org (Postfix) with ESMTPS id EB82127
	for <[email protected]>; Fri, 18 Aug 2023 08:08:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
  (uid 1000)
  by wmail.tana.it with local
  id 00000000005DC0E9.0000000064DF26FF.00005E40; Fri, 18 Aug 2023 10:08:31 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Alessandro Vesely <[email protected]>
To: Devuan Bug Tracking System <[email protected]>
Subject: traceroute: Exit code is not reliable nor documented
Message-ID: <169234611173.22998.13478232296979279263.reportbug@north.ext.tana.it>
X-Mailer: reportbug 7.10.3+devuan1
Date: Fri, 18 Aug 2023 10:08:31 +0200

Package: traceroute
Version: 1:2.1.0-2+deb11u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've been using traceroute to monitor network state of the server.
It is called for each interface by a cron job running a few times per hour.
Since yesterday, an interface stopped working, but the job never noticed it.
Manually calling traceroute only shows the (natted) modem interface:

:~# ip addr show eth1r
3: eth1r: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:26:55:e0:d0:e8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1r
       valid_lft forever preferred_lft forever
    inet6 fe80::226:55ff:fee0:d0e8/64 scope link 
       valid_lft forever preferred_lft forever

:~# traceroute -4 -n -i eth1r -m 4 -s 192.168.1.254 185.204.135.186
traceroute to 185.204.135.186 (185.204.135.186), 4 hops max, 60 byte packets
 1  192.168.1.1  0.235 ms  0.282 ms  0.289 ms
 2  * * *
 3  * * *
 4  * * *

Exit code is 0.  In fact recvmsg reports no error.  The relevant calls are:
23495 sendto(14, "@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_", 32, 0, NULL, 0) = 32
23495 recvmsg(3, {msg_name={sa_family=AF_INET, sin_port=htons(33434), sin_addr=inet_addr("185.204.135.186")}, msg_namelen=28->16, msg_iov=[{iov_base="@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_", iov_len=1280}], msg_iovlen=1, msg_control=[{cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=SO_TIMESTAMP_OLD, cmsg_data={tv_sec=1692345052, tv_usec=96190}}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, cmsg_data=[64]}, {cmsg_len=48, cmsg_level=SOL_IP, cmsg_type=IP_RECVERR, cmsg_data={ee_errno=113, ee_origin=2, ee_type=11, ee_code=0, ee_info=0, ee_data=0, offender={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.1.1")}}}], msg_controllen=104, msg_flags=MSG_ERRQUEUE}, MSG_ERRQUEUE) = 32
23495 recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(33435), sin_addr=inet_addr("185.204.135.186")}, msg_namelen=28->16, msg_iov=[{iov_base="@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_", iov_len=1280}], msg_iovlen=1, msg_control=[{cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=SO_TIMESTAMP_OLD, cmsg_data={tv_sec=1692345052, tv_usec=96276}}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, cmsg_data=[64]}, {cmsg_len=48, cmsg_level=SOL_IP, cmsg_type=IP_RECVERR, cmsg_data={ee_errno=113, ee_origin=2, ee_type=11, ee_code=0, ee_info=0, ee_data=0, offender={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.1.1")}}}], msg_controllen=104, msg_flags=MSG_ERRQUEUE}, MSG_ERRQUEUE) = 32
23495 recvmsg(5, {msg_name={sa_family=AF_INET, sin_port=htons(33436), sin_addr=inet_addr("185.204.135.186")}, msg_namelen=28->16, msg_iov=[{iov_base="@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_", iov_len=1280}], msg_iovlen=1, msg_control=[{cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=SO_TIMESTAMP_OLD, cmsg_data={tv_sec=1692345052, tv_usec=96277}}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, cmsg_data=[64]}, {cmsg_len=48, cmsg_level=SOL_IP, cmsg_type=IP_RECVERR, cmsg_data={ee_errno=113, ee_origin=2, ee_type=11, ee_code=0, ee_info=0, ee_data=0, offender={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.1.1")}}}], msg_controllen=104, msg_flags=MSG_ERRQUEUE}, MSG_ERRQUEUE) = 32
23495 +++ exited with 0 +++

The modem obviously needs a reset.  The point is that I was expecting
traceroute to detect that, since the interface doesn't work.  If this
is not a bug in the code, it is in the documentation, tagged 11 October
2006, which doesn't mention exit code at all.


Thanks
Ale


-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 4 (chimaera)
Release:	4
Codename:	chimaera
Architecture: x86_64

Kernel: Linux 5.10.0-24-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages traceroute depends on:
ii  libc6  2.31-13+deb11u6

traceroute recommends no packages.

traceroute suggests no packages.

-- no debconf information
Acknowledgement sent to Alessandro Vesely <[email protected]>:
New bug report received and forwarded. Copy sent to [email protected]. Full text available.
Report forwarded to [email protected], [email protected]:
bug#774; Package traceroute. Full text available.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <[email protected]>.
Last modified: Sat, 30 Nov 2024 22:39:01 UTC