On 11/12/2017 12:29 PM, Mike wrote:
> On 11/12/2017 10:08 AM, Sam Varshavchik wrote:
>> Anyone familiar with Cyberpower's model numbers?
>>
>> I finally got sick of my Tripplite's USB port going south, all the time, so
>> I'm looking to replace it.
>>
>>
On 11/12/2017 10:08 AM, Sam Varshavchik wrote:
> Anyone familiar with Cyberpower's model numbers?
>
> I finally got sick of my Tripplite's USB port going south, all the time, so
> I'm looking to replace it.
>
> The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the
>
On 11/1/2017 11:34 AM, Garrett Michael Hayes wrote:
> This was the secret sauce! I first modified my BASH script to stuff the
> output of the 'set' command into a variable, then passed that variable in to
> my email command. Then I triggered an event and saw what variables were
> there in the
On 9/10/2017 6:41 PM, Sam Varshavchik wrote:
> Dutchman01 writes:
>
>> Hello all,
>>
>>
>>
>> I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4
>>
>> The fact stays that not all distro’s use latest snapshots/commits from
>> github
>> dev tree.
>>
>>
>>
>> So
. How can I change the configuration on ESXI to shutdown after a
small delay so that it is done before the FreeNAS Shutdown starts.
Thanks
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
On 6/5/2017 7:41 PM, Charles Lepple wrote:
> On Jun 5, 2017, at 11:21 AM, Mike <the.li...@mgm51.com> wrote:
>>
>> Result of the command, where "n" is incremented in a loop:
>>
>> # usbconfig -u 1 -a 2 dump_string n
>> STRING_
On 6/4/2017 4:46 PM, Charles Lepple wrote:
[snip]
>> 4) when I went down to 95 volts, the "AVR" kicked in to boost the
>> voltage without going to battery. This was indicated by a "click" from
>> the UPS and an indication on the UPS display.
>
> In non-explore mode, does the driver report the
On 5/30/2017 10:47 PM, Charles Lepple wrote:
> On May 22, 2017, at 11:13 AM, Mike <the.li...@mgm51.com> wrote:
>>
>> On 5/21/2017 10:39 AM, Charles Lepple wrote:
[snip]
>
> The units supported by the usbhid-ups driver are usually solid enough that
> you can do
On 5/21/2017 10:39 AM, Charles Lepple wrote:
> Mike,
>
> Thanks for the info. I have enough to add an entry to the DDL, but I have a
> few more questions inline.
>
> On May 14, 2017, at 1:21 PM, Mike wrote:
>>
>> [updated]
>>
>> OpenBSD 6.1/
On 5/13/2017 1:12 PM, Mike wrote:
> On 5/13/2017 10:20 AM, Charles Lepple wrote:
>> On May 12, 2017, at 10:06 AM, Mike <the.li...@mgm51.com> wrote:
[snip]
>>
>> Per the message from upsdrvctl, the debug flags need to be passed directly
>> to the driver, not to u
[updated]
OpenBSD 6.1/amd64
NUT 2.7.4p0 (from OpenBSD package)
Results of upsc:
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 2902
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 26.9
battery.voltage.nominal: 24
OpenBSD 6.1/amd64
NUT 2.7.4p0 (from OpenBSD package)
Results of upsc:
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 2902
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 26.9
battery.voltage.nominal: 24
device.mfr:
On 5/13/2017 10:20 AM, Charles Lepple wrote:
> On May 12, 2017, at 10:06 AM, Mike <the.li...@mgm51.com> wrote:
>>
>>
>> OpenBSD 6.1/amd64
>> nut-2.7.4p0 (from OpenBSD package)
>> UPS: Tripp-Lite OMNI1500LCDT
>>
>> I cannot get the d
OpenBSD 6.1/amd64
nut-2.7.4p0 (from OpenBSD package)
UPS: Tripp-Lite OMNI1500LCDT
I cannot get the driver for the UPS to load without error.
Here are the commands, with the output, and the config files:
===
# upsdrvctl start
Network UPS Tools
On 3/2/2017 9:57 AM, Charles Lepple wrote:
> On Dec 9, 2016, at 11:14 AM, Mike <the.li...@mgm51.com> wrote:
>>
>> On 12/8/2016 10:37 PM, Charles Lepple wrote:
>>> On Dec 8, 2016, at 1:34 PM, Mike wrote:
>>>> The result of the command
>>>>
&g
On 2/21/2017 8:34 AM, Charles Lepple wrote:
> On Feb 20, 2017, at 11:19 AM, Mike <the.li...@mgm51.com> wrote:
>>
>> This UPS is already listed in the compatibility list. But I wanted to
>> add the instant commands supported by upscmd:
>>
> ...
>&g
This UPS is already listed in the compatibility list. But I wanted to
add the instant commands supported by upscmd:
Instant commands supported on UPS [PW5125]:
beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily
On 12/9/2016 11:14 AM, Mike wrote:
> On 12/8/2016 10:37 PM, Charles Lepple wrote:
>> On Dec 8, 2016, at 1:34 PM, Mike wrote:
>>>
>>> I didn't want to sign up for the nut-devs list or create a git account
>>> just to provide this information, so
On 12/8/2016 10:37 PM, Charles Lepple wrote:
> On Dec 8, 2016, at 1:34 PM, Mike wrote:
>>
>> I didn't want to sign up for the nut-devs list or create a git account
>> just to provide this information, so I hope posting this info here is OK...
>
> Not a problem. (
On 10/5/2016 10:59 PM, Jeff Bowman wrote:
>
>>> How does this work in conjunction with the UPS hardware? Does NUT
>>> immediately send a command to the UPS to wait for 300 seconds and then
>>> shut itself down, thereby allowing the server enough time to safely
>>> shut itself down as well?
>>
>>
d see what it says.
Thanks again!
--Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
o the UPS thinks 600 and
NUT thinks 120, which value will be honored if the power goes out? My
understanding is that the UPS self-reports its low battery status, so
it will report "OB LB" to NUT when it thinks there's 600s left. In
other words, the UPS value of 600s should "win.
configured on the
UPS will be honored.
I read the docs and am not using override.battery.runtime.low. I just
want to sanity check/confirm that the 120 value given by upsc will not
override the the 600 value on the UPS itself.
Thank you!
--Mike
> OS name and version,
Synology DSM 5.2-5644 Upd
We need to make sure this isn't something vm-related
I suspect that this is definitely vm related now. I've tried Ubuntu server
10.10 as you suggested, and also Debian wheezy and both do the same thing.
I saw in another thread that the author of the .vib of nut for ESXi is on
this mailer -
Hope this helps.
It did - thanks! I managed to hack around a bit earlier and did produce the
driver binary but thought I would try from fresh with your steps and got
the binary.
Unfortunately the problem is still there... after a while connection is
lost, updates stop, and upsc reports stale
Thanks Dan and Charles - I've found the usb passthrough will be a
non-starter (not supported on my host).
Dan - is your recommendation to build Nut from source or just the driver?
I'm trying to build the whole project but am obviously missing
dependencies... I've come across a configure error
apollo-ups@localhost lost
$ upsc apollo-ups@localhost
Init SSL without certificate database
Error: Data stale
Not sure what other logs I can provide to try to troubleshoot this?
Thanks
Mike
On 2 January 2015 at 21:04, Charles Lepple clep...@gmail.com wrote:
On Jan 2, 2015, at 1:07 PM, Mike
it forces it to work again, but
again after a few minutes I get the Data stale again and the UPS status
can no longer be interrogated.
Once again, any help greatly appreciated.
Thanks
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
as in the previous attachment. I truncated the before log
because it just carried on with the same output after the broadcast
notification that the UPS became unavailable (at 214.883342).
On 2 January 2015 at 22:14, Mike Raath raa...@gmail.com wrote:
Ok - before stale data:
After stale data:
$ lsusb
Ok - before stale data:
After stale data:
$ lsusb -d 0665:
Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
After stale data:
And the gzipped log attached:
On 2 January 2015 at 21:56, Charles Lepple clep...@gmail.com wrote:
On Jan 2, 2015, at 2:43 PM, Mike Raath raa
(sorry about the top-posting)
I did a killall on blazer_usb and nutdrv_qx, then did a lsusb, got the
following:
$ lsusb -d 0665:
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Then I started the driver in DDD mode, log attached, beyond the point where
communication fails
On 9/19/2013 at 10:49 PM Charles Lepple wrote:
|On Sep 19, 2013, at 12:11 PM, Paul O'Rorke wrote:
|
| So where does this leave things regards Eaton and shut down? Has
anyone
|managed graceful shut down from an Eaton unit with either of the
ushhid or
|bcmxcp drivers?
|
|Generally speaking, the
NUT 2.6.5 on FreeBSD 9.1
Why isn't the variable outlet.1.delay.shutdown set with the following
command?
# upsc PW5125@localhost | grep outlet.1.delay.shutdown
outlet.1.delay.shutdown: -1
# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125@localhost
Enter new value for
On 6/29/2013 at 9:14 AM Mike. wrote:
|NUT 2.6.5 on FreeBSD 9.1
|
|
|Why isn't the variable outlet.1.delay.shutdown set with the following
|command?
|
|
|
|# upsc PW5125@localhost | grep outlet.1.delay.shutdown
|outlet.1.delay.shutdown: -1
|
|# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125
On 6/29/2013 at 9:59 AM Charles Lepple wrote:
|On Jun 29, 2013, at 9:45 AM, Mike. wrote:
|
| On 6/29/2013 at 9:14 AM Mike. wrote:
|
| |NUT 2.6.5 on FreeBSD 9.1
| |
| |
| |Why isn't the variable outlet.1.delay.shutdown set with the
following
| |command?
| |
| |
| |
| |# upsc PW5125@localhost
On 6/29/2013 at 6:16 PM Kjell Claesson wrote:
|lördagen den 29 juni 2013 11.28.14 skrev Mike.:
|8--snip-
|Hi Mike,
|
| Thanks for the quick reply.
|
| I checked the log file (which, admittedly, I should have done before
I
| posted about the problem
On 6/29/2013 at 10:49 PM Kjell Claesson wrote:
|lördagen den 29 juni 2013 15.22.44 skrev Mike.:
|8-snip-
|Sorry for the delay.
|
| Here is the console output of bcmxcp with -DDD specified:
|
|
| [snip]
| 13.721204 Auto delay on: 2
|
| 13.721243
On 6/28/2013 at 6:21 AM Niels Baggesen wrote:
|Den 28-06-2013 04:17, Mike. skrev:
|
| My first question is: is it possible to simulate a UPS is on
battery
| state?
|
|Instead of the real ups, use the dummy-ups driver
|
=
Thanks, that helped me track down the problem, which turned
I've recently moved from installing NUT from source to installing NUT
from the FreeBSD package (FreeBSD 9.1).
One would think that I might have learned not to change anything, but I
made the change. And here is my tale of woe.
My first question is: is it possible to simulate a UPS is on
On 2/26/2013 at 8:56 PM Charles Lepple wrote:
|On Feb 21, 2013, at 11:49 AM, Nick P. Petropoulos wrote:
|
| Is it OK to post my configuration files here, to eliminate obvious
|mistakes and receive advise from other users, or should it be better
to
|send them to the Eaton person doing the porting
to be auto-created.
If I'm heading down the wrong path, please let me know, otherwise, please
point me in the right direction?
Thanks
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo
as requested. Congratulations on this project
and thanks for helping out so quickly!
On 18 October 2012 22:33, Arnaud Quette aquette@gmail.com wrote:
2012/10/18 Mike Raath raa...@gmail.com
Hope I let it run for long enough - compressed output attached.
congrats, you have a working unit.
you
On 8/10/2012 at 4:53 PM Charles Lepple wrote:
|On Aug 10, 2012, at 1:21 PM, Mike. wrote:
|
| I am trying to set a UPS variable, specifically
outlet.1.delay.shutdown
|
|You need upsrw: http://www.networkupstools.org/docs/man/upsrw.html
|
|Unlike upsc, you will also need to define a NUT user
queequeg says hi. :)
I am trying to set a UPS variable, specifically outlet.1.delay.shutdown
I've been all over the online docs. I have found the full listing of
the various variables that I can set. I've read the page that says,
.
C. NUT command and variable naming
Hi
I Bought a cheap Plexus 800VA UPS from ebuyer :
http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo.
Initial version of NUT was very old and NAS didn't detect it although in the
NAS log it said UPS Disconnected. Syslog did send the following :
Jan 25 12:46:36 nas-27lfc
This morning I finished building and configuring nut 2.6.0 on OpenBSD
4.8, and it is running fine.
While I was in the config files, I noticed what looks like it may be a
discrepancy between the config file commetns and the configure script
default.
uspd.conf has the following comment:
#
Trying to build nut 2.6.0 on OpenBSD 4.8, I get a compiler error.
Here's my configure:
./configure --with-user=_ups --with-group=_ups \
--sysconfdir=/etc/ups --with-usb=no
... and the result:
-e Configuration summary:
==
build serial drivers: yes
build USB
On 1/21/2011 at 8:15 PM Arjen de Korte wrote:
|Citeren Mike. the.li...@mgm51.com:
|
| Trying to build nut 2.6.0 on OpenBSD 4.8, I get a compiler error.
|
|[...]
|
| Making all in drivers
| gmake[1]: Entering directory `/home/downloads/nut/nut-2.6.0/drivers'
| gcc -DHAVE_CONFIG_H -I. -I../include
I want to upgrade to 2.6 now that it is an official release.
I have one box that is connected to the UPS via the serial port
('master'). I have another box that connects to the master over the
network.
Can I upgrade the master to 2.6, leaving the other box at 2.2, or do I
need to upgrade
On 1/16/2011 at 8:48 PM Charles Lepple wrote:
|As old as this compatibility chart looks, it is still valid for 2.4.x
and
|2.6.x:
|
|http://www.networkupstools.org/docs/user-manual.chunked/ar01s02.html#_b
ackwards_and_forwards_compatibility
|
|Basically, the network protocol has not changed since
On 11/13/2010 at 8:43 PM Arjen de Korte wrote:
|
|[snip]
| Q: Why doesn't upsmon shut down my system? I pulled the plug and
nothing
| happened.
|
| A: Wait. upsmon doesn't consider a UPS to be critical until it's
both
| 'on battery' and 'low battery' at the same time. This is by
17:20 ?00:00:00 ./usbhid-ups -u root -a
OMNIPLUS1000LCD -x productid=.*2007.*
root 7265 6235 0 17:22 pts/200:00:00 grep ups
Any ideas?
Mike
_
Test your Star IQ
http://club.live.com/red_carpet_reveal.aspx?icid
root 5974 1 0 14:53 ?00:00:00 eggcups --sm-client-id
default5
root 7263 1 0 17:20 ?00:00:00 ./usbhid-ups -u root -a
OMNIPLUS1000LCD -x productid=.*2007.*
root 7265 6235 0 17:22 pts/200:00:00 grep ups
Any ideas?
Mike
? Is
there no way for the server to send commands to the client instead?
I suppose I could make the UPS master the DMZ machine, but that just
seems wrong.
Any suggestions appreciated!
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
not
that familiar with the USB system.
Thanks
Michael Hill
[EMAIL PROTECTED]
-Original Message-
From: Charles Lepple [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 15, 2006 5:41 PM
To: Mike Hill
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] (no subject)
On 11
?
Thanks
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
of preference, I'm in:
Waterloo
Ontario
Canada
But suppliers in say Michigan or New York state would be ok too.
Mike
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
57 matches
Mail list logo
