Debian Bug report logs - #120166
iputils-ping: ping complains "kernel is not very fresh, upgrade is recommended" on latest kernel

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Alex Walker <alex@x3ja.co.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: iputils-ping: ping complains "kernel is not very fresh, upgrade is recommended" on latest kernel

Date: Mon, 19 Nov 2001 05:01:57 +0000

Package: iputils-ping
Version: 3:0ss010824-1
Severity: normal

When pinging hosts with errors (host unreachable, no route to host) ping gives the error "WARNING: kernel is not very fresh, upgrade is recommended" even on the latest development kernels.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux numbers 2.4.15-pre4-xfs #4 Thu Nov 15 02:13:39 GMT 2001 i686
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages iputils-ping depends on:
hi  libc6                         2.2.4-4    GNU C Library: Shared libraries an

Message #10 received at 120166@bugs.debian.org (full text, mbox, reply):

From: Matt Zimmerman <mdz@debian.org>

To: 120166@bugs.debian.org

Subject: Kernel not very fresh

Date: Fri, 18 Jan 2002 16:08:03 -0500

This happens to me as well.  It looks like it is actually intentional:

                                                static int once;
                                                if (!once) {
                                                        fprintf(stderr,
"\rWARNI
NG: kernel is not very fresh, upgrade is recommended.\n");
                                                        once = 1;
                                                }

So this will happen whenever ping gets more than one ICMP_PARAMETERPROB that
is neither a redirect nor a source quench.  So is the kernel supposed to
only send one?  That doesn't seem like the usual behaviour...

-- 
 - mdz

Message #15 received at 120166@bugs.debian.org (full text, mbox, reply):

From: Tuomas Heino <iheino@cc.hut.fi>

To: 120166@bugs.debian.org

Subject: Kernel not very fresh, arp

Date: Wed, 30 Jan 2002 22:15:42 +0200

Seems to also happen whenever arp resolution fails
(when you ping any localnet host that doesn't exist).
and yes, this is using 2.[45].* kernels...

Message #20 received at 120166@bugs.debian.org (full text, mbox, reply):

From: Tuomas Heino <iheino@cc.hut.fi>

To: 120166@bugs.debian.org

Subject: Kernel not very fresh, arp strace

Date: Wed, 30 Jan 2002 23:02:21 +0200

Just in case anyone has been wondering what 2.4.xx kernels actually tell
ping to cause this message (pinging an unplugged local host):

# strace -te recvmsg ping -c 2 -w 5 xxx.yyy.19.215
PING xxx.yyy.19.215 (xxx.yyy.19.215) from xxx.yyy.19.119 : 56(84) bytes of data.
22:55:18 recvmsg(3, 0xbfffeac0, 0)      = -1 EAGAIN (Resource temporarily unavailable)
22:55:19 recvmsg(3, 0xbfffeac0, 0)      = -1 EAGAIN (Resource temporarily unavailable)
22:55:20 recvmsg(3, {msg_name(16)={sin_family=AF_INET, sin_port=htons(10176), sin_addr=inet_addr("xxx.yyy.19.119")}}, msg_iov(1)=[{"E\300\0pM\237\0\0\377\1@m\202\351\23w\202\351\23w\3\1\374"..., 192}], msg_controllen=20, msg_control=0xbfffeadc, , msg_flags=0}, 0) = 112
WARNING: kernel is not very fresh, upgrade is recommended.
From xxx.yyy.19.119: icmp_seq=1 Destination Host Unreachable
22:55:21 recvmsg(3, 0xbfffeac0, MSG_DONTWAIT) = -1 EHOSTUNREACH (No route to host)
22:55:21 recvmsg(3, {msg_name(16)={sin_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("xxx.yyy.19.215")}}, msg_iov(1)=[{"\10\0\232\230\331c\1\0", 8}], msg_controllen=64, msg_control=0xbfffe85c, , msg_flags=MSG_TRUNC|MSG_ERRQUEUE}, MSG_ERRQUEUE|MSG_DONTWAIT) = 8
From xxx.yyy.19.119 icmp_seq=1 Destination Host Unreachable
22:55:21 recvmsg(3, 0xbfffeac0, MSG_DONTWAIT) = -1 EHOSTUNREACH (No route to host)
22:55:21 recvmsg(3, {msg_name(16)={sin_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("xxx.yyy.19.215")}}, msg_iov(1)=[{"\10\0\313Q\331c\2\0", 8}], msg_controllen=64, msg_control=0xbfffe85c, , msg_flags=MSG_TRUNC|MSG_ERRQUEUE}, MSG_ERRQUEUE|MSG_DONTWAIT) = 8
From xxx.yyy.19.119 icmp_seq=2 Destination Host Unreachable
22:55:21 recvmsg(3, 0xbfffeac0, MSG_DONTWAIT) = -1 EHOSTUNREACH (No route to host)
22:55:21 recvmsg(3, {msg_name(16)={sin_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("xxx.yyy.19.215")}}, msg_iov(1)=[{"\10\0\260P\331c\3\0", 8}], msg_controllen=64, msg_control=0xbfffe85c, , msg_flags=MSG_TRUNC|MSG_ERRQUEUE}, MSG_ERRQUEUE|MSG_DONTWAIT) = 8
From xxx.yyy.19.119 icmp_seq=3 Destination Host Unreachable

--- xxx.yyy.19.215 ping statistics ---
3 packets transmitted, 0 received, +4 errors, 100% loss, time 2018ms
, pipe 3

Message #25 received at 120166@bugs.debian.org (full text, mbox, reply):

From: "Noah L. Meyerhans" <frodo@morgul.net>

To: Tuomas Heino <iheino@cc.hut.fi>, 120166@bugs.debian.org

Subject: Re: Bug#120166: Kernel not very fresh, arp strace

Date: Wed, 30 Jan 2002 16:08:42 -0500

On Wed, Jan 30, 2002 at 11:02:21PM +0200, Tuomas Heino wrote:
> Just in case anyone has been wondering what 2.4.xx kernels actually tell
> ping to cause this message (pinging an unplugged local host):
> 

The particularly odd thing is that I don't see this message on *any* of
the machines I test!  This includes 2.4.7, 2.4.9, 2.4.13, 2.4.17, and
maybe one or two others.  This also includes SPARC, PPC, and MIPS
architectures.  I simply cannot get ping to give me the error message
about the kernel being unfresh.

I am actually considering disabling that message completely in the next
iputils-ping upload (today, maybe tomorrow).  It doesn't actually serve
a purpose, aside from annoying the user, and it doesn't even seem
consistant in when it gets triggerred.

Unless anybody objects, I think I will upload a version with that
message disabled.  If anything breaks, I'm sure I can count on my users
to inform me, since I can't seem to duplicate their complaints.  ;^)

noah

-- 
 _______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 

Message #30 received at 120166@bugs.debian.org (full text, mbox, reply):

From: "Noah L. Meyerhans" <frodo@morgul.net>

To: Tuomas Heino <iheino@cc.hut.fi>

Cc: 120166@bugs.debian.org

Subject: Re: Bug#120166: Kernel not very fresh, arp strace

Date: Wed, 30 Jan 2002 16:32:26 -0500

On Wed, Jan 30, 2002 at 11:12:46PM +0200, Tuomas Heino wrote:
> 
> Hmm... if you try a strace w/ those parameters, does it look like mine or
> are some of those recvmsg's missing?
> 

Actually, it turns out that I am wrong.  Adding the flags to make ping
exit automatically causes me to see that warning.  If I run ping without
the -c flag, I never get the message.  I suspect you probably see the
same behavior.

However, the latest iputils snapshot, which is just about ready for
upload, has slightly re-worked logic to determine when to display the
warning.

I will upload the new package and mark this bug as closed.  Please let
me know if you still see the warning.

noah

-- 
 _______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 

Message #35 received at 120166-close@bugs.debian.org (full text, mbox, reply):

From: Noah Meyerhans <noahm@debian.org>

To: 120166-close@bugs.debian.org

Subject: Bug#120166: fixed in iputils 3:20020124-1

Date: Thu, 31 Jan 2002 15:00:33 -0500

We believe that the bug you reported is fixed in the latest version of
iputils, which has been installed in the Debian FTP archive:

iputils-arping_20020124-1_i386.deb
  to pool/main/i/iputils/iputils-arping_20020124-1_i386.deb
iputils-ping_20020124-1_i386.deb
  to pool/main/i/iputils/iputils-ping_20020124-1_i386.deb
iputils-tracepath_20020124-1_i386.deb
  to pool/main/i/iputils/iputils-tracepath_20020124-1_i386.deb
iputils_20020124-1.diff.gz
  to pool/main/i/iputils/iputils_20020124-1.diff.gz
iputils_20020124-1.dsc
  to pool/main/i/iputils/iputils_20020124-1.dsc
iputils_20020124.orig.tar.gz
  to pool/main/i/iputils/iputils_20020124.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 120166@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Noah Meyerhans <noahm@debian.org> (supplier of updated iputils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 29 Jan 2002 16:32:58 -0500
Source: iputils
Binary: iputils-tracepath iputils-ping iputils-arping
Architecture: source i386
Version: 3:20020124-1
Distribution: unstable
Urgency: low
Maintainer: Noah Meyerhans <noahm@debian.org>
Changed-By: Noah Meyerhans <noahm@debian.org>
Description: 
 iputils-arping - Send ICMP echo requests to an ARP address
 iputils-ping - The ping utility from iputils
 iputils-tracepath - The tracepath utility from iputils
Closes: 119651 120166
Changes: 
 iputils (3:20020124-1) unstable; urgency=low
 .
   * New upstream release. (Closes: Bug#119651, Bug#120166)
   * Improved the build process.  Uses new debhelper scripts.
   * Added new build deps for manpage auto-generation from SGML source.
Files: 
 f32d585b6ea1d80434d943ea6c1e5108 674 net extra iputils_20020124-1.dsc
 ffd6d1e33c88e29cca5198859106cc62 120292 net extra iputils_20020124.orig.tar.gz
 8c2ceb3cebedd25319a640b656dfa1ff 391 net extra iputils_20020124-1.diff.gz
 c0dc6ffe2ade7bcf3fbc63113e313963 36910 net extra iputils-ping_20020124-1_i386.deb
 211ef7f19f616b75093b0efda5c9175b 22192 net extra iputils-tracepath_20020124-1_i386.deb
 e3bf131b707f9f2ca5de6827550ed556 16056 net extra iputils-arping_20020124-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8WGq6YrVLjBFATsMRAkVZAJ9NO/pVwbgHtvBT0iIW4uxbFvFTBgCeKdPL
TMGM/gznU/tj0ejmZZB7+hQ=
=n/aO
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.