I was having a similar problem with a Communigate MIB recently. I found using "smilint" on the offending MIB provided most of the insight I needed. In general, the biggest issue I saw were improper use of initial capitalization in statements, where they were not allowed by the SMI RFC. (I also ran it through dos2unix to make things easier.)
Afterwards, simply running the smidump command manually from the command line made sure that the output would be clean, before setting Zenoss loose on it. On Mon, 2007-09-24 at 14:44 +0000, gogo79 wrote: > Hi, > the result is the same: > smidump -fpython -p "/opt/zenoss/share/mibs/ietf/RFC1155-SMI" -p > "/opt/zenoss/share/mibs/ietf/RFC-1212" -p > "/opt/zenoss/share/mibs/ietf/RFC1158-MIB" -p > "/opt/zenoss/share/mibs/ietf/RFC1213-MIB" -p > "/opt/zenoss/share/mibs/site/ONSTOR-NASGW-MIB.TXT" > "/opt/zenoss/share/mibs/site/ONSTOR-CIFS-MIB.TXT" > > Segmentation fault > > Best Regards > > ------------------------ > Georgi Georgiev > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://community.zenoss.com/forums/viewtopic.php?p=11012#11012 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users -- James D. Roman IT Network Administration Terranet Inc.On contract to: Science Systems and Applications, Inc. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
