Charles,
Thanks again for your help. We were able to have a 2.7.2.6 build complied into
a working RPM for CENTOS 6.6. There is one more issue that needs to be
addressed:
The init script no longer works so a new script needs to be written to enable
and disable the ups functionality, however it is communicating with the UPS
properly. The question I have at this point is, is there a way I can set this
so that once Line Power is disrupted it starts the shutdown command on the
system versus waiting for the UPS battery to be "critical"?
Eric K. Cobb
eric_cobb at tripplite.com<mailto:eric_cobb at tripplite.com>
From: Charles Lepple [mailto:clepple at gmail.com]
Sent: Monday, March 23, 2015 10:07 PM
To: Eric Cobb
Cc: nut-upsdev at lists.alioth.debian.org
Subject: Re: CENTOS 6.6 NUT RPM BUILD ISSUES
Importance: High
On Mar 23, 2015, at 7:57 PM, Eric Cobb <Eric_Cobb at
tripplite.com<mailto:Eric_Cobb at tripplite.com>> wrote:
Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am
working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if
they have another way around it. This is code diving which is taking some time.
HAL support in NUT was bit-rotting, so it was removed. It isn't necessary
for the traditional /etc-based configuration method.
Number 2 change -
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/bin/nut-scanner
/usr/sbin/upsdrvctl
A dozen + Man pages
See attached nut.spec (gzipped). Hasn't been tested, but it builds on CentOS
6.6 (after installing the dependencies from the error message the first time I
ran 'rpmbuild -bb').
--
Charles Lepple
clepple at gmail
________________________________
This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150326/dcd9c8ce/attachment.html>
On Mar 26, 2015, at 11:16 AM, Eric Cobb <Eric_Cobb at tripplite.com> wrote:> The init script no longer works so a new script needs to be written to enable and disable the ups functionality, however it is communicating with the UPS properly. The question I have at this point is, is there a way I can set this so that once Line Power is disrupted it starts the shutdown command on the system versus waiting for the UPS battery to be ?critical?? >I would probably just raise the low battery threshold, but to trigger the shutdown immediately, you could write a NOTIFYCMD script for upsmon that looks for the ONBATT event (corresponds to "OB" for ups.status): http://www.networkupstools.org/docs/man/upsmon.html http://www.networkupstools.org/docs/man/upsmon.conf.html -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150326/a3a1ffd6/attachment.html>
That worked out just fine. What I am currently running into are conditions where I am getting the following error that I figured I would share. Error: libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 00 00 00 '.M......' Conditions: upsdrvctl start via Init Script at Boottime. If I run the init script after boot, I do not receive this error. Eric Cobb ekcobb at tripplite.com From: Charles Lepple [mailto:clepple at gmail.com] Sent: Thursday, March 26, 2015 8:59 PM To: Eric Cobb Cc: nut-upsdev at lists.alioth.debian.org Subject: Re: CENTOS 6.6 NUT RPM BUILD ISSUES On Mar 26, 2015, at 11:16 AM, Eric Cobb <Eric_Cobb at tripplite.com<mailto:Eric_Cobb at tripplite.com>> wrote: The init script no longer works so a new script needs to be written to enable and disable the ups functionality, however it is communicating with the UPS properly. The question I have at this point is, is there a way I can set this so that once Line Power is disrupted it starts the shutdown command on the system versus waiting for the UPS battery to be "critical"? I would probably just raise the low battery threshold, but to trigger the shutdown immediately, you could write a NOTIFYCMD script for upsmon that looks for the ONBATT event (corresponds to "OB" for ups.status): http://www.networkupstools.org/docs/man/upsmon.html http://www.networkupstools.org/docs/man/upsmon.conf.html -- Charles Lepple clepple at gmail ________________________________ This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150406/0fe5bd63/attachment.html>