Bug 1275730 - snmpd repeatedly logs errors for "Cannot statfs net:[###...#]"
Summary: snmpd repeatedly logs errors for "Cannot statfs net:[###...#]"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Vinay Kapalavai
QA Contact: Nataf Sharabi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-27 15:10 UTC by Peter Portante
Modified: 2019-03-18 13:03 UTC (History)
19 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180804083746.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-18 13:03:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0446 0 None None None 2019-03-18 13:03:18 UTC

Description Peter Portante 2015-10-27 15:10:23 UTC
Looks snmpd periodically logs errors of the form:

  Cannot statfs net:[4026532907]#012: No such file or directory

This seems to be caused by these two mount entries:

  proc on /run/netns/qdhcp-f90899a0-dc73-45c6-9889-80473cf67336 type proc (rw,nosuid,nodev,noexec,relatime)
  proc on /run/netns/qdhcp-f90899a0-dc73-45c6-9889-80473cf67336 type proc (rw,nosuid,nodev,noexec,relatime)

If one runs "snmpd -D -Lo -f > /tmp/snmpd.debug.log 2>&1", killing it after about 10 seconds (be patient, it does not take ctrl-c right away), you find in the log entries like:

  trace: _fsys_type(): hardware/fsys/fsys_mntent.c, 73:
  fsys:type: Classifying proc
  Cannot statfs net:[4026532907]
  : No such file or directory
  trace: netsnmp_fsys_by_path(): hardware/fsys/hw_fsys.c, 154:
  fsys:path: Get filesystem entry (net:[4026532907])

These seem to match up with the two mount entries.

Comment 2 Peter Portante 2015-10-27 16:02:49 UTC
The reason this is filed against the OSP director is that my RHEL 7.1 host was installed a running with SNMPD prior to the openstack install.

After running, "openstack undercloud install", SNMPD was started and the error messages begin.

Comment 9 Hugh Brock 2016-03-21 11:33:47 UTC
This has missed 8.0 -- I'm moving it to 9.0 and assigning it to the default owner (Angus)

Comment 12 Ben Nemec 2017-03-09 23:30:02 UTC
This seems like a fairly cosmetic issue.  Is it causing any functional issues?

Comment 13 Peter Portante 2017-03-10 03:49:34 UTC
It does not appear to be a functional issue.  But neither is it cosmetic, since depending on the configuration, you can see lots of these logs logged by snmpd at an error level.

This affects common logging efforts, as the more noise our products emit, the harder it is to wade through that noise to find real errors.

Adding Tushar to comment.

Comment 25 Lon Hohberger 2019-01-15 19:35:15 UTC
According to our records, this should be resolved by openstack-tripleo-heat-templates-9.0.1-0.20181013060908.el7ost.  This build is available now.

Comment 28 Nataf Sharabi 2019-02-19 11:24:14 UTC
Couldn't reproduce the original bug.


Not via manual run (snmpd -D -Lo TCP:1161 > /tmp/snmpd.debug.log1 2>&1)

Or via systemctl start snmpd

Comment 30 errata-xmlrpc 2019-03-18 13:03:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0446


Note You need to log in before you can comment on or make changes to this bug.