Hi Charles, Tim, Ah, thanks for bit about the dependencies. Would have thought them to be version specific. Tried with the client and server debs but it seems too many dependency differences between wheezy and jessie. I also tried upgrading from wheezy to jessie wholesale to see if that worked and it did solve nut but in the process broke something else that's more critical so I'll give the following another try: 1) try Tim's suggestion of searching for the "new" upsdrvctl or failing that, 2) uninstalling 2.6.5 and then installing 2.7.4 via tar Cheers On 3 August 2017 at 19:21, Charles Lepple <clepple at gmail.com> wrote:> On Aug 3, 2017, at 5:35 AM, Song Teck <songteck at gmail.com> wrote: > > > > That package is supposed to install both server and client (according to > the description at https://packages.debian.org/stretch/nut anyway). I'll > try both server and client individually later and see if that helps. > > > Right, but only if you install it via apt. If you install the 2.7.4 .deb > with dpkg, and you have the 2.6.4 nut-client and nut-server .debs > installed, the dependencies are satisfied. (The nut metapackage does not > depend on specific versions.)-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170804/665292b6/attachment.html>
Hi Charles, Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the shutdown sequence to work properly. Have been following this: http://networkupstools.org/docs/user-manual.chunked/ar01s06.html Unit performs as described in the "Testing shutdowns" section. I have another question that I am hoping to get some clarification with. The ups unit does not transit into OB LB even when Battery Charge falls below the LB level. The unit does initiate power off properly when Battery Charge/Runtime reaches 0. Is this correct? Or should there be an earlier transition and shutdown triggered by OB LB? I have also not been able to successfully get NOTIFYMSG or NOTIFYFLAG to work successfully although I suspect that has to do with my configuration of NOTIFYCMD. Will pursue that a little more. Cheers On 4 August 2017 at 20:09, Song Teck <songteck at gmail.com> wrote:> Hi Charles, Tim, > > Ah, thanks for bit about the dependencies. Would have thought them to be > version specific. > > Tried with the client and server debs but it seems too many dependency > differences between wheezy and jessie. I also tried upgrading from wheezy > to jessie wholesale to see if that worked and it did solve nut but in the > process broke something else that's more critical so I'll give the > following another try: > > 1) try Tim's suggestion of searching for the "new" upsdrvctl or failing > that, > 2) uninstalling 2.6.5 and then installing 2.7.4 via tar > > Cheers > > On 3 August 2017 at 19:21, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 3, 2017, at 5:35 AM, Song Teck <songteck at gmail.com> wrote: >> > >> > That package is supposed to install both server and client (according >> to the description at https://packages.debian.org/stretch/nut anyway). >> I'll try both server and client individually later and see if that helps. >> > >> Right, but only if you install it via apt. If you install the 2.7.4 .deb >> with dpkg, and you have the 2.6.4 nut-client and nut-server .debs >> installed, the dependencies are satisfied. (The nut metapackage does not >> depend on specific versions.) > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170815/62ba447b/attachment.html>
On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote:> > Hi Charles, > > Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the shutdown sequence to work properly. > > Have been following this: http://networkupstools.org/docs/user-manual.chunked/ar01s06.html > Unit performs as described in the "Testing shutdowns" section. > > I have another question that I am hoping to get some clarification with. > > The ups unit does not transit into OB LB even when Battery Charge falls below the LB level. The unit does initiate power off properly when Battery Charge/Runtime reaches 0. > Is this correct? Or should there be an earlier transition and shutdown triggered by OB LB?The driver should recognize one of several standard shutdown notifications: https://github.com/networkupstools/nut/blob/v2.7.2-signed/drivers/openups-hid.c#L300-L302 However, I don't know which of these is actually implemented in the firmware. If you can afford some downtime, you can capture a log as the battery discharges - let us know if you want to try that. To synthesize the OB+LB state, you can use the "ignorelb" flag with override.battery.charge.low and/or override.battery.runtime.low as described in http://networkupstools.org/docs/man/ups.conf.html You mentioned that the UPS powers off by itself when the charge reaches 0. Note that there does not seem to be a way to tell it to power off early with a command from NUT (e.g. "upsdrvctl shutdown", which gets translated to "/path/to/driver ... -k").> > I have also not been able to successfully get NOTIFYMSG or NOTIFYFLAG to work successfully although I suspect that has to do with my configuration of NOTIFYCMD. Will pursue that a little more.I'd recommend a separate email thread for that, and check Roger Price's writeup for further information: http://rogerprice.org/NUT.html