[Bug 1847377] Re: snmptrapd.service uses MIBSDIRS instead of MIBDIRS

2019-10-10 Thread a1291762
I noticed this while trying to add a directory to the list (custom
MIBs).

The snmp-mibs-downloader package populates the directories in the list.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847377

Title:
  snmptrapd.service uses MIBSDIRS instead of MIBDIRS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1847377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847377] Re: snmptrapd.service uses MIBSDIRS instead of MIBDIRS

2019-10-09 Thread Bryce Harrington
Yes, it does appear to be a typo, you're right.  Grepping the source
tree shows "MIBSDIR" only appears in ./debian/snmptrapd.service and
./debian/snmpd.service, whereas "MIBDIRS" shows up 144 times in the main
source tree.

The issue appears to be present in both bionic (5.7.3+dfsg-1.8ubuntu3)
and eoan (5.7.3+dfsg-5ubuntu5).  Looks like it should probably also
affect xenial and disco.

I notice, however, that none of these mibs directories actually exist,
at least not with just snmptrapd installed (are there any packages that
install mibs to any of these dirs?)  The service itself seems to
function identically with the typo'd env var and with the fixed one.
I.e.:

$ sudo apt-get install -y snmptrapd
$ service snmptrapd status

● snmptrapd.service - Simple Network Management Protocol (SNMP) Trap Daemon.
   Loaded: loaded (/lib/systemd/system/snmptrapd.service; disabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2019-10-09 22:21:50 UTC; 7s ago
 Main PID: 2276 (snmptrapd)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/snmptrapd.service
   └─2276 /usr/sbin/snmptrapd -Lsd -f

Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laConfig ::= { laEntry 4 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laLoad ::= { laEntry 3 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laNames ::= { laEntry 2 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Cannot adopt OID in 
UCD-SNMP-MIB: laIndex ::= { laEntry 1 }
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: NET-SNMP version 5.7.3 AgentX 
subagent connected
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: Warning: no access control 
information configured.
 (Config search path: 
/etc/snmp:/usr/share/snmp:/usr/lib/x86_64-linux-gnu/snmp)
   This receiver will *NOT* accept 
any incoming notifications.
Oct 09 22:21:51 triage-bionic snmptrapd[2276]: NET-SNMP version 5.7.3

By chance, did you discover this error by it causing an actual issue for
you?  If so, it'd help in SRUing this to know more about how you
triggered it and what the impact was.

Meanwhile, I believe you can use 'reportbug --bts debian' to force
reporting the error to debian.  You can include a link to this bug
report (and please let us know the debian bug report so we can link to
it from here).

** Changed in: net-snmp (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847377

Title:
  snmptrapd.service uses MIBSDIRS instead of MIBDIRS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1847377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs