I don't know.  Perhaps the file was modified by your mail reader?

The file patches fine here.  If you feel adventurous, patch it by hand.

-Eric

Fritz wrote:
yes 64 bit, i've tried it and it gives me this :

[EMAIL PROTECTED]:~/zenoss-0.22.1> make pysnmp-install
unpacking pysnmp-3.4.3 in build/
patching file pysnmp/proto/rfc1155.py
patching file pysnmp/proto/rfc1155.py
patch: **** malformed patch at line 4: return '%d.%d.%d.%d' % (ord(value[0]), ord(value[1])

the same line is also used in patch01 in 0.22.1, wich doesnt generate any errors. so i'm puzzled as to why it wont apply the patch. i tried removing the first patch pysnmp-3.4.3.patch01, but that didnt solve the problem. this probably a simple thing i'm overlooking here, but what did i miss?




On Tuesday 08 August 2006 15:40, Eric Newton wrote:
Is 192.168.20.165 a 64-bit machine, by any chance?  If so, you may be
interested in the attached patch

    $ cd zenossinst
    $ cp patch-from-eric.patch externallibs/pysnmp-3.4.3.patch02
    $ rm -rf build/pysnmp-3.4.3
    $ make pysnmp-install

Some machines appear to be sending out 64-bit IP addresses.  The patch
accomodates that.

-Eric

Fritz wrote:
WARNING:twsnmp.protocol:Bad response from ('192.168.20.165', 161):
'05\x02\x01\x00\x04\x06public\xa2
(\x02\x02\x03\x11\x02\x01\x00\x02\x01\x000\x1c0\x1a\x06\x0e+\x06\x01\x02\
[EMAIL PROTECTED]'

i keep receiving this error when collecting snmp data. is this a badly
setup snmp daemon or is it a parsing bug?


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to