search for: asns

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

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating 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

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating 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

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: b072ae74df177c3ad7704c5fbe66e3f10aad9d4e commit: b072ae74df177c3ad7704c5fbe66e3f10aad9d4e [12/12] vhost: use vhost_desc instead of vhost_log reproduce: # apt-get install sparse # sparse version: v0.6.1-101-g82dee2e-dirty git checkout b072ae74df177c3ad7704c5fbe66e3f10aad9d4e make

I have been working with NUT to get this working since upgrading to a web snmp card in a UPS. I keep getting seg faults when running snmp-ups also. Below is the output. kernel: [1365065.178230] snmp-ups[1940]: segfault at 0 ip b7555470 sp bf8d89e8 error 4 in libc-2.18.so[b74c2000+1a9000] Running: Arch i686 current Nut is current git Device is Tripp Lite SU2200XLa with WEBSNMPCARD running

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! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD Starting program: /usr/bin/snmp-ups -a tripplite -DD warning: Could not load shared library symbols for

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting

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 (openssh_RSA_verify):

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

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

On 2/24/2014 11:10 PM, Charles Lepple wrote: > 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?

Hi all. Im having a bit of a problem. I have about 20 Samba servers all over the country on 256/512 WAN links. We just upgraded our primary NT4 domain to mixed-mode Active Directory on Windows 2003. In addition to that we have a native-mode Active Directory domain on Windows 2003. We were planning on merging a couple of NT4 domains into 1 native mode Active Directory domain, but plans have

I have 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