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

Re: [Fink-devel] Could I get someone with 10.10+Xcode 7 to test something?

s: local/main stable/main local/injected $ fink list xcode Information about 9387 packages read in 3 seconds. i xcode 7.2.0.0.1.144782692 [virtual package representing the developer tools] i xcode.app 7.2.1-1 [virtual package repre

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

t specifically in the man page: "ERRORS 0 or ENOENT or ESRCH or EBADF or EPERM or ... The given name or uid was not found." Do you have any other nsswitch.conf settings besides the flat files for /etc/passwd and friends? Is nscd running? Did you uninstall the Ubuntu

Re: [Nut-upsuser] IBM 5396-1Kx ups nearly recognised.

you get in syslog. There are some procedures listed in the NUT User Manual for how to test shutdowns without accidentally cutting power if things are not configured correctly. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-ups

Re: [Nut-upsuser] IBM 5396-1Kx ups nearly recognised.

ed a compiler and all of the relevant lib*-devel packages.) It is possible that you could just change one of the Arch build scripts from "nut-2.7.4.tar.gz" to "nut-v2.7.4-20-ga7f4858.tar.gz" and rebuild, but I am totally speculating. (Note the extra "v" before the version nu

Re: [Nut-upsuser] OSX and USB issue

... $ cd hidapi $ git checkout hidapi-0.7.0 ... $ open testgui/TestGUI.app Choose your UPS from the list, and click Connect. It should not be necessary to send reports or feature requests to the UPS - a sequence of 8-byte hex values should show up in the bottom box in a few seconds. -- Charl

Re: [Nut-upsuser] OSX and USB issue

Pi or a BeagleBone Black? We have talked about making the USB backend a bit more flexible (to be able to use native HID code such as the OS X interfaces), but that will take a fair amount of design and testing. -- Charles Lepple clepple@gmail __

Re: [Nut-upsuser] Network UPS Tools for APC Smart-UPS 5000VA 230V SRT

into consideration when selecting an UPS brand." -- 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] longtime NUT user with APC ups units..just installed GE LP33..how to get it configured?

be able to change the hostname in the ups.conf entry for the old APC units. Other configuration information that might need to be changed: http://networkupstools.org/docs/man/snmp-ups.html -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuse

Re: [Nut-upsuser] riello idialog 600

"upsdrvctl start" when you are not debugging. Let us know how that works, and we will add the idialog 600 to the Hardware Compatibility List: http://networkupstools.org/stable-hcl.html#footnotes -- Charles Lepple clepple@gmail _

Re: [Nut-upsuser] Incorrect battery.runtime.low being reported?

On Mar 8, 2016, at 12:54 PM, Mike Lee <curby+for...@cur.by> wrote: > > On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clep...@gmail.com> wrote: >> If you stop and start the driver, it should refresh. > > Hi Charles, thanks for the reply! Pardon the dead ho

[Nut-upsdev] Countdown to 2.7.4

for closed issues as well), that would be helpful. -- 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: [Fink-users] wxwidgets300-osxcocoa: wxrc linking to libraries in %i rather than %p

On 2/2/16, 9:33 PM, Alexander Hansen wrote: > Thanks for the report. I’ll fix that when I get a chance. I do a > lot of fixing for root-directory linkage already, but apparently I > missed wxrc. > 3.0.2-4 works now, thanks!

Re: [Nut-upsuser] APC Back-UPS BX1400U

On Feb 20, 2016, at 1:08 PM, Charles Lepple <clep...@gmail.com> wrote: > > On Feb 16, 2016, at 12:57 AM, T. Ermlich <pelegr...@gmail.com> wrote: >> >> Sorry for the email only send to you, Charles! >> Here's the one for the list. > > I realize it is n

Re: [Nut-upsuser] APC Back-UPS BX1400U

e for the UPS. I ran "udevadm trigger --subsystem-match=usb --action=change" and it fixed that issue. (Rebooting after installing the package would also work.) -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.a

Re: [Nut-upsuser] download device event log entries

prefer, you can mask out the last digits of the serial number in the logs. -- 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] download device event log entries

endorid=0463 -x explore -DD' -- 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

[Fink-users] wxwidgets300-osxcocoa: wxrc linking to libraries in %i rather than %p

Fed up with the junk that SF.net is wrapping around OS X apps like FileZilla, I tried compiling it from source. (Sidebar: what is the difference between wxwidgets300-osxcocoa and wxwidgets300-cocoa?) With wxwidgets300-osxcocoa version 3.0.2-3, the wxrc binary seems to be linking to libraries in

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

Public bug reported: 1) $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 2) nut-server: 2.7.1-1ubuntu1; udev: 204-5ubuntu20.15 3) On a fresh install of Ubuntu 14.04 (amd64), I installed the nut- server package while the UPS was already connected via USB. After

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

Public bug reported: 1) $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 2) nut-server: 2.7.1-1ubuntu1; udev: 204-5ubuntu20.15 3) On a fresh install of Ubuntu 14.04 (amd64), I installed the nut- server package while the UPS was already connected via USB. After

Re: [Nut-upsdev] Patching CyberPower UPS drivers

chunked/ar01s03.html#_source_code_management http://buildbot.networkupstools.org/snapshots (note that "2.7.3.1" is not a real version number, it's just something greater than 2.7.3 - the links include the full Git revision, and only the first 5-8 characters are needed from that) -- Cha

Re: [Nut-upsdev] Patching CyberPower UPS drivers

better than comment characters (which don't nest), and removing it completely is even better (fewer false positives when searching). If nothing else, it's in version control. Diff attached. Thanks, -- Charles Lepple clepple@gmail powerp-txt.c.diff Description: Binary data ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [us...@bb.net] Buildbot on Mac OS X

ackages? (FWIW, I use virtualenv and pip for the master, and I create "packages" of the known-good installs by maintaining a history of tarballs - not pretty, but it works. I figure I am only maintaining one instance of the master, versus potentially many slaves.) -- Charles Lepple clepple@gmail ___ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users

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

Since you only have one UPS, I would recommend removing the extra "-x" options (this prevents problems down the road if a new kernel assigns a different bus number). I believe the regex matcher is case-sensitive, so the "051D" does not match. Interestingly enough, we did have another recent

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

Since you only have one UPS, I would recommend removing the extra "-x" options (this prevents problems down the road if a new kernel assigns a different bus number). I believe the regex matcher is case-sensitive, so the "051D" does not match. Interestingly enough, we did have another recent

Re: [Nut-upsuser] Can't get latest version for Raspberry Pi

n 8.x). I'm not sure if the Raspbian maintainers recommend doing "apt-get dist-upgrade", or if they would suggest that you start from a fresh install image, but the dist-upgrade would probably take quite a while. -- Charles Lepple clepple@gmail _

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

@davis65536: I think we might have a lead on this. Are you running in a VM? https://github.com/networkupstools/nut/issues/258 The APC portion of usbhid-ups expects that if it can open the device, it can read the string descriptors. Your system is printing "unknown" for the Manufacturer, Product

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

@davis65536: I think we might have a lead on this. Are you running in a VM? https://github.com/networkupstools/nut/issues/258 The APC portion of usbhid-ups expects that if it can open the device, it can read the string descriptors. Your system is printing "unknown" for the Manufacturer, Product

Re: [Nut-upsuser] Powercool?

entOS VMs, but that might be a while. Let us know if you need additional information on rebuilding the RPMs. Also, what does 'lsusb -v -d0001:' return when run as root? -- 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] Powercool?

On Jan 23, 2016, at 12:11 PM, Tim Clarke <tim.cla...@manifest.co.uk> wrote: > > On 23/01/16 16:52, Charles Lepple wrote: >> [please use reply-all to include the list on your response] >> >> On Jan 23, 2016, at 11:14 AM, Tim Clarke <tim.cla...@manifest.co.uk>

Re: [Nut-upsdev] UPS Trust OXXTRON 1300VA not working

ide much information - it is similar to genericups (OL/OB/LB). -- 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] UPS Trust OXXTRON 1300VA not working

ls.org/docs/man/richcomm_usb.html If the richcomm_usb driver does not show proper status changes, then the UPS is different than the previous model with the same name, and the real protocol is not known. -- Charles Lepple clepple@gmail ___ Nut-upsd

Re: [Nut-upsuser] NUT support for CyberPower PR1500LCDRTXL2Ua

On Jan 18, 2016, at 7:59 PM, Ben Kamen <bka...@benjammin.net> wrote: > > an ASCII translation mode sure would be nice. Hahahahah.. I forgot this wasn't in the common code: https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L372 -- Charles Lepple c

Re: [Nut-upsdev] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

the elapsed time as battery.runtime.elapsed. I have created a Github issue to clarify the documentation, and another to patch the driver to be consistent with the other NUT drivers: https://github.com/networkupstools/nut/issues/257 -- Charles Lepple c

[Nut-upsdev] Request for OpenSSL assistance (blocking I/O on Solaris)

of the client-side SSL I/O calls with while() loops. Any suggestions? -- 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] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

Since this might be hard to work around with the current driver, we can put a note in the DDL, but at this point I don't know what the note should say. -- 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] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

al: 120 > output.current: 0.0 > output.frequency: 60.0 > output.voltage: 119.7 > ups.alarm: Input Bad > ups.firmware: LSPWM(15).55 > ups.id: ny7bd8723tbecabc > ups.load: 000 > ups.mfr: NHS Sistemas de Energia > ups.model: Laser Senoidal 5000VA > ups.power.nominal: 05

Re: [Nut-upsuser] usbhid-ups dying, consistently

On Dec 31, 2015, at 6:54 PM, Nicholas Leippe <lei...@gmail.com> wrote: > On Thu, Dec 31, 2015 at 4:43 PM, Charles Lepple <clep...@gmail.com> wrote: >> Other than the reconnection attempts, usbhid-ups only fully opens the UPS >> USB device once. >> > Th

Re: [Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR (New output)

e? I would like to merge the solis_debug branch in to the master branch. Bruno, Any ideas? Mario mentioned his model is getting mis-detected as a Solis 1.0. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.

Re: [Nut-upsuser] Server not shutting down before power loss

g/docs/man/upsmon.html#_forced_shutdowns > You'll have to excuse me as I've not used nut before, but I'm sure it's an > Ubuntu or nut config problem here and that the shutdown sequence isn't > happening and not my UPS... Any other details you can provide on the configuration will make

Re: [Nut-upsuser] Server not shutting down before power loss

the output of "upsc" for your UPS, we can update the DDL. Be sure to check the output for serial numbers if you don't want that published online. (The first few digits can be helpful, though.) [2] http://www.networkupstools.org/ddl/APC/Back-UPS_ES_550.html -- Charles Lepple clepple@gma

Re: [Nut-upsuser] Contact-closure UPS

> put on UPS Pin1. I always forget which signals are inverted, but for upsdrv_qx: "By default the driver will set DTR and clear RTS..." You can adjust this if needed: http://www.networkupstools.org/docs/man/nutdrv_qx.html#_serial_interface_only -

Re: [Nut-upsuser] Contact-closure UPS

reshold voltage, so if it can accept 3-12V, you could wire it directly. -- 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] APC Back-UPS 950 Battery Connector

UPS models have a DC power connector to keep the battery unplugged while the unit is being transported. -- 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] output.voltage on a CyberPower CP1350PFCLCD

progress has been made on this issue, which I think is a prerequisite: https://github.com/networkupstools/nut/issues/169 > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin

Re: [Nut-upsuser] Cannot access Patriot Pro II from new system

0, UART: 16550A, Port: 0x03f8, IRQ: 4 >Baud_base: 115200, close_delay: 50, divisor: 0 >closing_wait: 3000 >Flags: spd_normal skip_test Curious about the "skip_test" option... > ___ > Nut-upsuser mailing list > Nut-upsuser@list

Re: [Nut-upsuser] usbhid-ups dying, consistently

fine for an older MGE on a slightly-less-old Soekris box running BSD - it reconnects about once every day or two. But I don't have any Gentoo boxes or 4.x kernels to test against at the moment.) -- Charles Lepple clepple@gmail ___

Re: [Nut-upsuser] Contact-closure UPS

LB[DCD] SD[DTR] is this correct? Probably. The testing procedure at http://www.networkupstools.org/docs/man/genericups.html#_testing_compatibility should help in case some of the signals need a "-". -- Charles Lepple clepple@gmail ___

Re: [Nut-upsdev] Some thoughts on loss of communication

cation failure, and most of the drivers already have timeouts built in. As a backup, the distribution startup/shutdown scripts should probably have timeouts as well - this used to be implemented as a delay between sending SIGTERM and SIGKILL. -- Charles Lepple clepple@gmail ___

Re: [Nut-upsdev] lost communication with UPS

to upsd, or the driver loses the connection to the UPS, upsmon should not shut down unless the last status message received was "OB". > As I said, thanks to all the help I received from Charles Lepple, I was able > to get this UPS working, and it has worked fine for many m

Re: [Nut-upsuser] Contact-closure UPS

/usr/lib/ups/driver/nutdrv_qx -a infosec The above message is saying that the debug flags need to be added to the driver command line, not to the upsdrvctl command: /usr/lib/ups/driver/nutdrv_qx -DDD -a infosec -- Charles Lepple clepple@gmail

Re: [Nut-upsuser] Contact-closure UPS

ect up the TxD and RxD lines, and use the nutdrv_qx (not available until after v2.6.5), megatec or blazer_ser drivers: PC UPS Description == === === 2 9 TxD 3 6 RxD 5 7 Ground -- Charles Lepple clepple@gmail _

Re: [Nut-upsuser] Contact-closure UPS

5.4.1)? The loopback connections would be for the modem control lines (hardware handshaking, which your UPS probably does not do). Other than that, I think the DB-9 pinout is the same. nutdrv_qx would be best, but blazer_ser is the next newest driver. -- Charles Lepple clepple@gmail ___

[Nut-upsuser] HOWTO video from +superlinux

+superlinux on YouTube posted a detailed walk-through of setting up NUT on Debian: https://www.youtube.com/watch?v=cn3DQ0ns9aQ Source: https://github.com/networkupstools/nut/issues/241 -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing

Re: [Nut-upsdev] UPS serial protocol

itoring features and test commands. If your customers' desired feature list matches that, you should be all set. -- 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-upsuser] snmp-ups ApplicationError / APPCRASH

47 In that case, neither the driver (snmp-ups.exe) nor upsd is needed in Windows (the usbhid-ups driver and upsd are running on the NAS). -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.

Re: [Nut-upsuser] I/O errors with usbhid-ups and Tripp Lite SMART1500LCDT

On Oct 25, 2015, at 8:33 PM, Null <n...@wuffleton.com> wrote: > > On 2015-10-23 5:42, Charles Lepple wrote: >> I'm not really sold on this approach (due to the testing needed on other >> hardware), but this pull request reworks the USB communication so that the >

Re: [Nut-upsdev] problem with compiling on Cygwin64

build the USB drivers. Which version of libusb do you have installed? -- 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-upsuser] I/O errors with usbhid-ups and Tripp Lite SMART1500LCDT

On Oct 23, 2015, at 8:42 AM, Charles Lepple <clep...@gmail.com> wrote: > >> Environment for reference: >> NUT Version: v2.7.3.r128.g96c93fb (GIT); v2.7.3 stable exhibits the same >> behavior >> OS: Arch Linux x86_64 >> Kernel Version: 4.2.4.2015102220

Re: [Nut-upsdev] problem with compiling on Cygwin64

th-drivers=dummy-ups,usbhid-ups -- 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-upsuser] OSX El Capitan - Fink - NUT

On Oct 5, 2015, at 10:24 PM, Charles Lepple <clep...@gmail.com> wrote: > > There are some unpleasant bits related to the OpenSSL license and GPL > software. The attached patch to /sw/fink/dists/stable/finkinfo/net/nut.info > should build on 10.11, but I probably shouldn't mer

Re: [Fink-devel] Transition of packages from system-openssl-dev

selfupdate” to get newer fink releases as > usual. Should we hold off on committing updated info files? I saw that a few packages on the list on the wiki are crossed out already. Or should we commit them as "restrictive", then update the license field after 0.39.x+1 lands? -

Re: [Nut-upsuser] Assistance with understanding how to setup NUT for our small server room

ps://www.zabbix.org/wiki/Zabbix_Templates#Power_.28UPS.29> Zabbix hasn't been discussed much on the NUT lists, but if that works, please let us know. Another easy-to-setup monitoring system compatible with NUT is collectd: https://collectd.org/wiki/index.php/Plugin:NUT <https://collectd.or

Re: [Nut-upsuser] APC Back-UPS ES 650 connected to a Synology DS411slim

ail (though not likely to change): the "upsmon master" permissions are a superset of the "upsmon slave" permissions. You should be able to set up your desktop as a slave using the existing upsd.users. https://github.com/networkupstools/nut/blob/master/server/user.c#L320 -

Re: [Nut-upsuser] APC Back-UPS ES 650 connected to a Synology DS411slim

the exact same configuration options, I can successfully connect from > Windows XP using WinNUT 2.0.0.4. WinNUT, to the best of my knowledge, only uses the NUT network protocol. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-ups

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

gt; the USB ID. Let me know what you think. Thank you. > > Joe Gzesh > Sent from Zimbra Open Source Mail Server. Hosted at my House. > Ask me how to set up your own Zimbra server. > > - On Oct 8, 2015, at 10:22 PM, Charles Lepple clep...@gmail.com wrote: > >> On O

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

DRT2U do on a real FreeBSD system? -- 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] Can this be done with NUT? (ordered shutdown, revisited)

ng if the "ignorelb" flag is set. Using dummy-ups in repeater mode does sound like a good option. Another potential hitch: while you can override LB, I haven't looked into overriding OB. So for testing, it might be necessary to have a copy of dummy

Re: [Nut-upsuser] OSX El Capitan - Fink - NUT

On Oct 5, 2015, at 12:14 PM, Ian Essendon wrote: > > However, although NUT is apparently stable for Fink under 10.11 (here), an > install fails, with the error > "Can't resolve dependency "system-openssl-dev" for package "nut-2.7.3-1" (no > matching packages/versions

Re: [Nut-upsuser] OSX El Capitan - Fink - NUT

On Oct 5, 2015, at 2:02 PM, Charles Lepple <clep...@gmail.com> wrote:On Oct 5, 2015, at 12:14 PM, Ian Essendon <may...@essendonphoto.com> wrote:However, although NUT is apparently stable for Fink under 10.11 (here), an install fails, with the error I should point out that "

Re: [Nut-upsuser] No power cycle after shutdown on Atlantis Land OnePower A03-S1001

as to when you unplug the power, and when the driver attempts to send the shutdown command? You may be running into this: http://www.networkupstools.org/docs/FAQ.html#_i_8217_m_facing_a_power_race -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing l

Re: [Nut-upsuser] Nut v2.7.3 - how to force shutdown for a specifc ups only

md`. Other instant commands (which may or may not be implemented on your UPS): http://www.networkupstools.org/docs/user-manual.chunked/apcs02.html -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org

Re: [Nut-upsuser] Incorrect values returned from usbhid-ups

tid: 0501 > ups.realpower.nominal: 600 > ups.serial: > ups.status: OL > ups.test.result: Done and passed > ups.timer.shutdown: -60 > ups.timer.start: -60 > ups.vendorid: 0764 > > ___ > Nut-upsuser mailing list > Nut-upsu

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

On Sep 25, 2015, at 9:21 AM, Louis G. <lo...@frentzgzesh.info> wrote: > > For what it is worth, I also have a Cyber Power CP900AVR laying around that I > can test with. That could certainly help narrow down whether it is a problem with the UPS or with the OS. -- Charles Leppl

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

chance that there is something different with NAS4Free's USB stack? Where do they keep their source code repository? Or can you test NUT with actual FreeBSD 10.2 system? -- 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] Configure NUT slaves for D-Link 320 ShareCenter NUT master

could try? Is it possible to get a shell as root? The NUT user/password settings are typically stored in /etc/nut/upsd.users If not, is it stored in the saved configuration settings? http://forums.dlink.com/index.php?topic=41866.msg147229#msg147229 -- Charles Lepple clepple@gmail _

Re: [Nut-upsuser] Configure NUT slaves for D-Link 320 ShareCenter NUT master

k used to build that version of NUT. It might have some insights into how their integration works. -- 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] FreeBSD backed with a PR1500LCDRT2U

75 00 08 00 95 00 01 00 15 00 00 would parse fairly normally if they read as follows: 0.157417 Report Descriptor: (656 bytes) => 05 84 09 04 a1 01 09 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 -- Charles Lepple clepple@gmail ___

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

ore specifically, this dates back to when the first two bytes of an a.out-format executable file were the "magic" values used to determine how to load it. The ASCII code for "#!" does not match any of those magic values, and has the added benefit of being the start of a shell

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

e problem is one level down, in the driver (usbhid-ups). We would need the output from: /usr/local/libexec/nut/usbhid-ups -a Blob -DDD Again, this can get big, so please redirect to a file, gzip, and attach it. -- Charles Lepple clepple@gmail __

Re: [Nut-upsdev] NOTIFYCMD shell script problem driving me NUTS

expand the NUT documentation on this topic. -- 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-upsuser] FreeBSD backed with a PR1500LCDRT2U

ds to be run as root, with the driver stopped.) usbconfig -u 4 -a 2 dump_curr_config_desc -- 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] UPS/NUT with openSUSE 13.1

here an /etc/ld.so.conf or /etc/ld.so.conf.d/* entry pointing to /usr/local/lib64? I am not sure if libusb-0.1 tries to rerun ldconfig after installing, but if after uninstalling libusb-compat, there are problems linking to the real libusb-0.1, then it

Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

need about the first 30 seconds. Please gzip the output before posting to the list. Also, please use reply-all, as this mailing list does not mangle the reply-to headers. -- 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-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb

On Sep 21, 2015, at 7:38 AM, Charles Lepple <clep...@gmail.com> wrote: > > (please keep the list CC'd) > >> On Sep 21, 2015, at 5:09 AM, Uroš Gaber <uros.ga...@gmail.com >> <mailto:uros.ga...@gmail.com>> wrote: >> >> Hi. >> No for me nut

Re: [Nut-upsdev] problem with NOTIFYCMD

o run as root, I would recommend adjusting your firewall accordingly. -- 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-upsuser] UPS/NUT with openSUSE 13.1

On Sep 21, 2015, at 9:39 AM, Rob Groner wrote: > > I didn't think to look for a log (attached), but now looking in it, I don't > see anything more than I already thought I knew. It's as cryptic as > configure itself. > > It does reference the line in the configure where

Re: [Nut-upsdev] Regarding the Asium P700

w.networkupstools.org/docs/man/blazer_usb.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] [HCL] Micropower LCD 1000 supported by blazer_usb

ny regressions? -- 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] [HCL] Asium P700

-spam measures result in mass unsubscription of non-Yahoo email users of these lists. Please consider submitting future information from a non-Yahoo email address, or create an issue on the NUT Github project: https://github.com/networkupstools/nut/issues -- Charles Lepple clepple@gmail ___

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

g to configure nut now I get > "USB drivers requested, but libusb not found", no matter what I put for > --with-usb-libs. Continuing to flog away at it... What's the error message? It might be hidden in config.log, but if you send that, please gzip it first.

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Sep 15, 2015, at 9:31 PM, Charles Lepple <clep...@gmail.com> wrote: > >> Trying to track down the source of the problem, I checked Yast to make sure >> I had at least 0.1.8 version for libusb. I saw this (attached photo). Is >> it then actually using –compat i

Re: [Nut-upsuser] UPS

reciate hearing about that as well: http://www.networkupstools.org/ddl/Cyber_Power_Systems/index.html -- 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] UPS/NUT with openSUSE 13.1

libusb-compat) and "libusb-1.0.so.0" (what libusb-compat calls through to). -- 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] UPS/NUT with openSUSE 13.1

On Sep 16, 2015, at 11:46 AM, Rob Groner wrote: > I then added - to the commandand then it failed, giving me the same > "Can't claim USB" message. Why does adding the debug commands cause a > problem? It doesn't write a PID file in debug mode:

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

ort a busy error. https://github.com/networkupstools/nut/blob/master/drivers/main.c#L588 -- 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] "upsmon -c fsd" cause system shutdown

rol panel, for instance). If you want to experiment with various combinations of OB+LB on multiple UPSes, I would recommend swapping out one or more drivers with dummy-ups. -- 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] stale/dead ups logic

[forwarding to the list] On Sep 14, 2015, at 10:39 PM, d tbsky <tbs...@gmail.com> wrote: > > 2015-09-14 20:34 GMT+08:00 Charles Lepple <clep...@gmail.com>: >> I would recommend investigating ways around the "data stale" error, rather >> than in

Re: [Nut-upsuser] "upsmon -c fsd" cause system shutdown

[please keep the list CC'd - use "Reply All".] On Sep 14, 2015, at 10:29 PM, d tbsky <tbs...@gmail.com> wrote: > > 2015-09-14 20:28 GMT+08:00 Charles Lepple <clep...@gmail.com>: >> "upsmon -c fsd" sets the FSD flag on all of the UPSes attached to ups

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