<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Repeated Syslog Entry from XMC in General Network Management</title>
    <link>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81728#M139</link>
    <description>A general web search suggests that this behavior is expected whenever the snmpd (daemon) source /proc/mounts and encounters a path it can not find or access. In this case - an access issue.&lt;BR /&gt;&lt;BR /&gt;https://wiki.opennms.org/wiki/SNMP_spams_my_log is a reference point.&lt;BR /&gt;&lt;BR /&gt;This suggests one workaround - to filter out this particular message - which I've tested and indeed does appear to work.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The /sys/kernel/debug/tracing sub-directory is owned by 'root' and snmpd is run as a separate user Debian-snmp.&lt;BR /&gt;&lt;BR /&gt;drwx------ 8 root root 0 Sep 22 10:55 tracing/&lt;BR /&gt;&lt;BR /&gt;So changing this path (unknown consequences) using 'chmod 755 tracing' to allow non-root users access appears to also suppress / prevent snmpd from logging this issue.&lt;BR /&gt;&lt;BR /&gt;drwxr-xr-x 8 root root 0 Sep 22 10:55 tracing/&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I would opt for filtering versus changing path permissions.</description>
    <pubDate>Tue, 12 Oct 2021 19:57:32 GMT</pubDate>
    <dc:creator>Robert_Haynes</dc:creator>
    <dc:date>2021-10-12T19:57:32Z</dc:date>
    <item>
      <title>Repeated Syslog Entry from XMC</title>
      <link>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81727#M138</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The syslog in my XMC is constantly getting the following entry:&lt;/P&gt;&lt;P&gt;“snmpd[2703]: Cannot statfs /sys/kernel/debug/tracing: Permission denied”&lt;/P&gt;&lt;P&gt;the source is the XMC itself.&lt;/P&gt;&lt;P&gt;We are running version 8.5.6.17&lt;/P&gt;&lt;P&gt;This entry is new and I think it started after the upgrade to 8.5.6.17&lt;/P&gt;&lt;P&gt;Does anyone know how to correct this?&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;</description>
      <pubDate>Fri, 10 Sep 2021 22:31:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81727#M138</guid>
      <dc:creator>Christopher_Tay</dc:creator>
      <dc:date>2021-09-10T22:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: Repeated Syslog Entry from XMC</title>
      <link>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81728#M139</link>
      <description>A general web search suggests that this behavior is expected whenever the snmpd (daemon) source /proc/mounts and encounters a path it can not find or access. In this case - an access issue.&lt;BR /&gt;&lt;BR /&gt;https://wiki.opennms.org/wiki/SNMP_spams_my_log is a reference point.&lt;BR /&gt;&lt;BR /&gt;This suggests one workaround - to filter out this particular message - which I've tested and indeed does appear to work.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The /sys/kernel/debug/tracing sub-directory is owned by 'root' and snmpd is run as a separate user Debian-snmp.&lt;BR /&gt;&lt;BR /&gt;drwx------ 8 root root 0 Sep 22 10:55 tracing/&lt;BR /&gt;&lt;BR /&gt;So changing this path (unknown consequences) using 'chmod 755 tracing' to allow non-root users access appears to also suppress / prevent snmpd from logging this issue.&lt;BR /&gt;&lt;BR /&gt;drwxr-xr-x 8 root root 0 Sep 22 10:55 tracing/&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I would opt for filtering versus changing path permissions.</description>
      <pubDate>Tue, 12 Oct 2021 19:57:32 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81728#M139</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2021-10-12T19:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: Repeated Syslog Entry from XMC</title>
      <link>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81729#M140</link>
      <description>We are currently reviewing this behavior.&lt;BR /&gt;&lt;BR /&gt;The debugfs and tracefs mounts are active in Ubuntu OS when this particular event is logged. Simply typing 'umount tracefs' will temporarily resolve it. Ultimately filtering out such a message if it continues to re-appear periodically may be the workaround / solution here.</description>
      <pubDate>Wed, 13 Oct 2021 15:10:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/general-network-management/repeated-syslog-entry-from-xmc/m-p/81729#M140</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2021-10-13T15:10:57Z</dc:date>
    </item>
  </channel>
</rss>

