Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying file `./config.guess' libtoolize: copying file `./config.sub' libtoolize: copying file `./install-sh' libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: 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 detected! Terminating other driver! Using subdriver: CyberPower HID 0.3 root at odroid-u2:~/nut# upsc serverups Error: Driver not connected root at odroid-u2:~/nut# How do I run the git one? I guess it's up to date. -Raymond Day On 10/18/2016 9:02 AM, Charles Lepple wrote:> upsc serverups
On Oct 18, 2016, at 9:35 AM, Raymond Day <raymondday at hotmail.com> 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 to install over the Debian one, but I would recommend getting the .deb version configured properly first.
On Oct 18, 2016, at 9:40 AM, Charles Lepple wrote:> > 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 to install over the Debian one, but I would recommend getting the .deb version configured properly first.Did you get the "Duplicate driver instance detected" error resolved? After that, if the Debian driver is still not working, here is the configure line for nut-2.7.1 in Debian - should work for the Git version as well: ./configure --includedir=/usr/include --mandir=/usr/share/man \ --infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var \ --libexecdir=/usr/lib/nut --srcdir=. --disable-maintainer-mode \ --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib/x86_64-linux-gnu \ --with-ssl --with-nss --with-cgi --with-dev --enable-static \ --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/aarch64-linux-gnu/pkgconfig \ --with-user=nut --with-group=nut --with-udev-dir=/lib/udev \ --with-systemdsystemunitdir=/lib/systemd/system (if your email client puts that all on one line, remove the "\" characters)
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 > device.mfr: CPS > device.model: SX650G > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.version: 2.6.4 > driver.version.data: CyberPower HID 0.3 > driver.version.internal: 0.37 > input.transfer.high: 0 > input.transfer.low: 0 > input.voltage: 121.0 > input.voltage.nominal: 120 > output.voltage: 121.0 > ups.beeper.status: enabled > ups.delay.shutdown: 20 > ups.delay.start: 30 > ups.load: 0 > ups.mfr: CPS > ups.model: SX650G > ups.productid: 0501 > ups.realpower.nominal: 375 > ups.status: OL > ups.test.result: No test initiated > ups.timer.shutdown: -60 > ups.timer.start: 0 > ups.vendorid: 0764 > > So looks like it's working Thank you. Were is the page I ask for this > help? This e-mail don't have the link looks like. > > -Raymond Day > > > On 10/26/2016 8:55 AM, Charles Lepple wrote: >> On Oct 18, 2016, at 9:40 AM, Charles Lepple wrote: >>> 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 to install over the Debian one, but I would recommend getting the .deb version configured properly first. >> Did you get the "Duplicate driver instance detected" error resolved? >> >> After that, if the Debian driver is still not working, here is the configure line for nut-2.7.1 in Debian - should work for the Git version as well: >> >> ./configure --includedir=/usr/include --mandir=/usr/share/man \ >> --infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var \ >> --libexecdir=/usr/lib/nut --srcdir=. --disable-maintainer-mode \ >> --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib/x86_64-linux-gnu \ >> --with-ssl --with-nss --with-cgi --with-dev --enable-static \ >> --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \ >> --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ >> --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut \ >> --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/aarch64-linux-gnu/pkgconfig \ >> --with-user=nut --with-group=nut --with-udev-dir=/lib/udev \ >> --with-systemdsystemunitdir=/lib/systemd/system >> >> (if your email client puts that all on one line, remove the "\" characters) >
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 goes to low? -Raymond Day On 10/27/2016 8:37 AM, Charles Lepple wrote:>> On Oct 27, 2016, at 6:43 AM, Raymond Day <raymondday at hotmail.com> wrote: >> >> So looks like it's working Thank you. Were is the page I ask for this >> help? This e-mail don't have the link looks like. > You're welcome. The links don't get sent if you're on the "To:" or "CC:" list, but here they are: > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
On Oct 27, 2016, at 10:18 PM, Raymond Day wrote:> > Is there a way to test if it will turn off my server when the battery > power goes to low?http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns
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 goes to low? > >-Raymond Day > > >On 10/27/2016 8:37 AM, Charles Lepple wrote: >>> On Oct 27, 2016, at 6:43 AM, Raymond Day <raymondday at hotmail.com> >wrote: >>> >>> So looks like it's working Thank you. Were is the page I ask for >this >>> help? This e-mail don't have the link looks like. >> You're welcome. The links don't get sent if you're on the "To:" or >"CC:" list, but here they are: >> >> _______________________________________________ >> Nut-upsdev mailing list >> Nut-upsdev at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev > > >_______________________________________________ >Nut-upsdev mailing list >Nut-upsdev at lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdevA short answer might be to set up upsmon with a custom SHUTDOWNCMD that would report (log) that/when it is going to shutdown. Except for the test it will not actually shut down, just report. For a larger integration test, involving actual shutdowns (and how long they take - so you know how much runtime + headspace your ups must have remaining to trigger the event) and perhaps poweroff of the UPS and whether it comes back up when wallpower comes back, you might stage a real production shutdown. Also, to test just the UPS part you do not have to powercycle the server - you can run the upscmd's involved in the shutdown routine against the UPS which is not actually powering your system at the moment. Note that some UPSes do require non-trivial load to operate - then perhaps a display might suffice, or one of redundant server PSUs. Hope this helps, Jim Klimov -- Typos courtesy of K-9 Mail on my Samsung Android