Displaying 20 results from an estimated 1000 matches similar to: ""UPS myups@localhost is unavailable" from upsmon"
2005 Oct 17
0
Re: Feedback: Back-UPS RS 800 USB works with NUT
Hi Klaus,
Thanks for your much appreciated feedback.
Klaus Holler wrote:
> Hello,
>
>I just wanted to report that the Back-UPS RS 800 works with the
>Network UPS Tools. Currently I use the following (Ubuntu breezy)
>debian packages on kernel 2.4.31:
>ii nut 2.0.2-1build1
>ii nut-usb 2.0.2-1build1
>
>lsusb reports:
>ID 051d:0002 American Power Conversion Back-UPS Pro
2006 Mar 12
1
Fw: upsmon not authenticating (I've read the FAQ)
Another update!
It works. The systems shuts down properly when power is lost.
Almost.
"upsdrvctl shutdown" disconnects my UPS from the mains. From everything I've
read in the documentation this should turn off the output of the UPS, not
the input. Am I right here?
I'm still having the following problem. Any help is appreciated.
>> Also - I get the following every 4
2005 Nov 07
1
TrippLite OMNI1000LCD hiddev compatibility
Hi all:
I am trying to get a TrippLito OMNI1000LCD working with nut.
Even with the development branch, I get the following....
upsdrvctl start
Network UPS Tools - UPS driver controller 2.1.0
Network UPS Tools: HID UPS driver 0.13 (2.1.0)
Warning: This is an experimental driver.
Some features may not function correctly.
Detected Tripp Lite TRIPP LITE UPS
on port /dev/usb/hiddev0
2006 Mar 12
0
upsmon not authenticating (I've read the FAQ)
An update -
I ran a test by unplugging my UPS and letting it run down. The system shut
down as it should.
However, the /etc/killpower file was not created, and the UPS did not shut
off power as it should from the shutdown scripts. This may be because the
command to kill the output of the UPS isn't available, or that by not being
able to log in as master prevents this. The permissions on the
2005 Dec 28
2
(no subject)
I'd like to submit a patch to the 'hidups' driver. I'm a bit new to
open-source development model, so I hope I'm not committing a faux paus by
just posting it here. I did verify that the problem still exists (by
source code inspection) in the latest dev snapshot, which is
nut-2.0.3-pre2. I'm using nut-2.0.2 myself.
The problem is when I'm connecting to my APC
2007 Jan 12
0
Followup to previous E-mail..
Using the "hidups" driver produces better results, however, I'm not sure
if these "unhandled events" errors are good or bad.. I would suspect
bad...
Any direction would be appreciated..
Thanks,
Richard.
root@excalibur:/usr/src/nut-2.0.5-pre2# ./drivers/hidups -u root -DDDD -a
apc /dev/usb/hiddev0
Network UPS Tools: HID UPS driver 0.13 (2.0.5-pre2)
Warning: This is an
2014 Oct 01
2
Socomec ITYS 3000 + Netvision upsmon output
Hi,
I have UPS Socomec ITYS 3000 with Netvision card.
OS is Centos 6.5 64-bit.
NUT installed with yum,.
nut-2.6.5-2.el6.x86_64
nut-client-2.6.5-2.el6.x86_64
Why is ups.status empty?
Here is upsc output:
upsc myups at localhost
battery.charge: 97.00
battery.runtime: -60.00
battery.voltage: -0.10
device.mfr: Net Vision v6.01 (SN 0101414290)
device.model: ITYS 3 kVA
device.serial: 3I14450043
2018 Aug 11
1
After years, upsmon says I've no perms
But /etc/nut/upsmon.conf has the correct username and password.
returns:
gene at coyote:/usr/share/doc/nut-doc/pdf$ upsmon myups at localhost
Network UPS Tools upsmon 2.6.4
kill: Operation not permitted
/etc/nut/upsmon.conf line 75: invalid directive [*****]
/etc/nut/upsmon.conf line 76: invalid directive password = **************
/etc/nut/upsmon.conf line 77: invalid directive upsmon master
UPS:
2006 May 18
1
Difficulty over USB with a CyberPower 800AVR and nut 2.0.3
I recently purchased a CyberPower 800AVR UPS which I'm trying to use
over USB with my PC (ArchLinux 0.7.2 [aka up to date]) and nut 2.0.3.
Following the setup instructions, I have an entry as follows in
/etc/nutups/ups.conf (where I chose the configuration file to go when
building nut):
[MyUPS]
driver = cyberpower
port = /dev/bus/usb/004/007
desc = Workstation
2005 Jul 22
0
USB setup
Hi,
I am trying to get a tripp-lite UPS monitored. It is connected to a
system through usb.
Here is my ups.conf:
[myups]
driver = hidups
port = /dev/usb/hiddev0
Here is what lsusb shows:
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 09ae:0001 Tripp Lite
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Here is what reports when I
2006 Dec 27
1
right problem with ups belkin (model who work with nut)
hi
i have a belkin ups
here some setting
chmod 0600 /dev/hiddev0
chown nut:root /dev/hiddev0
linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.4
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
No matching USB/HID UPS found
Driver failed to start (exit status=1)
linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start
2017 May 26
0
Powercom Smart KING Pro 1250A - Driver failed to start
Hi. Sorry for the English. Use online translator.
Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie.
OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1
exact NUT version: 2.7.2-4
NUT installation method: package
exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed)
complete problem description, with any relevant
2017 May 26
0
Powercom Smart KING Pro 1250A - Driver failed to start
Hi. Sorry for the English. Use online translator.
Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie.
OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1
exact NUT version: 2.7.2-4
NUT installation method: package
exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed)
complete problem description, with any relevant
2006 Dec 01
1
hidups unhandled events on Linux/amd64
Hello,
I have encountered problems trying to set up nut to work with APC BackUps Pro CS connected over USB to an AMD64 machine running Debian. While apcupsd works fine with that device, whenever I start upsd I get the following messages in syslog:
hidups[23159]: Startup successful
upsd[23160]: Connected to UPS [apc1]: hidups-hiddev0
upsd[23161]: Startup successful
hidups[23159]: Unhandled event:
2006 Sep 13
2
POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string!!!
Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message:
POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string
My upmon.conf contain:
MONITOR myups@theseo 1 orion91 carlos81 master
SHUTDOWNCMD "/sbin/shutdown -h +0"
HOSTSYNC 15
POWERDOWNFLAG /etc/killpower
FINALDELAY 5
My killpower scrit in /etc/killpower
2005 Oct 18
2
usb doesn't build on mac os x (10.4)
I am having problems building usb on mac os x. First, mac os x
doesn't seem to have asm/types.h, just sys/types.h. I can't find
hiddev.h on mac os x either. Also, it doesn't have usb.h but instead
IOKIT/usb/USB.h. I am using mac os x (10.4), and the latest cvs of nut.
Is the new usb support going to work on mac os x? Is anyone working
on it? It seems that libusb is available
2015 Feb 09
0
About your driver NUTDRV_ATCL_USB(8) for install
Dear Chales,
Thanks for your quick reply.
I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8
14:47:22 GMT 2015 armv6l GNU/Linux]
If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well
without any error as "Device or resource busy".
If I run <upsc> command never receive any value from my ups <upsc
ups at
2006 Jul 01
2
Unhandled event when using APC BackUPS Pro
Hi,
I'm new to nut, just installed it. I configured it using the hidups
driver to work with my APC BackUPS:
# upsc apc350@localhost
battery.charge: 100
battery.runtime: 885
battery.voltage: 13.5
driver.name: hidups
driver.parameter.port: /dev/usb/hiddev0
driver.version: 2.0.0
ups.delay.shutdown: -1
ups.delay.start: 0
ups.load: 660
ups.mfr: American Power Conversion
ups.model: Back-UPS CS 350
2006 Sep 12
1
Build 2.0.4, usb.h missing.
Hi!
I've got a Mandrake 2006.0 machine and a APC Back-UPS Pro 500/1000/1500
(from lsusb). The Mandrake package version of nut is 2.0.1 and hidups
actually detects the UPS, however I get loads of these:
Sep 12 18:26:11 vader hidups[7658]: Ignoring x86 page event 0xff860080 (0)
Sep 12 18:26:11 vader hidups[7658]: Unhandled event: 0x840058 (6)
Sep 12 18:26:11 vader hidups[7658]: Unhandled
2007 May 24
1
Bogus shutdown
Nut shut down a machine last night when there was no power outage.
When I came in this morning, the UPS was turned off, but it turned on
cleanly and passed its self-test. The battery was at 62% when I
first checked it, and it's up to 63% now, about 20 minutes later.
The UPS is a Tripp-Lite AVR550U. I'm running nut version 2.0.3.
I expect to be told to update to a newer version and to