Hei hei, I'm having problems finding explanations and best practices for stuff stored in the mib_indexes folder in the persistent storage area of net-snmp 5.7. Maybe I just describe what happens on the machine making problems, all with net-snmp 5.7.2 and 5.7.2.1:
Image a system with a root filesystem and a separate filesystem for persistant storage. There's a set of certain MIBs in the root filesystem. On calling any net-snmp related tool the mib_indexes folder is created somewhere in the persistent filesystem and two index files 0 and 1 are created. As far as I can see those contain a two columns, first is the name of a MIB and second the filename. On top is a directory where those files are found. It's not clear to me, when net-snmp uses this and what for. Now this is an embedded platform and you can update the root filesystem with a newer one. In one of those updates a MIB file was renamed, so it basically contains the same MIB, but with a different filename. snmpd runs as root and all relevant files and folders are writable by root. Additionally I have named OIDs in /etc/snmpd.conf so when starting snmpd tries to translate them to numeric ones. What I see in syslog now on start is snmpd tries to load the old MIB file which obviously fails. The only reference to the old file is in those indexes in the mib_indexes folder. I tried deleting those mib_indexes folder while snmpd was not running. After restarting snmpd the folder was there again with different, updated index files and snmpd started fine. I also tried updates from different versions of our root filesystem to different other versions of our root filesystem, all with the above mentioned net-snmp versions. Sometimes there is actually an automatic update of those indexes happening, sometimes not and I have no clue why up to now. What is the right way to update those index files. When does net-snmp do this by itself? Can I safely delete those files on system reboot? Why are those placed in the persistent net-snmp folder then? Or what should I do when renaming things in /usr/share/snmp/mibs to prevent errors like this? And finally another question, according to syslog: Jan 15 14:18:39 inblox-c00 daemon.err snmpd[606]: MIB search path: //.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/ There are two index files 0 and 1, is that because I set the following in /etc/snmp/snmp.conf? mibdirs +/usr/share/snmp/mibs/ Can this double defined folder lead to any problems? Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
