On a i386 CentOS system this is fine, but only x86_64 system has the problem. My guess is the netSNMP library was compiled with i386 only. For the short term I created a wrapper monitor for the freespace.monitor that discards stderr.
On Nov 29, 2006, at 8:53 PM, Ed Ravin wrote: > Did you upgrade or downgrade the net-snmp libraries? Googling for > "No log handling enabled - turning on stderr logging" suggests that > there is a Perl / NetSNMP library mismatch. > > Another possibility is that someone installed another copy of net-snmp > / ucd-snmp in a directory in the library path, or the library path > was changed and points to the wrong place. > > On Wed, Nov 29, 2006 at 09:35:27AM -0700, Jeff Montagna wrote: >> Anyone have an idea of why logging would suddenly be disabled? >> netsnmp-freespace.monitor was working fine yesterday then broke >> today. >> >> [EMAIL PROTECTED]:mon.d$ ./netsnmp-freespace.monitor sts1 >> No log handling enabled - turning on stderr logging >> truncating integer value to 32 bits >> truncating integer value to 32 bits >> truncating integer value to 32 bits >> [EMAIL PROTECTED]:mon.d$ ./netsnmp-freespace.monitor ltxnic7 >> No log handling enabled - turning on stderr logging >> truncating integer value to 32 bits >> ltxnic7 >> >> ltxnic7:/(/dev/dsk/c0t0d0s0) total=7468 used=6002(89%) free=718 >> err=/: less than 900000 free (= 736195) _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
