Two quick and simple questions; I want to install the "WinPower" software for my new UPS. On their web site, they have a tar.gz file available for download. I know the reasons for staying with RPM, if at all possible. I've Googled and Yahood for ""WinPower"+RPM+Linux and get hits, but no obvious RPM. I tried "yum install winpower" and the response was "no package winpower available" (rpmforge is one of the yum repositories I use, so it's not there, with that name).
(a) Is an RPM available for it? (If so, where and what's the name?) (b) If I need to download the tar.gz file and install from that, it looks from their documentation that they install into /opt/MonitorSoftware Is it better to install into /usr/local or into /opt? What is the recommendation for a CentOS box, when installing non RPM software? Where best to install non RPM stuff? TIA!
I tried "yum install winpower" and the response was "no package winpower available" (rpmforge is one of the yum repositories I use, so it's not there, with that name).
It's not, but that search method could be expanded: # yum list *winpower* # yum list *win* # yum list *win* |grep -i <you get the picture...> etc etc
Try Apcupsd, it is a very complete enterprisable package that just runs well.
jlc
On 2/27/09, Joseph L. Casale JCasale@activenetwerx.com wrote:
I tried "yum install winpower" and the response was "no package winpower available" (rpmforge is one of the yum repositories I use, so it's not there, with that name).
It's not, but that search method could be expanded: # yum list *winpower* # yum list *win* # yum list *win* |grep -i <you get the picture...> etc etc
Try Apcupsd, it is a very complete enterprisable package that just runs well.
Thank you. I will give apcupsd a shot. We don't have any APC units, but, possibly, it will work with our UPS. If not, I will try to get WinPower running properly. I will also try your suggestions for searching with yum.
Thank you. I will give apcupsd a shot. We don't have any APC units, but, possibly, it will work with our UPS. If not, I will try to get WinPower running properly. I will also try your suggestions for searching with yum.
I forgot to mention Network UPS Tools (NUT). That also works with many. jlc
On 2/27/09, Joseph L. Casale JCasale@activenetwerx.com wrote:
Thank you. I will give apcupsd a shot. We don't have any APC units, but, possibly, it will work with our UPS. If not, I will try to get WinPower running properly. I will also try your suggestions for searching with yum.
I forgot to mention Network UPS Tools (NUT). That also works with many.
NUT is the one Anne is trying to get to work with her Leibert (sp?) UPS. I will try apcupsd first. On Wikipedia they say it works with some OEM UPS too. Possibly with ours.... Thanks! I did search on yum with your search suggestions, but no joy.
On 2/27/09, Joseph L. Casale JCasale@activenetwerx.com wrote:
Thank you. I will give apcupsd a shot. We don't have any APC units, but, possibly, it will work with our UPS. If not, I will try to get WinPower running properly. I will also try your suggestions for searching with yum.
I forgot to mention Network UPS Tools (NUT). That also works with many.
I've got the package below installed now. Is that the right one? Now, I need to RFM to find out how to configure and run it....
Running Transaction Installing: perl-UPS-Nut ######################### [1/1] Installed: perl-UPS-Nut.noarch 0:0.04-1.el5.rf Complete!
Lanny Marcus wrote:
I've got the package below installed now. Is that the right one? Now, I need to RFM to find out how to configure and run it....
it's only part of it, typically there are 3 nut packages, one for perl, one for the main nut, and one that contains cgi scripts(sometimes another one specifically for usb).
First I would check what version of NUT your installing and try to validate whether or not your UPS is supported by checking the homepage:
http://www.networkupstools.org/
I've been running NUT against APC and Cyberpower UPSs for about 8 years now. I especially like the CGI interface where I can aggregate several UPSs from different systems into a single web page that I can monitor without needing authentication.
Sample: http://portal.aphroland.org/ (I hacked the cgi up years ago so I could embed it in pages, and still pass w3c validation, wee)
nate
On 2/27/09, nate centos@linuxpowered.net wrote:
I've got the package below installed now. Is that the right one? Now, I need to RFM to find out how to configure and run it....
it's only part of it, typically there are 3 nut packages, one for perl, one for the main nut, and one that contains cgi scripts(sometimes another one specifically for usb).
First I would check what version of NUT your installing and try to validate whether or not your UPS is supported by checking the homepage:
Nate: Thank you. I will RFM the documentation for nut (hopefully I can download a .pdf file for it) and then try to get the right packages. If it doesn't support my UPS then I'll download the 45.2 MB tarball for WinPower. Lanny
On 2/27/09, Lanny Marcus lmmailinglists@gmail.com wrote:
On 2/27/09, nate centos@linuxpowered.net wrote:
<snip>
First I would check what version of NUT your installing and try to validate whether or not your UPS is supported by checking the homepage:
The Nicomar Electronics UPS we bought a few weeks ago (made in Bogota, Colombia) is not on their list. I suspect nut might work with it, but, maybe not.... <snip>
I just finished downloading the WinPower tarball (from Taiwan). 45.3 MB. I will install it over the weekend.
Thanks much to everyone! Greatly appreciated
On 2/27/09, Lanny Marcus lmmailinglists@gmail.com wrote:
On 2/27/09, Joseph L. Casale JCasale@activenetwerx.com wrote:
<snip>
I forgot to mention Network UPS Tools (NUT). That also works with many.
I've got the package below installed now. Is that the right one? Now, I need to RFM to find out how to configure and run it....
Running Transaction Installing: perl-UPS-Nut ######################### [1/1] Installed: perl-UPS-Nut.noarch 0:0.04-1.el5.rf Complete!
I doubt the one above is the correct one. Lots of stuff available for nut, but I'm not sure which is the right one for me and where to get it. (CentOS 5.2, 32 bit). If I can't get this to go, I will download the tarball for WinPower (45.2 MB) and install that over the weekend.
I've got the package below installed now. Is that the right one?
No
Running Transaction Installing: perl-UPS-Nut ######################### [1/1] Installed: perl-UPS-Nut.noarch 0:0.04-1.el5.rf Complete!
Slow down a bit son, anything with a "Perl-" in the front is, well, a perl module:)
You should have done a yum info first.
# yum info perl-UPS-Nut.noarch Name : perl-UPS-Nut Arch : noarch Version: 0.04 Release: 1.el5.rf Size : 24 k Repo : rpmforge Summary: Perl module to talk to a UPS via Network UPS Tools (NUT) upsd Description: perl-UPS-Nut is a Perl module to talk to a UPS via NUT (Network UPS Tools) upsd.
This package contains the following Perl module:
UPS::Nut
Looks like rpmfind doesn't show any for RHEL :/ You might have to roll your own. Let's try and get Apcupsd working first, your config was wrong to start so its worth trying again.
jlc
Hi,
On Fri, Feb 27, 2009 at 19:39, Joseph L. Casale JCasale@activenetwerx.com wrote:
Looks like rpmfind doesn't show any for RHEL :/ You might have to roll your own. Let's try and get Apcupsd working first, your config was wrong to start so its worth trying again.
NUT RPMs seems to be available from EPEL. NUT 2.2.0 is available for CentOS 5. Here are the i386 RPMs: http://download.fedora.redhat.com/pub/epel/5/i386/repoview/nut.html
HTH, Filipe
On Sat, Feb 28, 2009 at 1:40 AM, Filipe Brandenburger filbranden@gmail.com wrote:
On Fri, Feb 27, 2009 at 19:39, Joseph L. Casale JCasale@activenetwerx.com wrote:
Looks like rpmfind doesn't show any for RHEL :/ You might have to roll your own. Let's try and get Apcupsd working first, your config was wrong to start so its worth trying again.
NUT RPMs seems to be available from EPEL. NUT 2.2.0 is available for CentOS 5. Here are the i386 RPMs: http://download.fedora.redhat.com/pub/epel/5/i386/repoview/nut.html
Filipe: Thank you! I will add the EPEL Repository and get the nut rpms there. That should be a lot easier than "rolling my own" (and much faster, since I've never done that), which Joe said I might need to do. Lanny
On Sat, Feb 28, 2009 at 1:40 AM, Filipe Brandenburger filbranden@gmail.com wrote:
On Fri, Feb 27, 2009 at 19:39, Joseph L. Casale JCasale@activenetwerx.com wrote:
Looks like rpmfind doesn't show any for RHEL :/ You might have to roll your own. Let's try and get Apcupsd working first, your config was wrong to start so its worth trying again.
NUT RPMs seems to be available from EPEL. NUT 2.2.0 is available for CentOS 5. Here are the i386 RPMs: http://download.fedora.redhat.com/pub/epel/5/i386/repoview/nut.html
I just installed the repo file for EPEL (and gave it a very low priority). I installed nut and nut-client from EPEL. When I try to start the ups daemon, I get the below error:
ups failed. The error was: Starting UPS driver controller: [FAILED]
Starting upsd: [FAILED]
Starting UPS monitor (master): [FAILED]
If I can't get apcupsd or nut configured properly, then I will try the WinPower software the UPS manufacturer (and many others) specify. I have the tar ball on my hard drive (45.3 MB) and maybe I can "roll my own" RPM for the first time.
On Sun, Mar 1, 2009 at 11:42 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
On Sat, Feb 28, 2009 at 1:40 AM, Filipe Brandenburger filbranden@gmail.com wrote:
<snip>
NUT RPMs seems to be available from EPEL. NUT 2.2.0 is available for CentOS 5. Here are the i386 RPMs: http://download.fedora.redhat.com/pub/epel/5/i386/repoview/nut.html
<snip>
If I can't get apcupsd or nut configured properly, then I will try the WinPower software the UPS manufacturer (and many others) specify. I have the tar ball on my hard drive (45.3 MB) and maybe I can "roll my own" RPM for the first time.
I would like to "roll my own" RPM for the WinPower UPS monitoring software. Never done this before. I have the WinPower tarball on my box. I have installed the development tools. I followed Filipe's How to: http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment and these commands: mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} echo '%_topdir %(echo $HOME)/rpmbuild' > ~/.rpmmacros (for a non root user)
Questions: (1) After I unzip the WinPower tarball, what command(s) do I use to create an RPM for WinPower? (2) Is there any need to install the development kernel for this? (This is a fully updated CentOS 5.2 box, 32 bit)
TIA!
On Sun, Mar 1, 2009 at 1:00 PM, Lanny Marcus lmmailinglists@gmail.com wrote:
On Sun, Mar 1, 2009 at 11:42 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
On Sat, Feb 28, 2009 at 1:40 AM, Filipe Brandenburger filbranden@gmail.com wrote:
<snip> >> NUT RPMs seems to be available from EPEL. NUT 2.2.0 is available for >> CentOS 5. Here are the i386 RPMs: >> http://download.fedora.redhat.com/pub/epel/5/i386/repoview/nut.html <snip> > If I can't get apcupsd or nut configured properly, then I will try > the WinPower software the UPS manufacturer (and many others) specify. > I have the tar ball on my hard drive (45.3 MB) and maybe I can "roll > my own" RPM for the first time. > I would like to "roll my own" RPM for the WinPower UPS monitoring software. Never done this before. I have the WinPower tarball on my box. I have installed the development tools. I followed Filipe's How to: <http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment> and these commands: mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} echo '%_topdir %(echo $HOME)/rpmbuild' > ~/.rpmmacros (for a non root user)
Questions: (1) After I unzip the WinPower tarball, what command(s) do I use to create an RPM for WinPower? (2) Is there any need to install the development kernel for this? (This is a fully updated CentOS 5.2 box, 32 bit)
Follow on: Neither of the 2 books I have for reference explain how to do this. Looks like the SPEC file is the biggest mystery for me. I discovered rpm.org and will do some online reading about RPM there.
On Sun, 2009-03-01 at 15:06 -0500, Lanny Marcus wrote:
On Sun, Mar 1, 2009 at 1:00 PM, Lanny Marcus lmmailinglists@gmail.com wrote:
On Sun, Mar 1, 2009 at 11:42 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
...
I would like to "roll my own" RPM for the WinPower UPS monitoring software. Never done this before. I have the WinPower tarball on my box. I have installed the development tools. I followed Filipe's How to: http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment and these commands: mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} echo '%_topdir %(echo $HOME)/rpmbuild' > ~/.rpmmacros (for a non root user)
Questions: (1) After I unzip the WinPower tarball, what command(s) do I use to create an RPM for WinPower? (2) Is there any need to install the development kernel for this? (This is a fully updated CentOS 5.2 box, 32 bit)
Follow on: Neither of the 2 books I have for reference explain how to do this. Looks like the SPEC file is the biggest mystery for me. I discovered rpm.org and will do some online reading about RPM there.
Long ago on a planet far away... (-: or was that near the beginning of this thread? :-) checkinstall was mentioned.
less /usr/share/doc/checkinstall-1.6.0/README less /usr/share/doc/checkinstall-1.6.0/FAQ checkinstall --help
May be a moot point given other recent posts in the thread, but for creating an RPM from scratch see: http://genetikayos.com/code/repos/rpm-tutorial/trunk/rpm-tutorial.html
If a spec file is included then "rpmbuild -ta tarballname.tgz" may work.
Rolling your own RPM if a spec file is not included in the tarball is an exercise left for the student RPM builder.
Phil
On Mon, Mar 2, 2009 at 6:29 AM, Phil Schaffner P.R.Schaffner@ieee.org wrote:
On Sun, Mar 1, 2009 at 11:42 AM, Lanny Marcus lmmailinglists@gmail.com wrote:
<snip>
discovered rpm.org and will do some online reading about RPM there.
Long ago on a planet far away... (-: or was that near the beginning of this thread? :-) checkinstall was mentioned.
By you and I installed it, shortly after I read your post. Thanks!
less /usr/share/doc/checkinstall-1.6.0/README less /usr/share/doc/checkinstall-1.6.0/FAQ checkinstall --help
May be a moot point given other recent posts in the thread, but for creating an RPM from scratch see: http://genetikayos.com/code/repos/rpm-tutorial/trunk/rpm-tutorial.html
Thank you for that link. I will read it later.
If a spec file is included then "rpmbuild -ta tarballname.tgz" may work.
If that's all it takes, with a spec file, easy.
As you probably know, when I looked at the contents of the tarball yesterday, it was a lot of JRE stuff. No source, no spec file. When I need something that isn't packaged and I try to roll my first package, I need at least the Binary and hopefully the Source. Open Source :-)
Rolling your own RPM if a spec file is not included in the tarball is an exercise left for the student RPM builder.
I did some reading yesterday of a book about RPM on rpm.org and writing a spec file looks like something that may involve a lot of trial and especially error, to get it correct.
With regard to the UPS, will look into nuts and apcupds more when I can, to see if I can figure out how to configure them for this UPS. We still have one Tripp Lite UPS that works, so I need to get their SW and see if it will shutdown that box.
When I try to start the ups daemon, I get the below error:
ups failed. The error was: Starting UPS driver controller: [FAILED]
Starting upsd: [FAILED]
Starting UPS monitor (master): [FAILED]
I have never used NUT before, I just knew it existed. Apcupsd has always done what I need but I would check the logs, I have no doubt they would show what is wrong. Have made any initial config? Check http://eu1.networkupstools.org/doc/2.2.0/README.html Read the FAQ: Once the config files are ready, start upsd: # /usr/local/ups/sbin/upsd -u nutsrv Check your syslog
If I can't get apcupsd or nut configured properly, then I will try the WinPower software the UPS manufacturer (and many others) specify.
Look here: http://www.apcupsd.com And here is a possible config: http://www.apcupsd.com/manual/Configuration_Examples.html#SECTION00013300000...
I have the tar ball on my hard drive (45.3 MB) and maybe I can "roll my own" RPM for the first time.
You need to write a spec file, then use rpmbuild to make the rpm. Google should hopefully provide the guidance this needs, you can also ckeck the spec from any src.rpm file you can get by extracting the contents: rpm2cpio example.src.rpm | cpio -dimv The look for the spec.
jlc
Ps. My guess you:)
On Sun, Mar 1, 2009 at 3:06 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
When I try to start the ups daemon, I get the below error:
ups failed. The error was: Starting UPS driver controller: [FAILED] Starting upsd: [FAILED] Starting UPS monitor (master): [FAILED]
I have never used NUT before, I just knew it existed. Apcupsd has always done what I need but I would check the logs, I have no doubt they would show what is wrong. Have made any initial config?
Joe: Thank you for replying again! This is a learning experience for me. I just finished getting at the WinPower Linux stuff. Not at all what I expected! Everything seems to be JRE. I didn't see any Linux source files, etc., so now I assume that it is not open source and this is not the software for me to learn how to "roll my own" RPM with. With some other software, another day, I will begin to learn about packaging. I just installed WinPower, the Software specified by the UPS manufacturer, the old fashioned (non RPM way) which is highly not recommended. After I send this email, I will try to configure it and see if it works properly. If not, back to apcupsd and nut..... I'm going to cut out the rest of your reply. I read part of a book on rpm.org so now I have the beginnings of understanding how to package something. Your help is much appreciated! Lanny <snip>
On Sun, Mar 1, 2009 at 4:43 PM, Lanny Marcus lmmailinglists@gmail.com wrote:
On Sun, Mar 1, 2009 at 3:06 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
When I try to start the ups daemon, I get the below error:
ups failed. The error was: Starting UPS driver controller: [FAILED] Starting upsd: [FAILED] Starting UPS monitor (master): [FAILED]
<snip>
Joe: Thank you for replying again! This is a learning experience for me. I just finished getting at the WinPower Linux stuff. Not at all what I expected! Everything seems to be JRE. I didn't see any Linux source files, etc., so now I assume that it is not open source and
<snip>
I have the WinPower UPS monitoring SW running OK on Linux. Voltage in and out is 122 and the maximum load I saw was 47%. I need to do a simulated power failure, to verify that it will in fact shutdown the box after 2 minutes! Still curious about nut and apcupsd and learning how to package. Thanks to everyone who replied!
I need to do a simulated power failure, to verify that it will in fact shutdown the box after 2 minutes!
Plug the PC into a stable power source, let the same PC monitor the UPS. Unplug the UPS and place a load on it, watch what it instructs the PC to do :)
Check your halt scripts for a command to drop the power in the UPS *after* your root remounts ro and hopefully your ups supports this and your bios powers up after power returns so when the outage is over, everything returns to normal.
Still curious about nut and apcupsd and learning how to package. Thanks to everyone who replied!
I would be as well:) Apcupsd and NUT are both stable, popular and well documented projects. I am not sure about the one you are using...
jlc
On Sun, Mar 1, 2009 at 5:43 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
I need to do a simulated power failure, to verify that it will in fact shutdown the box after 2 minutes!
Plug the PC into a stable power source, let the same PC monitor the UPS. Unplug the UPS and place a load on it, watch what it instructs the PC to do :)
I plugged the UPS into a surge protector and after awhile, I cut the power to the UPS. The UPS continued to supply power to the box and monitor and the alarm beeped. All OK. But, the WinPower software supplied for the UPS did *not* shut the box down, after 2 minutes of power failure, as I expected. The reason I installed the WinPower SW was so it could shut down the box.... Here's the output:
[lanny@dell2400 Winpower]$ ./monitor Starting Winpower Manager: Done [lanny@dell2400 Winpower]$ Broadcast message from root (Sun Mar 1 18:03:28 2009): /usr/local/Winpower/UPSPILOT.TRA Broadcast message from root (Sun Mar 1 18:03:28 2009): Winpower Message: LINE-INT in /dev/ttyS0 input power failed Broadcast message from root (Sun Mar 1 18:08:52 2009): Winpower Message: LINE-INT in /dev/ttyS0 input power restored. Broadcast message from root (Sun Mar 1 18:08:52 2009): /usr/local/Winpower/UPSPILOT.TRA
As you can see, I killed the power to the UPS for 5 minutes, but the WinPower SW did *not* shut down the box. The monitoring part of the WinPower SW works well, but their default settings are for it to shutdown the box if the battery is low or after a 2 minute power failure.
I will RFM the WinPower manual, but if I don't find a solution there, there's nobody to contact, so then nut and apcupsd become much more interesting, again..... <snip>
bios powers up after power returns so when the outage is over, everything returns to normal.
BIOS is set to power up the box when power is restored. <snip.
I would be as well:) Apcupsd and NUT are both stable, popular and well documented projects. I am not sure about the one you are using...
The WinPower software for the UPS is apparently proprietary and I don't see a way to contact them. That's the best way for them to do it. If users have problems, the problems are for the users and they don't have to support the users. :-)
On Sun, 2009-03-01 at 18:41 -0500, Lanny Marcus wrote:
On Sun, Mar 1, 2009 at 5:43 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
I need to do a simulated power failure, to verify that it will in fact shutdown the box after 2 minutes!
Plug the PC into a stable power source, let the same PC monitor the UPS. Unplug the UPS and place a load on it, watch what it instructs the PC to do :)
I plugged the UPS into a surge protector and after awhile, I cut the
OOPS!? It used to be that the manual for all the UPSs I've used said to _not_ plug it into a surge suppressor, IIRC. Has that changed? It had something to do with the wave form from the suppressor vs. the box's monitoring circuitry.
I don't think that has anything to do with not shutting down though.
power to the UPS. The UPS continued to supply power to the box and monitor and the alarm beeped. All OK. But, the WinPower software supplied for the UPS did *not* shut the box down, after 2 minutes of power failure, as I expected.<snip>
On Mon, Mar 2, 2009 at 4:43 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Sun, 2009-03-01 at 18:41 -0500, Lanny Marcus wrote:
On Sun, Mar 1, 2009 at 5:43 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
I need to do a simulated power failure, to verify that it will in fact shutdown the box after 2 minutes!
Plug the PC into a stable power source, let the same PC monitor the UPS. Unplug the UPS and place a load on it, watch what it instructs the PC to do :)
I plugged the UPS into a surge protector and after awhile, I cut the
OOPS!? It used to be that the manual for all the UPSs I've used said to _not_ plug it into a surge suppressor, IIRC. Has that changed? It had something to do with the wave form from the suppressor vs. the box's monitoring circuitry.
You are correct. Normally, each of our UPS is plugged directly into a wall outlet. I plugged mine into a surge protector, to do the simulated power failure for to see if it would shutdown the box.
I don't think that has anything to do with not shutting down though.
Either the WinPower SW will not shut down the box after 2 minutes or there is something unclear to me about the settings. I read their documentation again and everything is set to their default settings, which looks like it should shut down the box after a 2 minute power failure. <snip> This was a lesson for me, about the many advantages of Open Source, rather than Proprietary SW. When I looked at the contents of the tarball and saw a lot of JRE stuff, and no Source code, I was disappointed. They wrote it, they sold it to a bunch of companies that make UPS, but they do not support it. No community. Probably the only other Proprietary SW I have installed is Google's Picasa and Earth, but they have Community, if one should have a problem, which I haven't had.
Lanny Marcus wrote:
Either the WinPower SW will not shut down the box after 2 minutes or there is something unclear to me about the settings. I read their documentation again and everything is set to their default settings, which looks like it should shut down the box after a 2 minute power failure.
Maybe the engrish docs weren't clear, could it be possible that the software will not shut down until there are 2 minutes left on the battery instead of 2 minutes after an outage? With most UPSs I have used the default is to not to issue a shut down until the battery condition is low.
Try the test again and let the UPS run until the battery runs out and see if it ever shuts down.
nate
On Mon, Mar 2, 2009 at 12:37 PM, nate centos@linuxpowered.net wrote:
Lanny Marcus wrote:
Either the WinPower SW will not shut down the box after 2 minutes or there is something unclear to me about the settings. I read their documentation again and everything is set to their default settings, which looks like it should shut down the box after a 2 minute power failure.
Maybe the engrish docs weren't clear, could it be possible that the software will not shut down until there are 2 minutes left on the battery instead of 2 minutes after an outage? With most UPSs I have used the default is to not to issue a shut down until the battery condition is low.
Try the test again and let the UPS run until the battery runs out and see if it ever shuts down.
Hmmmm. You may be on to something with that idea! :-) When I downloaded the SW (45.3 MB, which is enormous, compared to nut or apcupsd), I did a traceroute on the domain and it ended in .tw (Taiwan). I will try testing it your way and see what happens.... BTW, years ago, I worked with a bunch of people from Taiwan and they were pretty sharp. This WinPower SW is *much* more basic in what it does than what we were doing in Assembly Language on barefoot mini computers.
On Fri, Feb 27, 2009 at 7:39 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
I've got the package below installed now. Is that the right one?
No
Running Transaction Installing: perl-UPS-Nut ######################### [1/1] Installed: perl-UPS-Nut.noarch 0:0.04-1.el5.rf Complete!
Slow down a bit son, anything with a "Perl-" in the front is, well, a perl module:)
After I clicked send, immediately after I clicked send, I realized that it was a perl module. That's the only nut package I came up with, when I searched with yum, so I didn't have the proper search terms.
You should have done a yum info first.
# yum info perl-UPS-Nut.noarch
<snip>
Summary: Perl module to talk to a UPS via Network UPS Tools (NUT) upsd Description: perl-UPS-Nut is a Perl module to talk to a UPS via NUT (Network UPS Tools) upsd.
This package contains the following Perl module:
UPS::Nut
Looks like rpmfind doesn't show any for RHEL :/ You might have to roll your own. Let's try and get Apcupsd working first, your config was wrong to start so its worth trying again.
Thank you! I feel better about not finding the packages for nut, when I searched with yum! :-) I hope apcupsd will work with this UPS, if I can configure it properly.
I will try apcupsd again. What should I change in the config for apcupsd?
Just a little bit of knowledge, which is what I have about Linux, can be *extremely* dangerous.... I had come up with the idea that I might need to "roll" my own package(s) for nut, but I will really need to RFM before even thinking about trying to do that, because I'm not sure what that involves.... I have 2 books: "Running Linux" and "Red Hat Fedora and Enterprise Linux 4 Bible" which probably will explain that, along with the CentOS Wiki. The development tools are installed on this box, if I need them to do that.
Joe: Thank you very much. And you called me "son". Who is older? :-) Lanny
On 2/27/09, Joseph L. Casale JCasale@activenetwerx.com wrote:
I tried "yum install winpower" and the response was "no package winpower available" (rpmforge is one of the yum repositories I use, so it's not there, with that name).
<snip>
Try Apcupsd, it is a very complete enterprisable package that just runs well.
Apcupsd apparently runs with some of the UPS not made by APC, but looks like it will not work with mine. Here's what's in the Service data for apcupsd:
apcupsd (pid 6568) is running... Error contacting host localhost port 3551: Connection refused
I'll stop that daemon, uninstall it and install nut. I like the name better and hopefully it will work with this UPS.....
Apcupsd apparently runs with some of the UPS not made by APC, but looks like it will not work with mine. Here's what's in the Service data for apcupsd:
apcupsd (pid 6568) is running... Error contacting host localhost port 3551: Connection refused
That doesn't mean it can't contact your ups, that means you have it setup wrong:)
What interface does your ups use? Serial, ether, usb? What model #?
jlc
On Fri, Feb 27, 2009 at 7:32 PM, Joseph L. Casale JCasale@activenetwerx.com wrote:
Apcupsd apparently runs with some of the UPS not made by APC, but looks like it will not work with mine. Here's what's in the Service data for :
apcupsd (pid 6568) is running... Error contacting host localhost port 3551: Connection refused
That doesn't mean it can't contact your ups, that means you have it setup wrong:)
What interface does your ups use? Serial, ether, usb? What model #?
Serial port communications. It is made by Nicomar Electronics in Bogota, Colombia. 750 VA Line Interactive UPS. The software they say to use (WinPower) is apparently widely used, by Belkin UPS and many others. The WinPower software download site is in Taiwan, so now I wonder whether or not they just sell the software to the OEMs or if they manufacturer the UPS and put a brand name on them and ship them from Taiwan....
apcupsd was very easy to install with yum and the documentation for it is easy to download. nut is a different story and not so easy to know what to download. And, I didn't see a .pdf file I could download with the nut documentation.
Lanny Marcus wrote: ...
(b) If I need to download the tar.gz file and install from that, it looks from their documentation that they install into /opt/MonitorSoftware Is it better to install into /usr/local or into /opt? What is the recommendation for a CentOS box, when installing non RPM software? Where best to install non RPM stuff? TIA!
I prefer /usr/local and that seems to be more common, but either should work. As for tarball installs - to be avoided if possible - there's always checkinstall.
Name : checkinstall Arch : i386 Version: 1.6.0 Release: 3.el5.rf Size : 82 k Repo : rpmforge Summary: CheckInstall installations tracker Description: CheckInstall keeps track of all the files created or modified by your installation script ("make install" "make install_modules", "setup", etc), builds a standard binary package and installs it in your system giving you the ability to uninstall it with your distribution's standard package management utilities.
Phil
On 2/27/09, Phil Schaffner Philip.R.Schaffner@nasa.gov wrote:
Lanny Marcus wrote:
(b) If I need to download the tar.gz file and install from that, it looks from their documentation that they install into /opt/MonitorSoftware Is it better to install into /usr/local or into /opt? What is the recommendation for a CentOS box, when installing non RPM software? Where best to install non RPM stuff? TIA!
I prefer /usr/local and that seems to be more common, but either should work. As for tarball installs - to be avoided if possible
Phil: Thank you. /usr/local if I need to install tarballs. Which I avoid, if possible!
- there's
always checkinstall.
Name : checkinstall Arch : i386 Version: 1.6.0 Release: 3.el5.rf Size : 82 k Repo : rpmforge Summary: CheckInstall installations tracker Description: CheckInstall keeps track of all the files created or modified by your installation script ("make install" "make install_modules", "setup", etc), builds a standard binary package and installs it in your system giving you the ability to uninstall it with your distribution's standard package management utilities.
Wow. Thank you! I will install Checkinstall, in a few minutes. We have fresh Colombian coffee in the kitchen. Colombian Beer is also very good. We are *big* fans of the Space Shuttle program. Lanny
-
Filipe Brandenburger -
Joseph L. Casale -
Lanny Marcus -
nate -
Phil Schaffner -
Phil Schaffner -
William L. Maltby