search for: asn

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but it's a thing I have to deal with...

...f while the other two are configured with SNMPv1. It doesn't matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all work individually (see below example). However, if I configure any two or all three of them to use SNMPv3 then on startup upsdrvctl complains about "unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.3" and fails to start. My current [redacted] ups.conf follows. The only differences between the values are on the port and desc lines (ignoring #, of course). [ups1] desc = "APC Smart-UPS 5000 SNMP in rack 1 - AP9617"...

...nating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected NETYS RT 1/1 UPS on host 192.168.14.10 (mib: ietf 1.4) [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.3.0 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.6.0 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.4.1 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.5.1 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.4.4....

...nating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected NETYS RT 1/1 UPS on host 192.168.14.10 (mib: ietf 1.4) [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.3.0 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.6.0 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.4.1 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.3.3.1.5.1 [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.4.4....

...ing tag Reported-by: kbuild test robot <lkp at intel.com> sparse warnings: (new ones prefixed by >>) drivers/vhost/vhost.c:763:17: sparse: sparse: incorrect type in return expression (different address spaces) drivers/vhost/vhost.c:763:17: sparse: expected void [noderef] <asn:1> * drivers/vhost/vhost.c:763:17: sparse: got void * drivers/vhost/vhost.c:763:17: sparse: sparse: incorrect type in return expression (different address spaces) drivers/vhost/vhost.c:763:17: sparse: expected void [noderef] <asn:1> * drivers/vhost/vhost.c:763:17: sparse:...

...g MIB found for sysOID '.1.3.6.1.4.1.850.1'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. 0.027886 load_mib2nut: trying classic method with 'apcc' mib 0.031624 [tripplite] unhandled ASN 0x80 received from .1.3.6.1.4.1.318.1.1.1.1.1.1.0 0.031665 load_mib2nut: trying classic method with 'mge' mib 0.034569 [tripplite] unhandled ASN 0x80 received from .1.3.6.1.4.1.705.1.1.1.0 0.034584 load_mib2nut: trying classic method with 'netvision' mib...

...g MIB found for sysOID '.1.3.6.1.4.1.850.1'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. 0.029148 load_mib2nut: trying classic method with 'apcc' mib 0.032571 [tripplite] unhandled ASN 0x80 received from .1.3.6.1.4.1.318.1.1.1.1.1.1.0 0.032599 load_mib2nut: trying classic method with 'mge' mib 0.035518 [tripplite] unhandled ASN 0x80 received from .1.3.6.1.4.1.705.1.1.1.0 0.035545 load_mib2nut: trying classic method with 'netvision' mib...

...elopers, with an 'upsc' output for your device. Going back to the classic MIB detection method. 0.018895 load_mib2nut: trying classic method with 'apcc' mib 0.018903 Testing ups.model using OID .1.3.6.1.4.1.318.1.1.1.1.1.1.0 0.022142 [WL_UPS_L4-06] unhandled ASN 0x80 received from .1.3.6.1.4.1.318.1.1.1.1.1.1.0 0.022160 load_mib2nut: testOID provided and doesn't match MIB 'apcc'! 0.022165 load_mib2nut: trying classic method with 'mge' mib 0.022170 Testing ups.model using OID .1.3.6.1.4.1.705.1.1.1.0 0.025440...

...upsd[94201]: mainloop: Interrupted system call Mar 31 09:11:15 freenas kernel: <118>Mar 31 09:11:15 freenas upsmon[94217]: upsmon parent: read Mar 31 09:11:15 freenas notifier: Detected SU6000RT4UHVPM on host 192.168.0.24 (mib: ietf 1.4) Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from 1.3.6.1.2.1.33.1.2.6.0 Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from 1.3.6.1.2.1.33.1.3.3.1.4.1 Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from 1.3.6.1.2.1.33.1.3.3.1.5.1 Mar 31 09:11:19 freenas notifier: [tripplite]...

Hi, Tavis Ormandy found some bugs in OpenSSL's ASN.1 and buffer code that can be exploited to cause a heap overflow: http://lists.grok.org.uk/pipermail/full-disclosure/2012-April/086585.html Fortunately OpenSSH's sshd is not vulnerable - it has avoided the use of ASN.1 parsing since 2002 when Markus wrote a custom RSA verification function (o...

On Feb 24, 2014, at 6:57 PM, Jason R Begley wrote: > Segmentation fault That's not good. If you crank up the debug level past 2, does it provide any more detail about where it crashed? (We'd only need the last few lines, if they are different.) I don't know how Arch Linux does debug symbols, so the dmesg output doesn't pinpoint which function in libc got bad data. Can you run

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at cddiagnostics.com> wrote: > I missed that snmp-ups set pollfreq to 30 by default. I?d hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? There is a TODO comment in snmp-ups that mentions doing something similar to usbhid-ups: just poll the

drivers/virtio/virtio_pci_modern.c:66:40: warning: incorrect type in argument 2 (different base types) drivers/virtio/virtio_pci_modern.c:66:40: expected unsigned int [noderef] [usertype] <asn:2>*addr drivers/virtio/virtio_pci_modern.c:66:40: got restricted __le32 [noderef] [usertype] <asn:2>*lo drivers/virtio/virtio_pci_modern.c:67:33: warning: incorrect type in argument 2 (different base types) drivers/virtio/virtio_pci_modern.c:67:33: expected unsigned int [noderef] [us...

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

This works for me on Centos 5.6. It may assist newcomers to the Linux world of Centos. whois 51.51.51.51 produces a normal and conventional display of data. However since ARIN, the North American registrar of IP addresses, "modernised" its WHOIS processing, a query to whois 64.64.64.64 will produce a one line summary of possible matches, which always includes ARIN, but omits the

Hi: This series tries to fix various issues of vhost: - Patch 1 adds a missing write barrier between used idx updating and logging. - Patch 2-3 brings back the protection of device IOTLB through vq mutex, this fixes possible use after free in device IOTLB entries. - Patch 4 fixes the diry page logging when device IOTLB is enabled. We should done through GPA instead of GIOVA, this was done

Hi: This series tries to fix various issues of vhost: - Patch 1 adds a missing write barrier between used idx updating and logging. - Patch 2-3 brings back the protection of device IOTLB through vq mutex, this fixes possible use after free in device IOTLB entries. - Patch 4 fixes the diry page logging when device IOTLB is enabled. We should done through GPA instead of GIOVA, this was done

...alled? The MIBS are installed in my net-snmp mib directory, I don't know if I need to do anything else. I'm not getting any usefull output from the subdriver script I had to snmp walk to get the data in the files I previously attached. snmp_build: unknown failuresnmpget: Error building ASN.1 representation (Can't build OID for variable) COUNT = 0 / 0 Creating /usr/share/snmp/mibs/tripplite-mib.txt-mib.h Creating /usr/share/snmp/mibs/tripplite-mib.txt-mib.c Done. Do not forget to: * bump DRIVER_VERSION in snmp-ups.c (add "0.01") * copy "/usr/share/snmp/mibs/trippl...

...ng a couple of NT4 domains into 1 native mode Active Directory domain, but plans have changed, and we just went with the upgrade. When I try to join the Samba servers to the new upgraded AD mixed mode domain (net ads join -U Administrator), machines on the WAN fail with the error: ads_connect: ASN.1 encoding ended unexpectedly One machine failed with the error: Broken pipe. I've only tested 3 machines so far, but I'm convinced it will happen everywhere, they are identical boxes, imaged with mkcdrec. The thing is that these machines still join the old native-mode Active Directory...

...e a data set p1982, its structure is the following Then I take 20 observations from this dataset, and assign to pr. in p1982, p has 1982 levels, in dataset pr, p should have 1 levels. But I do str(pr), it shows that p still has 1982 levels. also for these > pr$aa [1] ARG THR ASP CYS TYR ASN VAL ASN ARG ILE ASP THR THR ALA SER CYS LYS THR ALA LYS Levels: ALA ARG ASN ASP CYS GLN GLU HIS ILE LEU LYS MET PHE PRO SER THR TRP TYR VAL it seems pr$aa don't have level GLU, but it list this level. I don't understand this, Is there some reason for these? thanks, > str(p1982)...