similar to: NUT Client shuts down when performing runtime calibration on APC UPS

Hello, I am using an APC UPS (Smart-UPS 2200 RM) to secure my SAN. The SAN runs on FreeBSD 9.1-RELEASE-p5 and is using NUT 2.6.5 version 2. Since the UPS has also a Network card AP9630 I am using the snmp-ups driver to connect the SAN to the UPS for signaling. Last week I need to change the battery pack and then I needed to perform a runtime calibration. I used the web interface of the AP9630

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

On Jan 9, 2017, at 9:46 AM, Merk - Oliver <oliver.merk at pecon.biz> wrote: > > I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power loss is 5 min", the UPS is configured to an SNMP-Connection with its IP-address. Started runtime calibration and after 5min. the QNAP NAS has shut down. But before that I connected via SSH on

Thanks for your help. I have posted information, but I think I have answered myself, so maybe you haven't got an info. Sorry, using a mailing list is new for me ;-) Let's forget about the QNAP problem. It seems that although upsc is getting correct status information ("OL", "OB", "OB LB", OB CAL"), including calibration state, the QNAP special program

On Wed, 11 Jan 2017, Merk - Oliver wrote: > nas4free: /# more /usr/local/bin/upssched-cmd > #!/bin/sh I would strongly recommend specifying which script interpreter is to be used: dash, bash, csh, ksh, ... For example #!/bin/bash There seem to be too many case statements in this script. > case "${1}" in > shutdown-warning) >

Hello: I have APC AP9630 UPS, use nut, but the execution failed, my ups.conf setting right? thank! nut2.7.3 net-snmp5.2.1 openssl0.9.8 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160419/032eedd5/attachment.html> -------------- next part -------------- A non-text attachment was

Hello, i'm trying to monitor a APC Smart-UPS 1000 behind a APC AP9630 Network Management Card via SNMPv3 using the AES Privacy Protocol. * OS name and version: Debian 10.1 * exact NUT version: 2.7.4 * NUT installation method: from debian package 2.7.4-8 * exact device name and related information * Model Number AP9630 * Hardware Revision 08 * Manufacture Date

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

That's an idea Charlie. The APC UPS I am using has an AP9630 card in it and pfSense is grabbing the snmp. I could try to use the USB cable on the FreeNAS so both could be masters. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Danny Siminiuk" <daniel at siminiuk.com> Cc: "nut-upsuser" <nut-upsuser at

Updating an old thread. History here. http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html On Fri, 1 Feb 2013, Tim Rice wrote: [snip] > > In all my testing I discovered the APC AP9630 is kind of flaky when >

Hi, thanks for the reply. On 2014-05-29 05:21, Charles Lepple wrote: >> Now my questions: >> 1. should the blazer_ser's high voltage be the voltage during charging >> or right after I've unplugged it from the mains? > sounds like during charging (or more accurately, during float charging at the end of the cycle): > >

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more

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 Mar 30, 2014, at 10:39 PM, Shade Alabsa wrote: > Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the

Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the AES protocol, though in my set up it works with

On 2014-02-19 03:04, Tim Rice wrote: > If you've got a AP9630 card these notes may be useful. > > # APC ap9630 notes: > # Use firmware 6.0.6 or later if you want SNMPv3 > # Configuration->Shutdown > # In "Start of Shutdown" section, set "Low Battery Duration" and > # "Shutdown Delay" to get enough grace time for the ESXI shutdown > #

Hi, I have a binary variable and corresponding predicted probability (using logistic regression on some explanatoey variables); I want to check that the model is well-calibrated using a calibration plot. how can I have the calibration plot for my data? thanks. [[alternative HTML version deleted]]

I have been working on fitting Cox model for prediction by using rms package. I want to measure model's calibartion and discrimination. Discrimination was measured by using validate() in rms, Dxy can be transferred to Harrell's c index. But in this way, I cannot get 95%CI of c index. How can I do this in R? And by the way, what value should be in c index to present the model's well?