Re: [Nut-upsuser] /var/run/nut directory not created on CentOS 7.2 with systemd

On Dec 25, 2016, at 3:37 PM, Mark Hansen wrote: > > I think one of the NUT configuration/control files is supposed to create this > directory when it starts, but that's not happening. Is it possible this is a > bug > in the NUT package on CentOS? I would argue that it should be handled by the

Re: [Nut-upsuser] unclear about expected shutdown behavior

> On Dec 24, 2016, at 3:14 AM, Roger Price wrote: > > On Sat, 24 Dec 2016, Spike wrote: > >> ... from reading the docs it seems the UPS should power off, is that the >> case? > > Yes, The UPS should be sent a "delayed shutdown" command, upsdrvctl shutdown, > to tell it

Re: [Nut-upsuser] NUT Client shuts down when performing runtime calibration on APC UPS

On Dec 20, 2016, at 9:03 AM, Merk - Oliver wrote: > > Hello, > > 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 card to start the > runtime calibration. However, after 2min. of

Re: [Nut-upsdev] 2.7.4 make install fails: libnutclient.so.0.0.0 missing

On Dec 10, 2016, at 3:42 PM, Roger Price wrote: > > I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled > nut 2.7.4. ./configure, make clean and make went well, but make install > failed. Make reports > > Making install in clients > make[1]: Entering directory

Re: [Nut-upsuser] Problem installing NUT on 16.04

> On Dec 9, 2016, at 10:40 PM, Jack McGee wrote: > > ● nut-server.service - LSB: Network UPS Tools initscript >Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled) >Active: active (running) since Fri 2016-12-09 13:48:34 CST; 7h ago > Docs:

Re: [Nut-upsuser] Keeps losing connection with UPS (local usb connection)

On Dec 8, 2016, at 8:57 PM, dwill...@inebraska.com wrote: > > > OS: Debian 3.16.36 > Nut version: 2.7.4 from the “stretch” distribution (this was to solve > another problem – which it did) > Install method: apt-get > Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver > > Problem: I

Re: [Nut-upsuser] Problem installing NUT on 16.04

On Dec 8, 2016, at 7:56 PM, Jack McGee wrote: > > I rebooted machine and nut cannot connect to the UPS. Any messages from the kernel regarding USB HID drivers? (Check dmesg and/or journalctl.) ___ Nut-upsuser mailing list

Re: [Nut-upsuser] [HCL] Cyber Power Systems EC750G supported by usbhid-ups

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. (Both lists go into the same mailbox on my end.) The important part is the "HCL"

Re: [Nut-upsdev] nut-git reporting 24 Volts with CP1350PFCLCD -- is that correct?

On Dec 7, 2016, at 1:35 PM, David C. Rankin wrote: > I just built and installed network-ups-tools-git-v2.7.4.r161.g7bf209a on > Archlinux for a CyberPower CP1350PFCLCD ups. After hitting the FAQ 29. "My USB > UPS is supported but doesn’t work!" udev issue because

Re: [Nut-upsuser] Problem installing NUT on 16.04

> On Dec 3, 2016, at 12:31 PM, Jack McGee wrote: >> so this is progress. Thanks! Anything else to check to know it is working >> as it should? http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic,

Re: [Nut-upsuser] Problem installing NUT on 16.04

On Dec 3, 2016, at 11:16 AM, Jack McGee wrote: > > Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 > Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 > Dec 3 08:38:16 amethi upsd[18234]: no listening interface available I can't say I

Re: [Nut-upsuser] Problem installing NUT on 16.04

> On Dec 3, 2016, at 11:01 AM, Jack McGee wrote: > > I did restart those services, no change. > $ ps auxww|grep [/]nut root 13074 0.0 0.0 37844 2628 ?Ss 08:42 0:00 /lib/nut/upsmon nut 13076 0.0 0.0 45632 5148 ?S08:42 0:00

Re: [Nut-upsuser] Problem installing NUT on 16.04

> On Dec 3, 2016, at 9:44 AM, Jack McGee wrote: > > But doesn't this still indicate an error: > > mythuser@amethi:/etc/nut$ upscmd -l CyberPower1 > Error: Connection failure: Connection refused Correct - "upsc", "upscmd" and "upsrw" need to connect to "upsd", and "upsd"

Re: [Nut-upsuser] Problem installing NUT on 16.04

On Dec 2, 2016, at 10:23 PM, Jack McGee wrote: > > This is new install on Ubuntu 16.04, using packages from Synaptic, > Network UPS Tools upsd 2.7.2 > > I am getting these messages in the terminal: > Broadcast message from nut@amethi (somewhere) (Fri Dec 2 12:33:03 2016):

[Bug 1540008] Re: USB permissions not set at install time (udevd name changed?)

Confirmed that this affects xenial as well. ** Tags added: xenial ** Changed in: nut (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540008 Title: USB

Re: [Nut-upsuser] Can't get NUT slave to connect to master

.html#UPS_shutdown -- - Charles Lepple https://ghz.cc/charles/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Nov 24, 2016, at 10:58 AM, Jonah Naylor wrote: > > Is there something I should be doing other than adding "allowfrom = > ipaddressofslave" to the upsd.users file on the master? Which version of NUT are you using? Reference for the current version:

Re: [Nut-upsdev] [HCL] CyberPower Cyber Power Systems CP685AVR supported by usbhid-ups

[please use Reply-All - this list does not modify the reply-to header] > On Nov 23, 2016, at 10:30 AM, Craig STCR wrote: > > It looks like the CyberPower Cyber Power Systems CP685AVR supported by > usbhid-ups has a favorable device dump linked to the Devices Dumps >

Re: [Nut-upsuser] How to disable hal-addon-hid-ups

On Nov 13, 2016, at 10:08 AM, Charles Lepple wrote: > > This sounds a lot like what this file was designed to do: > > > https://github.com/networkupstools/nut/blob/master/scripts/upower/95-upower-hid.rules I thought this sounded familiar. In removing the code that talked to

Re: [Nut-upsuser] How to disable hal-addon-hid-ups

On Nov 11, 2016, at 1:01 PM, Stuart Gathman wrote: > > I've tried several recipes found with google, but hal likes to grab the > USB ups before nut can get it. > There are a number of klugey workarounds, like turn off port power until > ready to start nut (so that hal doesn't see the UPS). Or >

Re: [Nut-upsuser] Windows 2008 r2 nut not starting

On Nov 1, 2016, at 1:43 PM, nccuss17 wrote: > > Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c > Can't start C:\Program Files (x86)\NUT\bin/(null).exe: No such file or > directory > [The system cannot find the file specified. ] > EventLog : Starting

Re: [Nut-upsuser] Questions about Eaton 5E 1, 100W 2, 200VA 6-Outlet UPS

> On Oct 31, 2016, at 10:15 PM, Michael Evans wrote: > > Are there any other tests I can perform or ways that I can help gather data > to get the longer tests supported? > The "test.battery.start" command takes a parameter in seconds (defaults to 600):

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

I finally got the PPA updated: https://launchpad.net/~clepple/+archive/ubuntu/nut The latest version there was built with libusb-1.0 instead of libusb-0.1. I still get the occasional issue with the Tripp Lite 3016 device with this code, but it seems to be less frequent. I will need to swap

Re: [Nut-upsdev] [HCL] supported by

[please use Reply-All - this list does not modify the reply-to header] > On Oct 29, 2016, at 2:37 PM, Francois Cukier wrote: > > root@Monitor:/etc/nut# upsc ups1 > Init SSL without certificate database > battery.runtime: 133200.00 This runtime seems high. The driver

Re: [Nut-upsuser] trouble building nut for HID-USB [Tripp Lite 4016]

On Oct 28, 2016, at 8:43 AM, Dorsey, Scott B. (LARC-D316)[LITES II] wrote: > > So, no suggestions for diagnosing intermittent driver loading issues? > >> You might also benefit from adjusting these variables: >> http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010352.html > >

Re: [Nut-upsuser] setting up CYBERPOWER CP1500PFCLCD

On Oct 26, 2016, at 8:41 AM, Tomasz Przychodzień wrote: > > This was only the log from the program. I'm sending my upsmon.conf attached > (I removed nas ip number, admin login and pass (no spaces in parameters) and > also changed back minsupplies to 1), the rest of the settings are the same as

Re: [Nut-upsuser] setting up CYBERPOWER CP1500PFCLCD

On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzień wrote: > > Level INFO10/26/2016 10:46:17Detected OS as Windows NT > Level NOTICE10/26/2016 10:46:17Network UPS Tools upsmon 2.0.0.4 > Level INFO10/26/2016 10:46:17Config Load: MINSUPPLIES set to 1 > Level INFO

Re: [Nut-upsuser] setting up CYBERPOWER CP1500PFCLCD

[please use reply-all to include the list - the headers are not mangled] On Oct 25, 2016, at 9:53 AM, Tomasz Przychodzień wrote: > > Hi, > > Another beginner question. I spend hours trying to find the solution for how > to configure winnut properly but I' struggling to make it work. I want my

Re: [Nut-upsuser] Questions about Eaton 5E 1, 100W 2, 200VA 6-Outlet UPS

On Oct 25, 2016, at 8:08 PM, Michael Evans wrote: > > It seems that the UPS I bought is actually served by the blazer_usb driver. > > USB ids 06da:0003 (lsusb DB thinks it's a "Phoenixtec Power Co., Ltd 1300VA > UPS", but this has apparantly been re-used by Eaton 5E2200USB-LA) > > It's sold as

Re: [Nut-upsuser] Data Stale at random intervals

On Oct 24, 2016, at 9:56 PM, Daniel Shields wrote: > > Hi Charles, > > Tried it with -p but couldn't get it to run, I'll have to dig further > into the man pages. I ran without -p though and got an interesting timeout > error. Attached is the log. I'll look further into the -p option

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

On Oct 24, 2016, at 10:38 AM, Lane Russell wrote: > > How could I check if another instance is causing me issues? This is a running > on a KVM host server, so there's very little activity on the server itself. There should only be one usbhid-ups process running at

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

esource busy >> 9528.632326 Got disconnected by another driver: Device or resource busy​ >> >>> On Wed, Oct 12, 2016 at 8:35 AM, Charles Lepple <clep...@gmail.com> wrote: >>> On Oct 12, 2016, at 9:07 AM, Lane Russell wrote: >>> > >&g

Re: [Nut-upsuser] Data Stale at random intervals

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields wrote: > > I've been testing with debug further and there's a few extra lines when the > nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS

Re: [Nut-upsuser] TrippLite SU3000XLCD

[please use reply-all to include the list - the headers are not mangled] On Oct 20, 2016, at 3:22 PM, Fairfax, Charles A. wrote: > > I’m having trouble with a TrippLite SU3000XLCD. I’m using a Raspberry Pi > running Raspbian (wheezy) with NUT 2.6.4. > > I can monitor my older TrippLite

Re: [Nut-upsuser] No matching HID UPS found

> On Oct 20, 2016, at 8:25 AM, jf...@sdf.org wrote: > > Using protocol: Q1 0.02 > Can't autodetect number of battery packs [-1/13.50] > Battery runtime will not be calculated (runtimecal not set) > > ... looks like it's connected to something, although maybe the driver is not > quite right?

Re: [Nut-upsuser] No matching HID UPS found

[please use reply-all to include the list - the headers are not mangled] > On Oct 18, 2016, at 9:02 PM, jf...@sdf.org wrote: > > So, apparently, my Eaton is sending > > Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Do you get a device named "/dev/ttyUSB0" when you plug

Re: [Nut-upsdev] CyberPower SX650G no driver.

On Oct 18, 2016, at 9:35 AM, Raymond Day wrote: > > How do I run the git one? I guess it's up to date. Don't, for now. There have been a few posts on the mailing list explaining what to pass to ./configure (or ./autogen.sh, which calls configure) to get the Git version

Re: [Nut-upsdev] CyberPower SX650G no driver.

(please use Reply-All to keep the list CC'd, thanks) > On Oct 18, 2016, at 8:53 AM, Raymond Day 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

Re: [Nut-upsdev] CyberPower SX650G no driver.

On Oct 18, 2016, at 8:21 AM, Raymond Day wrote: > > > # To find out if your driver supports any extra settings, start it with > # the -h option and/or read the driver's documentation. > [serverups] ^ this is the name of the UPS that you should pass to "upsc"

Re: [Nut-upsuser] Data Stale at random intervals

On Oct 14, 2016, at 8:53 PM, Daniel Shields wrote: > > Ran with gdb: > > gdb /lib/nut/usbhid-ups > > run -u nut -a nailbunny -x bus=010 -x vendorid=0764 -x productid=0501 -D > > Same result as when I ran normally. Driver just stops communicating with no >

Re: [Nut-upsuser] Unable to find driver for a supported device

On Oct 12, 2016, at 3:28 PM, Nick Teague wrote: > > Alright. Sorry to bother you guys. Apparently after I rebooted the box, it > started working now on the tripplite-usb driver. One correct also. I didn't > have it installed from ports but from binary pkg. (pkg install nut) No worries -

Re: [Nut-upsuser] trouble building nut for HID-USB

> On Oct 12, 2016, at 2:00 PM, Dorsey, Scott B. (LARC-D316)[LITES II] > wrote: > > It does in fact show exactly what you describe. Udev is working properly > with the device file being assigned to group > dialout, which the nut user is in. You were correct about my

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

On Oct 12, 2016, at 9:07 AM, Lane Russell wrote: > > Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not called out, > so I assume it's using the default of 2s. "pollfreq" and "pollfreqalert" are > both set to 10s in upsmon.conf at the moment. "deadtime" is set to 30s. No

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

On Oct 10, 2016, at 11:32 PM, Lane Russell wrote: > > It looks like I'm currently on 4.4.0-38 > > uname -a: > Linux kvm 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 > x86_64 x86_64 GNU/Linux Ah, right, the default kernel for Ubuntu 16.04. (I am getting the distributions

Re: [Nut-upsuser] Unable to find driver for a supported device

ding from source), so let us know, and we can zero in on the problem quickly. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

> On Oct 6, 2016, at 7:26 PM, Lane Russell wrote: > > Ubuntu Server 16.04.1 LTS > NUT 2.7.2-4ubuntu1 > Apologies if you mentioned this already, but which kernel are you running? Looking back over the recent USB problems, we saw a lot of problems with the 3.16

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM [DNS]

> On Oct 10, 2016, at 2:12 PM, Stuart D. Gathman wrote: > > On Mon, 10 Oct 2016, Lane Russell wrote: > >> I tried viewing your link, but it returns a 404 error. It also doesn't seem >> to have a valid certificate. Could you send the correct link please? > > I tried from

Re: [Nut-upsdev] nutdrv-qx powercool 1500VA USB UPS

> On Oct 10, 2016, at 4:29 PM, Matthew Wire wrote: > > Here is the complete log for two minutes from startup. thank you compressed to fit on the mailing list. > > On 9 October 2016 at 23:41, hyo...@gmail.com wrote: > > 12.243069 send: Q1 > >

Re: [Nut-upsuser] trouble building nut for HID-USB

pshots on Buildbot aren't being properly indexed by branch, but this build is what I am currently testing: http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/664 -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing li

Re: [Nut-upsuser] NOTIFYCMD doesn't work at all... not fully

> On Oct 6, 2016, at 6:15 AM, Stefan Fröchtenicht wrote: > > when i execute the upsnotify.sh as root, then it works great. eMails and SMS > are incoming. > But when i for e.g. pull out the ups from power, then there will be only > emails and NO SMS. Why? > NUT runs the notify script as the

Re: [Nut-upsuser] UPS Shutdown

On Oct 5, 2016, at 10:59 PM, Jeff Bowman wrote: > >> The command is "upsdrvctl shutdown". > > That's what I thought, but I get this: > > Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could > not > claim interface 0, win error: The requested resource is in use. > >

Re: [Nut-upsdev] driver for Victron Multiplus RS485

[please use Reply-All - this list does not modify the reply-to header] > On Oct 3, 2016, at 4:15 PM, Jon 'Boli' Copeland wrote: > > Hi All, > > I'd like to modify an existing driver to support my Victron Multiplus > inverter/charger. This device is not supported by the victron driver. > > I do

Re: [Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]

On Sep 16, 2016, at 9:38 AM, Vassilis Virvilis wrote: > > A little deciphering > >> Looks like the ups always replies >> 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 > > That is > length = 0x16 = 22 > type = 0x3 = string > Message = "UPS No Ack" > > Very fun... that string shows up

Re: [Nut-upsuser] Use nut to handle shutdown when using local Li-io battery (Cubietruck)

On Sep 15, 2016, at 7:45 AM, Ingo Fischer wrote: > > But would it not be an idea to have a gerneric "linux" driver for nut? Good point. When I think "generic", I think "programmable"[*], but you are right - the /sys interface is fairly standard. [*] ("programmable" is a bit heavy for this

Re: [Nut-upsuser] Use nut to handle shutdown when using local Li-io battery (Cubietruck)

On Sep 15, 2016, at 7:19 AM, Ingo Fischer wrote: > > Or is there a generic driver that maybe uses a formatted textfile, so I > could write the data in a defined format file every x Minutes or such ... > I was not able to find something like this so far. You can do this with the "dummy-ups"

Re: [Nut-upsuser] How to get started (Windows)

On Sep 14, 2016, at 9:29 AM, Jeff Bowman wrote: > C:\Users\Admin>upsc ups@localhost > battery.charge: 100 ... > ups.status: OL If ups.status follows the state of line power, the driver is working (and upsc talks to upsd, so that connection is working as well). > So

Re: [Nut-upsuser] How to get started (Windows)

> >> I think you have that first link working (assuming usbhid-ups is still >> running). If the server is not running, you can try starting it manually with >> one or more "-D" flags to see what is going wrong. > > Not much here: > > --- > C:\Users\Admin>upsdrvctl -DD start Sorry,

Re: [Nut-upsuser] How to get started (Windows)

On Sep 11, 2016, at 3:37 PM, Jeff Bowman wrote: > >Using subdriver: APC HID 0.95 > > ...and then hangs for 45 seconds before returning to a command prompt. No UPS > hardware information is printed. It can take about that long to read the descriptors. The

Re: [Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]

On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis wrote: > Now that's a problem. I am not sure that I can find > > 1) the original software > 2) a (physical) windows machine in the vicinity of the UPS > > I will give it a try but for now looks like a dead end. I have 3 of

Re: [Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]

On Sep 8, 2016, at 9:25 AM, Vassilis Virvilis wrote: > > + failed to claim USB device: could not claim interface 0: Device or > resource busy > + detached kernel driver from USB device... > nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > HID

Re: [Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]

rebooting" the UPS (something other than "Got 0 HID objects..."), try toggling the AC power (recommend using a circuit breaker or power strip to keep the ground and neutral attached) to see what an "on battery" event looks like. -- - Charles Lepple https://ghz.cc/charles/

Re: [Nut-upsuser] Any good SNMP tutorial?

> On Aug 17, 2016, at 5:01 PM, Brian Hilmers wrote: > > ... how to configure NUT to receive SNMP Trap signals I don't have any SNMP equipment to test against, but I think the snmp-ups driver simply polls - no traps needed. (Polling has the advantage of detecting when

Re: [Nut-upsuser] CGI: multiple web pages

> On Aug 12, 2016, at 2:20 PM, Sergio Belkin wrote: > > Hi, > > I'm using the CGI program upsstats.cgi to view the status of UPS's on a web > browser. > > > I'd want to do something like that: > > /var/www/nut-cgi-bin-group-A/upsstats.cgi >

[Bug 1483615] Re: usbhid-ups driver segfaults on discovery of UPS

@william-gallaf, likely related. While the patch mentioned in comment #6 above will prevent the segfault, it also prevents the driver from determining whether some APC workarounds need to be applied: https://github.com/networkupstools/nut/blob/master/drivers/apc-hid.c#L40 Which size Back-UPS ES

Re: [Nut-upsuser] FSD sequence not working on Ubuntu 16.04 LTS

tracking this down. (I'm still wrestling with vagrant and VirtualBox, trying to set up a 16.04 test environment...) Please let us know the Launchpad URL for the issue once it is filed. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-u

Re: [Nut-upsuser] Windows Version not working --

On Jul 14, 2016, at 7:34 AM, Jeff Silberberg <j...@compudesigns.net> wrote: > > >> On Wed, Jul 13, 2016 at 11:28 PM, Charles Lepple <clep...@gmail.com> wrote: >> It sounds like the UPS is connected. Since you mentioned libusb0.dll, make >> sure that the UPS

Re: [Nut-upsuser] FSD sequence not working on Ubuntu 16.04 LTS

conf I would recommend filing a bug with Ubuntu. It would help them track things down if you can identify the logs which should be running the systemd equivalent of "upsdrvctl shutdown" or " -k". -- Charles Lepple clepple@gmail __

Re: [Nut-upsuser] Windows Version not working --

rator console - not sure how the Windows port handles permissions. Only then will upsd and upsc (upper layers in the diagram) have a chance of returning data. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@

Re: [Nut-upsuser] Tripplite SNMP Webcard and NUT

d be able to shutdown that UPS over a USB connection. However, if you need to use SNMP, you will need the snmp-ups driver, and SNMP shutdown functionality was not added until 2.6.4 (in Ubuntu 14.04 and later). http://networkupstools.org/docs/man/snmp-

Re: [Nut-upsuser] unexpected shutdown, had to reinstall xorg.server

are/doc/nut-cgi/README.Debian has step-by-step instructions, although it is a little light in the web server configuration section (naturally, given how many are out there). I think the cgi-bin pathname works with the default configuration for Apache 2. -- Charles Leppl

Re: [Nut-upsuser] query "Data stale" from the cmdline

interrupt stuff applies to APC models with USB ID 051d:0002) If needed, we can look at the debug output to see what is going on, but for whatever reason, a few "data stale" messages over the course of a day seems normal for many USB UPS interfaces. -- Charles Lepple clepple@gmai

[Nut-upsdev] reassessing the HCL ratings scale

topic of the HCL, I also think it might be handy to list some of the more common vendors at the top of the "Manufacturer" filter dropdown. Suggestions for criteria would be appreciated. -- Charles Lepple clepple@gmail ___ Nut-upsdev ma

Re: [Nut-upsuser] What is the purpose of the upsmon setting in upsd.users?

On Jun 23, 2016, at 10:28 PM, André Hänsel wrote: > > On Donnerstag, 23. Juni 2016 14:14, Charles Lepple wrote: > >> The "upsmon slave" setting should not prevent clients from connecting. Can >> you provide more details about the system? If this is a distr

Re: [Nut-upsuser] What is the purpose of the upsmon setting in upsd.users?

gt;> André > > Ok, I did some further testing and it seems that setting "upsmon slave" does > not allow clients to connect, so when would I want to set it? > The "upsmon slave" setting should not prevent clients from connecting

Re: [Nut-upsdev] ./configure excludes USB drivers and documentation

. libusb-1.0 switched from usb.h to libusb.h, and the internal libusb.h inside NUT is different (but does not seem to interfere with the public header). -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian

Re: [Nut-upsdev] updating the NUT website

t seems to be the > real match for 'bestpower-mib.c' (see how '.1.3.6.1.4.1.2947.1.1.8.0' > is mapped to 'manufacturing date', while > http://powerquality.eaton.com/Support/Software-Drivers/Downloads/connectivity-firmware/bestpwr2.mib > -which appears to be a newer revision of that

Re: [Nut-upsuser] Besoin d’aide pour upssched

alioth.debian.org/mailman/listinfo/nut-upsuser -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Fink-users] zbar installation

On 11/2/15, 4:35 PM, Buz Barstow wrote: > In [1]: import zbar > Segmentation fault: 11 > apollo8:Version 0 buz$ > Any updates on this? Same symptoms here. Using Fink's python2.7, "import zbar" gets a Segmentation fault. libzbar-py27 0.10-3 $ fink --version Package

Re: [Nut-upsdev] updating the NUT website

ckage branch. I don't think I have enough experience with submodules to say what I would prefer, so I'll leave that up to you. Let me know if you'd like help with anything else. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] updating the NUT website

Makefile:796: *** target pattern contains no '%'. Stop. Any ideas? Also, what do I do afterwards to push to GitHub? -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/

[Nut-upsdev] updating the NUT website

to the NEWS file in the NUT repository, then that pulls in any other changes from that branch. Does it make sense to create a NUT branch based off of the 2.7.4 release, and put all of the NEWS/download updates there? We can then merge that back into master as needed. -- - Charles Lepple https://ghz.cc

Re: [Nut-upsuser] Is a timer a file?

> On Jun 5, 2016, at 6:34 AM, Roger Price <ro...@rogerprice.org> wrote: > > On Sat, 4 Jun 2016, Charles Lepple wrote: > >> On Jun 3, 2016, at 6:48 AM, Roger Price <ro...@rogerprice.org> wrote: >>> ... the timer. I don't see it in /var/lib/ups where the

Re: [Nut-upsuser] Restarting service issues

the NUT repository can only be a suggestion -- the actual integration will depend on the distribution. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Is a timer a file?

suggestion > would be much appreciated. Thanks, Roger I don't use upssched myself, but from looking at the code, it seems that the timers are only stored in memory. See checktimers(): https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L129 -- Charles Lepple clepple@gmail

Re: [Nut-upsuser] Problem with nut

. My understanding is that the Synology software embeds NUT, and that there is an "upsd.users" file somewhere on the NAS which has the NUT username and password that you can add to "upsmon.conf" on your desktop system. SSH wouldn't be involved in that c

Re: [Nut-upsdev] Lyonn ULT-2000 MKR supported by

http://networkupstools.org/docs/man/snmp-ups.html -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] A lot of EAGAIN (Resource temporarily unavailable) using nutdrv_qx

libusb-1.0 in the roadmap? So far, there have not been any good arguments for libusb-1.0 that would offset the amount of testing needed. Feel free to experiment, though. For timing purposes, it should be sufficient to write a small loop that sends the command for your UPS, and reads the res

Re: [Nut-upsuser] cannot get APC ups status change via usb cable from RaspberryPi

ith the apcsmart driver: http://networkupstools.org/ddl/APC/Smart-UPS_3000_RM.html There is a "pollonly" flag that might help, but it is supposed to be selected automatically. What does 'lsusb -vvv -d 051d:' return when run as root? -- Charles Lepple clepple@gmail __

Re: [Nut-upsuser] Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down

lear which protocol number the serial driver was written for. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down

power to return"). I suspect we could emulate it with the watchdog, but that will require a fair amount of testing to make sure we understand the timer. https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L675 As a result, the last entry in the FAQ will apply: http://net

Re: [Nut-upsdev] Tripp-Lite SMART1500LCDT

orkupstools/nut/pull/122 I don't have a lot of experience with that branch, but it sounds promising. (I would prefer to identify the underlying problem rather than work around it by closing and reopening the USB device more frequently, though, especially given the testing needed for other UPSes.)

Re: [Nut-upsuser] ups.status don't switch to "OB LB"

} }; Reference: https://github.com/networkupstools/nut/blob/master/drivers/ietf-mib.c#L38 If these values don't change when the power state changes, then the problem is upstream of NUT. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Monitoring Only

On Wed, May 18, 2016 at 9:27 AM, Sergio Belkin wrote: > Hi, > > What shoud I do in order to configure NUT to perform only monitoring, I mean > to not shutdown anything at all? The simplest way: in upsmon.conf, make sure that SHUTDOWNCMD is set to something innocuous.

Re: [Nut-upsuser] Low Battery event not occurring

On May 16, 2016, at 1:30 PM, Kamran Khan wrote: > > I added the "ignorelb" option and changed the "battery.charge.low" to "90" to > try to get it to reboot fast. There should be a "driver.flag.ignorelb: enabled" line in the upsc output. Check syslog to make sure that

Re: [Nut-upsuser] Low Battery event not occurring

and synthesize it from battery.charge or battery.runtime: http://networkupstools.org/docs/man/ups.conf.html (search for 'ignorelb') -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] New UPS Support: Eaton 5S 1000

ot;new low-speed USB device" message once for the UPS, when it is first plugged in (or when the system is booted). -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] New UPS Support: Eaton 5S 1000

ce I guess I skipped the non-LTS versions between Ubuntu 12.04 and 14.04): which init system does this version run? Do you know if there are any apparmor profiles that might be preventing the driver and upsd from talking? Any crash messages in dmesg? -- Charles Lepple clepple@gmail _

Re: [Nut-upsuser] New UPS Support: Eaton 5S 1000

I'd kill the driver and start everything normally once. (I didn't think the driver would get that far, but for future logs, please redirect to a text file and attach a gzip'd version.) -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsus

Re: [Nut-upsuser] New UPS Support: Eaton 5S 1000

nning under the nut/ups users). Then, just start the driver with debugging, same as your first email: # /usr/local/ups/bin/usbhid-ups -DD -a eaton -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@list

Re: [Nut-upsuser] New UPS Support: Eaton 5S 1000

t;./configure --with-user=ups..." Although it can be overridden with the "-u" flag, I am not sure if that would help. (We sometimes recommend "-u root" for debugging permission issues with the driver, but then the driver might create a socket that upsd can't read with

<    1   2   3   4   5   6   7   8   9   10   >