Nice! Thank You Nick. I have installed the apcupsd now, looking good. Not testet though, but my experience with this from 5.x is very good. No nonsense, it just does the job.

Very good to get some "best practices" from other users, helps alot when your'e not dealing with linux/COS everyday

If I'm trying to find a package I generally do something like:

yum list apcupsd* --enablerepo=*

This will give me a clue if the package is available somewhere in the clearos repo's. I believe most packages in clearos-epel are OK to install but a few are not (things like amavis and openvpn). As soon as you install packages from clearos-epel you are making a relatively safe gamble but I'd try to avoid ever installing a clearos-epel package if it also exists in other clearos repos. I believe clearos-epel is not much more than a mirror of the main EPEL site for the v6 packages.

Easy to answer this one: Did'nt have a clue it existed B)

How do I find info about clearos-epel, how to install them, differences between community and pro reg. epel's...? Quite a unknown world for me.. :silly:

Now I used the command

yum --enablerepo=clearos-epel,clearos-core install apcupsd

, and it worked nice. I have used apcupsd on all my 5.x installs, so I know there is a few tricks to do in the apcupsd.conf-file (in /etc/apcupsd), like KILLDELAY (if you want it to stay awake after shutdown of server, useful if you have other equipment that need power as long as possible), identify the UPS by name (very useful when you have several of them in the rack), and more

Why not just install it directly from clearos-epel. From memory configuration is pretty much automatic for USB devices and documentation is here. I did not have to do anything in particular for the UPS to shut down the server last week when the mains tripped and the battery ran out.

Anyone got this install-how-to for 6.x? Cannot find this on the scary interweb :S

kfox wrote:

Here's the procedure for 6.3: http://foxpa.ws/2012/09/20/installing-apcupsd-on-clearos-6-3/

worked for me, thanks.

Here's the procedure for 6.3: http://foxpa.ws/2012/09/20/installing-apcupsd-on-clearos-6-3/

Can I suggest you try the apcupsd mailing list? Then if you get a solution or need any more information you post back here? I don't think I am able to help any more.

I have properly installed a different version and still the same.
this is my model Back-UPS BR 900GI
may not be suitable apcupsd аor this model.

If it helps, I am on apcupsd-3.14.10 which is the latest stable release.

my version apcupsd 3.14.8

maxwell wrote:

but when the program stops / var / run / apcupsd.pid the file disappears.

That is exactly as it is meant to:
Nick Howitt wrote:

When you start apcupsd it should create the file /var/run/apcupsd.pid, but it should also delete the file when it is stopped.

Not sure why you are getting the test did not complete message. You can google it but references point to a fix in about 2006. What version of apcupsd are you running?

and I do not pogyatno here is that the test number two, I always crash bug:

1) Test kill UPS power
2) Perform self-test
3) Read last self-test result
4) View/Change battery date
5) View manufacturing date
6) View/Change alarm behavior
7) View/Change sensitivity
8) View/Change low transfer voltage
9) View/Change high transfer voltage
10) Perform battery calibration
11) Test alarm
12) View/Change self-test interval
Q) Quit

Select function number: 2


This test instructs the UPS to perform a self-test
operation and reports the result when the test completes.

Clearing previous self test result...CLEARED
Initiating self test...INITIATED
Waiting for test to complete...TEST DID NOT COMPLETE

but when the program stops / var / run / apcupsd.pid the file disappears.

I'm not totally following this, but if "ps aux | grep apc" does not show your first line then apcupsd is not running. If the file /var/run/apcupsd.pid exists and apcupsd is not running, this will normally stop apcupsd from starting - it is normally a tool to stop you running a program more than once. When you start apcupsd it should create the file /var/run/apcupsd.pid, but it should also delete the file when it is stopped.

[root@server ~]# ps aux | grep apc
root 9445 0.0 0.0 22624 744 ? Ssl 22:09 0:00 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf
root 10044 0.0 0.0 4012 732 pts/0 S+ 22:21 0:00 grep apc

Yes, I found a file in / var / run / apcupsd.pid I deleted it. But when you start apcupsd file reappeared. It did "ps aux | grep apc" but did not change any.

Does the file /var/run/apcupsd.pid exist (it should not)? Or any file starting apc in /var/run?

Can you also do a "ps aux | grep apc" and post the output?

I use the root user

When you are running the test, are you running as the root user?

The massage writes constantly Valid lock file for pid =

I would not know where to start. Have you tried the apcupsd manual? There are also a mailing list which you could try out. Googling suggests there may be a timeout setting which governs this.

Configuration is identical to the one you sent. The server finds the model of APC. Where to find the reason I can not understand.

Hmm. If you are talking about apctest then option 2 for a self-test, then mine works. Attached is my apcupsd.conf (renamed to .txt so the forum allows me to attach it) [file name=apcupsd.txt size=12201]http://www.clearfoundation.com/media/kunena/attachments/legacy/files/apcupsd.txt[/file]

properly installed apcupsd-3.14.8-1.el5.i386.rpm. but when I spend Perform self-test is now throws this message:

Clearing previous self test result ... CLEARED
Initiating self test ... INITIATED
Waiting for test to complete ... TEST DID NOT COMPLETE


write to the configuration apcupsd.сonf. I want to see may be something in the configuration.

If it helps at all I use apcupsd-3.14.8-1.el5.i386.rpm. I just did an "rpm -ivh ..." and it worked out of the box. I see it is now available at 3.14.10 but I have not updated.

Please help with installing APCUPSD. Continuing bug apctest FATAL ERROR in device.c at line 71.
Unable to create UPS lock file. Unable to create UPS lock file. Do not know where to find the error has already broken her head. HELP! :dry:

Now Ive tried to setup the PowerChute. I say tried, because its not possible on my UPS. It does not support USB-connected devices, as most newer UPSs is.
Also APC hardly give any info on how to install/configure this, making it a quite hard time for me to install. The APCUPSD is far better documented, and for what I can see, does have excact the same functions as PowerChute. So for my case it is back in with APCUPSD :-)

Thanks Sigurd. Will try. Most "for fun", since I'm already happy with acupsd

Yes it is attached to a ClearOS 5.2 server.
As I wrote it is a rpm file, and easely innsalled with:

yum --localinstall --nogpgcheck name.rpm
(Not a thome so check the spelling he he)
or

rpm -ivh name.rpm

Good luch.

sigurdi

Do you use this on a COS-server? How was it to install/configure, easy?

This is a rather old post, but just had to answar.

If you have a APC ups why not use the APC software PowerChute Business Edition.

It have a linux rpm Agent with its own web interface, easy to manage and deteced my old smart UPS automaticly.

I had som problems with apcupsd that put my server in a reboot loop bacause of a faulty cable. :-)

They do not have server consolle so you need a windows computer, if you have more computers connected.
You can then install a client on alle other windows computers that you need smooth shutdown on. :-)

Realy nice web interface and gives alot of information, the server also have the posebility to shedule battery check, do runtime calibration, logs the power consuption and gives you a price estimate.....

Realy nice and free.

sigurdi

Just got a new APC UPS in the house, and I can confirm that this metod described here, does work nicely. First install the "yum install net-snmp", download and install the newest apcups package, i used the apcupsd-3.14.8-1.el5.i386.rpm. It is possible to adjust alot of settings in the /etc/apcupsd/apcupsd.conf but standard settings seems to do a OK job.
Well, all this is dependent you have a USB based UPS (and possibly it must be from APC?), and it is 1 PC connected to 1 UPS. As soon as you have several PCs and/or several UPS, the setup is a bit more work...
When I powered the UPS it instantly went into overcurrent protection mode. I thought it was something wrong, a setting I had forgot, but no. I have too high current into my house! 253V. No good. This makes sense I have had some trouble with some computers and other electronic stuff in our house. Guess I have to call the electric company on monday...

SO, is this what who is needed to get a USB-based APC UPS to work as supposed? Ive never tried installed a UPS on any Linux-based machines, so..

So to just wrap this up this is what is needed to install apcusd on ClearOS 5.1 enterprise:

yum install net-snmp

(this installs lm-sensors, and net-snmp)

rpm -ihv apcupsd-xxxxxxx.el5.i386.rpm

(obviously replace the apcupsd rpm with the correct filename)

I downloaded the latest version from apcupsd.org.

It said missing net-snmp.

So I went to net-snmp and got an RPM that when installed said it was missing tons. But I should have instead done a

yum install net-snmp

Will try when I get home.

I don't know why the ACPID is being suggested above--AFAIK that has nothing to do with this.

Am I wrong? I think that is for suspend/resume type stuff.

apcupsd and nut are for letting the ups tell the machine to shut down when the UPS is out of juice.

I like apcupsd because I have a large ups with several machines plugged into it. I can install apcupsd on all of them so that all machines can be shut down gracefully.

I just tried installing it on a a fresh ClearOS and it worked fine - only asked for lm_sensors and net-snmp.

The version I tried was just one I had laying around - apcupsd-3.14.6-1.el5.i386.rpm

I know that version also works perfectly with CC5.0

I'm sure there is a newer rpm available as well that should work fine.

Make sure your acpid package is installed and up to date:

yum install acpid

The APC power supply will need to call the ACPI stack. Sadly I don't have one of these but I have been able to get them running in the past.

Which dependencies did it say was missing?

You wouldn't happen to of taken note of which dependencies where missing by any chance

I am about to do the same thing