search for: serverup

...more lines starting with 'exec:' followed by an absolute path to the driver binary and some command line option. This is what the driver starts and you need to copy and paste that line and append the debug flags to that line (less the 'exec:' prefix). 0.007145 Shutdown UPS: serverups 0.007618 exec: /lib/nut/usbhid-ups -a serverups -k root at odroid-u2:/etc/nut# So I guess it's saying it will not work but to copy and paste some place the line at the end. It that right? If so what file do I copy and paste it in? -Raymond Day -------------- next part --------------...

...at's on this Odroid-u2. The best I found was putting "driver =usbhid-ups" in the /etc/nut/ups.conf file. It looks like this at the end of that file: # To find out if your driver supports any extra settings, start it with # the -h option and/or read the driver's documentation. [serverups] driver = usbhid-ups port = auto desc = "Server UPS" # productid = "CP1500 AVR UPS" Here is what I get on the command line: root at odroid-u2:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic HID driver 0.37 (2.6.4...

...; wrote: > > Wow that was fast thank you Charles. > > Put "upsc" in the /etc/nut/ups.conf and then went to start it with > "upsdrvctl start" but I get this then: No, sorry, I didn't mean to change ups.conf - I meant that if the UPS name is listed as "[serverups]", you should run "upsc serverups" at the command line, rather than "upsc apc". I'd recommend the following ups.conf: #################### [serverups] driver = usbhid-ups port = auto desc = "Server UPS" #################### > You said NUT 2.6.4...

I did just copy and paste on the command line like this: root at odroid-u2:/etc/nut# Shutdown UPS: serverups -bash: Shutdown: command not found root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 Initiating UPS shutdown root at odroid-u2:/etc/nut# Don't know why it says &...

...toolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' configure.ac:15: installing `./missing' clients/Makefile.am: installing `./depcomp' Makefile.am: installing `./INSTALL' root at odroid-u2:~/nut# upsc serverups Error: Driver not connected root at odroid-u2:~/nut# upsc serverups Error: Driver not connected root at odroid-u2:~/nut# upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Duplicate driver instance detec...

28 ??????? 2016??. 4:18:06 CEST, Raymond Day <raymondday at hotmail.com> ?????: >I forgot how I ask this. But I just found out. It's a list here: > >http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html > >Thanks again. Seems like it's working real good. > >Is there a way to test if it will turn off my server when the battery >power

...for our church.? We are?running CENTOS 5.2. I tried the Linux Power Management Software that came with Belkin UPS with NO success. I installed the NUT software. After some experimentation I received some success with the megatec_usb Nut driver: [root at server bin]# /sbin/megatec_usb -u root -a serverups -DDDD Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] debug level is '4' Checking device (1267/0103) (001/004) - VendorID: 1267 - ProductID: 0103 - Manufacturer:...

Wow thanks for all your help. I unplug the power to the UPS and did the command "upsc serverups" to see if the "battery.charge: 100" would go down. I watched some videos so it's hard drive would spin up to use more power. After about a hour it did go down to "battery.charge: 90" So it is working. Not sure if it will turn off at 20% of battery that's what...

...bhid-ups" "Cyber Power Systems" "Value 800E" "USB" "usbhid-ups" > /Thomas > > PS. Here's the full variable list. Oh, and thanks to all of you for > some great software, I guess :) thanks for all of us ;-) > # upsc serverups > battery.charge: 98 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS this one is bad > battery.runtime: 588 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 19.9 > battery.voltage.nominal: 12 > driver.name: usbhid-up...

...s for a few seconds, even though the line power is never lost. I guess it could be caused by some transient in the power line? I've listed the output of upsc and tripplite_usb --DDD below. I'm running NUT 2.4.3 with tripplite_usb driver 0.20 on Fedora 14 x86_64. [root at denali ~]# upsc serverups battery.charge: 100 battery.voltage: 27.40 battery.voltage.nominal: 24 device.mfr: Tripp Lite device.model: SMART1000RM2U device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.product: .*SMART1000RM2U.* driver.version: 2.4.3 drive...

sending to the list for posterity. > On Oct 27, 2016, at 6:43 AM, Raymond Day wrote: > > Thank you. > > Looked like that worked. > > I put your code in /etc/nut/nut.conf just at the end of that file. > > Then did. > > upsdrvctl start > > upsc serverups > > Got this date back: > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 7650 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 9.5 > battery.voltage.nominal: 12 > de...

...ry runtime will not be calculated (runtimecal not set) 18.025409 [D3] send: error sending control message: Connection timed out 18.025529 [D2] blazer_status: short reply 18.026837 [D1] Communications with UPS lost: status read failed! 18.027010 [D2] dstate_init: sock /var/run/nut/blazer_usb-serverups open on fd 5 23.026403 [D3] send: error sending control message: Connection timed out 23.026442 [D2] blazer_status: short reply 23.026453 [D1] Communications with UPS lost: status read failed! 23.197877 [D3] send: QS 23.202242 [D3] read: #230.0 004 24.00 50.0 23.202271 [D2] blazer_stat...

...alculated (runtimecal not set) > 18.025409 [D3] send: error sending control message: Connection timed out > 18.025529 [D2] blazer_status: short reply > 18.026837 [D1] Communications with UPS lost: status read failed! > 18.027010 [D2] dstate_init: sock /var/run/nut/blazer_usb-serverups open on fd 5 > 23.026403 [D3] send: error sending control message: Connection timed out > 23.026442 [D2] blazer_status: short reply > 23.026453 [D1] Communications with UPS lost: status read failed! > 23.197877 [D3] send: QS > 23.202242 [D3] read: #230.0 004 24.00 50....