similar to: SNMP installation

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5

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

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol:

SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't

>How close do the EPEL RPM's systemd configuration files look to the ones in the NUT tree? The only difference between?/lib/systemd/system/nut-driver.service and the one at?https://github.com/networkupstools/nut/blob/v2.7.2/scripts/systemd/nut-driver.service.in (not counting variable substitution for paths) is an additional line in the [Service] section provided by EPEL:

I have it "working" with the following settings changes from the default in the RPM. By "working" I mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

Hi David On 4/29/20 3:28 PM, David Zomaya wrote: > Is NUT using the same SNMP v3 user as your SNMP Set or a different one? > > If it is a different one (e.g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net> wrote: > > SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP > DL360p gen8, two six-core Thuban-II workstations plua their monitors, > and the network stack and KVM. > > The APC SU3000RM (3KVA) that blew up last week considered this to be > just short of 60% load. > The new

Hello all, I was asked about a proper way to ensure powerfail shutdown of a blade server fed off an APC SmartUPS, which is monitored by all hosts over SNMP. In particular, they'd like to avoid the "untimely" return of utility power - when the OSes are already shutting down, and would stay down because the UPS is well-fed now and thus won't power off and later power on to boot

Hi Jim, On Tue, 18 Feb 2014, Jim Klimov wrote: > Hello all, > > I was asked about a proper way to ensure powerfail shutdown of a blade > server fed off an APC SmartUPS, which is monitored by all hosts over > SNMP. In particular, they'd like to avoid the "untimely" return of > utility power - when the OSes are already shutting down, and would > stay down

On 1/27/19 9:13 PM, Charles Lepple wrote: > On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net > <mailto:phils at caerllewys.net>> wrote: >> The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power >> factor, considers this same load to be 43% load. >> >> I wasn't expecting that much of a reduction. > > So... 50%

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

On Thu, Oct 26, 2017 at 2:24 AM, Marcin Dulak <marcin.dulak at gmail.com> wrote: > Hi, > > since people are suggesting nagios then I can't resist suggesting exporting > the metrics in the prometheus format, > or at least making the project into a library so > https://github.com/prometheus/client_python could be used to export the > prometheus metrics. > There has

Hi all, Despite switching to mod_fcgid (which has improved performance), sessions are still expiring sporadically. I thought I might try switching to storing them in the db, but I get the following error when I try to run the rake create_sessions_table command D:\User\Code\ruby\prometheus>rake create_sessions_table (in D:/User/Code/ruby/prometheus) rake aborted! undefined local variable or

Hi Aravinda, Very nice initiative, thank you very much! As as small recommendation it would be nice to have a "nagios/icinga" mode, maybe through a "-n" parameter which will do the health check and output the status ina nagios/icinga compatible format. As such this tool could be directly used by nagios for monitoring. Best, M. > -------- Original Message -------- >

Hi, since people are suggesting nagios then I can't resist suggesting exporting the metrics in the prometheus format, or at least making the project into a library so https://github.com/prometheus/client_python could be used to export the prometheus metrics. There has been an attempt at https://github.com/ofesseler/gluster_exporter but it is not maintained anymore. Cheers, Marcin On Wed,

Hi, First, thanks for this awesome piece of software. I've just upgraded to latest dovecot, aka 1.2. I've a problem. I've started using Sieve, and everything works fine, I already received a thousand of mails without any problem. However, there's one mail which is stuck in the postfix queue because of that: Jul 8 18:47:51 prometheus dovecot: deliver(jd at danjou.info):

hi there! unfortunately, we are repeatedly having problems with uninitialized constants in our rails app (v1.1.6), which is running on a mongrel cluster behind apache''s mod_proxy_balancer. ---- snip ---- NameError (uninitialized constant Base): [...] /app/models/image.rb:90:in `subclasses'' /app/models/image.rb:98:in `subclass?''