Bug 663665
| Summary: | kernel: process `cp' is using deprecated sysctl (syscall) net.ipv6.neigh.virbr0.base_reachable_time | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | David Kovalsky <dkovalsk> |
| Component: | sos | Assignee: | Adam Stokes <astokes> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.5 | CC: | agk, benl, bmr, gavin, kdudka, meyering, prc, zzhou |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-01-14 16:52:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Kovalsky
2010-12-16 14:48:59 UTC
Is that kernel-xen machine or bare metal? Please add your kernel version. gettimeofday() was reported to be causing this kind of messages on kernel-xen machine in https://bugzilla.redhat.com/show_bug.cgi?id=461640 ... so probably the issue is still there. Anyway it is likely something under the coreutils, as we are not directly calling this syscall there. Ondrej, bare metal. Kernel version I've seen this with is (was) 2.6.18-194.11.1.el5 Is that reproducible? Could you please provide more clean reproducer (cp parameters you have used)? I can't reproduce that (although I haven't tried sosreport, just ordinary file, to be honest)... It may be random, I admit that I don't boot RHEL5 on my notebook that often :-) What I did was: - boot to runlevel 5 - CTRL + ALT + F1 - login as root - sosreport - cp /tmp/sosreport-dkovalsky-943010-223510.tar.bz2 /home/test/ Now that I'm checking fstab on RHEL5 root I've noticed that I've mislead you, /tmp is not tmpfs and home is actually ext4. Sorry about that, I got a couple of bugs mixed up. Fstab: /dev/vg_kovinek/root_1 / ext3 noatime,nodiratime 1 1 LABEL=/boot /boot ext2 noatime,nodiratime 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/mapper/cryptoswap_1 swap swap defaults 0 0 /dev/mapper/cryptohome /home ext4 noatime,nodiratime 1 2 Perhaps it's related to NetworkManager and the fact that I didn't login into GUI to finish networking setup (?). I wasn't connected to wired network when I tried. Let me try to isolate a clear reproducer. Ha, Ondrej, I do have a clear reproducer. It's not related to the cp I did from /tmp/, but it's triggered on by sosreport. What I did: screen tail -f -n0 /var/log/messages CTRL+A CTRL+C to open another window sosreport CTRL+A 0 and watch the message appear Dec 17 09:52:01 x86-64-5s-m1 kernel: process `cp' is using deprecated sysctl (syscall) net.ipv6.neigh.virbr0.base_reachable_time; Use net.ipv6.neigh.virbr0.base_reachable_time_ms instead. sos-1.7-9.49.el5.noarch The warning comes from sos itself:
# grep proc /usr/lib/python2.4/site-packages/sos/plugins/system.py
self.addCopySpec("/proc/sys")
While traversing /proc/sys, it encounters /proc/sys/net/ipv6/neigh/eth0/base_reachable_time and triggers the warning. It's, however, completely harmless. If the kernel does not provide base_reachable_time, it will still work fine (and even better as there will be no warning).
From my point of view, it's _not_ a bug.
Closing NOTABUG; so long as the kernel supports the deprecated sysctls anything that walks /proc/sys can trigger this problem. Not specific to sos. See comment #8 *** Bug 676264 has been marked as a duplicate of this bug. *** |