Displaying 20 results from an estimated 3000 matches similar to: "USB problem as user"
2007 Apr 12
1
APC 1500 USB problem
Hello,
We have two APC Back-UPS RS 1500 USB stuff, and i've got a bit
of a problem with it and NUT.
The usbdevs output:
addr 2: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion
addr 3: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion
(UPS1 and UPS2)
I've configured our NUT system to monitor the UPSes, and it went very
fine till the time had arrived for a
2007 Apr 20
2
Multiple UPS monitoring, relaying
Hello,
I've got a setup with NUT, where we've got two UPSes,
ups1 and ups2. UPS1 supports our servers, while UPS2
supports our desktop boxes. We monitor both of them
via USB on a box now called "upsmon".
The interesting point comes here. We monitor both
UPSes on the upsmon box, but if UPS2 fails, which
supports our desktop boxes, NUT shouldn't initiate
a shutdown in
2008 Feb 07
1
usbhid-ups and "data stale"
Hello
I'm using nut 2.2.0 on FreeBSD 7.0-RC1. I've got two UPSes (Back-UPS RS
1500) connected to the host, and I often see them to go away. All the
system logs are full of "Poll UPS [ups1 at upshost] failed - Data
stale".
What causes this issue? Is this a known issue, is it going to be fixed?
What farther investigations should I do to get some more info on this
issue?
--
2009 May 05
5
upsd flapping in the breeze
Hi,
I have had a long standing problem with NUT talking to 110V MGE UPSs on
FreeBSD, I was recently investigating again and noticed that upsd seems
overly noisy, eg..
May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale
May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver
May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale
May 5
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
(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
2025 Apr 02
2
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
Well, either I misunderstood what you wrote or (my initially written post
follows, probably misguided at start) I think your log contradicts your
statements:
> when my bash script receive events from TIMER like LINE-STATUS-xx
> NOTIFYTYPE is always ONBATT
> in all other cases, NOTIFYTYPE is TRUE and same as it was called by upsmon
in the log I see :
* Initial ONBATT:
Apr 1 17:07:39
2025 Apr 01
1
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
HI
i'am using schema upsmon call : NOTIFYCMD /sbin/upssched
and this part of upsschede strategy (working fine)
device.model: Ellipse ECO 650
root at ---:~# cat /etc/nut/upssched.conf
# Network UPS Tools - upssched.conf sample file
CMDSCRIPT /opt/nut/bin/upssched-cmd
PIPEFN /var/run/nut/upssched.pipe
LOCKFN /var/run/nut/upssched.lock
#
2008 Jul 22
1
MGE Pulsar EX1500 RT comms problem
Hi,
I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data
stale' very frequently (every few minutes).
I have tried the usual trick of setting maxage, poll interval, etc etc
but to no avail.
When I wind up logging I see (on mge-shut)
entering shut_get_report(id: 0d, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 16, len: 1800)
shut_wait_ack():
2013 Oct 09
0
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
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
2009 Nov 15
3
two MGE Ellipse 1500 ups via usb
Hi,
I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu
jaunty system with nut and libupsclient1 2.4.1-2ubuntu4.
As soon as I start the driver for the second one, they start fighting
each other and I get no data. I found an older post to this list that
said: If you want to monitor multiple UPSes through usbhid-ups, you
*must* make sure that each one can be uniquely identified
2017 Nov 30
2
SNMPv3 fails when more than one UPS is configured in ups.conf
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
2011 Mar 14
1
UPS Support
I am currently trying to use your NUT program to monitor a SMART3000RMOD2U TRIPP LITE device. I find that it connects with the in the device folder as hiddev0 and if I connect a second device it connects under hiddev1. I attempted to use your software with the driver=usbhid-ups and port=auto, but when I try to discover it it can't be found. Then when I run the command /sbin/usbhid-ups -a
2012 Mar 04
2
NUT Two Apc UPSes on Windows
Hi,
I've got a question about managing two UPSes under NUT.
I have two similar model APC usb-connected UPSes to work with, but don't
know how to manage them simultaneously from under Windows. Long story
short, my ups.conf looks like this:
--- ups.conf ---
[ups1]
driver= usbhid-ups
port= auto
serial=AS1054340323
[ups2]
driver= usbhid-ups
port= auto
serial=AS1026662626
---
2007 Apr 16
1
newhidups fails only at boot
I can start the driver successfully manually, after the machine is up
and running, but at boot time, it can't find my UPS. My init script
makes sure that the usbfs is up (by checking for the existence of
/proc/bus/usb/devices), and I can't think of what else could be
different with the boot-time failure versus the manual startup after
logging in. I'll include my configuration at the
2007 Jan 18
1
APC Back-UPS XS 1200 - permission denied
I have a new APC Back-UPS XS 1200. It is detected properly by the Linux
kernel (2.6.16):
# dmesg
usb 5-3.4: new low speed USB device using ehci_hcd and address 9
usb 5-3.4: new device found, idVendor=051d, idProduct=0002
usb 5-3.4: new device strings: Mfr=3, Product=1, SerialNumber=2
usb 5-3.4: Product: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1
usb 5-3.4: Manufacturer: American Power Conversion
usb
2007 Jul 28
1
Support removed for newer Belkin 1200 VA UPS?
Have had no issue until I ran apt-get dist-upgrade this morning:
# /lib/nut/newhidups -u nut -DDDDDD auto
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
debug level is '6'
Checking device (0000/0000) (001/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
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()
0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.056112 SNMP UPS driver : entering load_mib2nut(auto)
0.056126 trying the new
2007 Feb 07
1
Network Management Card (MGE) 66102 with snmp-ups
I'm trying to set up nut with a MGE UPS equiupped with a network
management card, but encountered a problem.
UPS: MGE Pulsar M 3000
Network Management card (installed in the UPS): 66102 (2006 edition)
Operating system: FreeBSD
Nut port version: 2.0.5
Nut driver: snmp-ups
According to MGE in Norway this card is supported by nut, but only
the old version of the card (66244) is listed on
2005 Dec 24
1
Regular expressions in upssched.conf?
Hi,
I didn't found an answer for my question in NUT documentation/FAQ or
this mailing list archive so I?m posting it here.
I want to start a timer only if both of my UPSes remain on battery. Not
just one, both.
My UPSes are:
- ups1@host-a
- ups2@host-b
Is it possible to use something like this in upssched.conf?
AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180
Thanks,
2006 Feb 27
1
MGE Nova 1100 using newhidups on netBSD 3.0
Have recently purchased a MGE Nova 1100 UPS and am trying to get running on
netBSD.
Configuration
netBSD 3.0 amd64
libusb 0.1.10a
nut 2.0.3
Built & installed libusb
Built kernel with ugen device and uhid removed
Build & install nut-2.0.3 with usb
Chmod /dev/ugen1 etc to allow access by nut user.
Ups.conf
[MGENova]
driver = newhidups
port = auto