| « Prospect give out members details to an unknow person by email | HOWTO: setup a pxe server on Fedora with dnsmasq » |
HOWTO: Setup and install NUT to work with Fedora
20/07/11
06:23:00 pm, by richard 
, 672 words 
Categories: Fedora, Installing and Configuration, Network Management, Systems Administration
HOWTO: Setup and install NUT to work with Fedora
The only reason I'm using NUT rather than apcupsd is that my ReadyNas Duo will not talk to apcupsd. apcupsd is a lot simpler to setup and install without a lot of duplication of configuration values.
We need to edit a whole bunch of config files most are in /etc/ups. But first we will start with
SERVER=yes
Tell nut we will be a server over the network.The same message needs to also be in the nut.conf. You will see this type of annoying duplication of configuration a lot with nut ( think I already mentioned that though).
Setup which UPS's we are going to be monitoring from this machine, in our case its the one actually connected to this machine.
Tell Nut we will be a netserver again.
Create the setting for the UPS we will be monitoring, I'm using an APC Back-UPS BR 800 connected via its USB cable. If you want this to be able to talk to a ReadyNas you MUST call it [UPS]. (ReadyNas Duo another product I have and would not recommend. Among other things it is painfully slow even with the extra RAM module.)
driver = usbhid-ups
port = auto
desc = "UPS on Mailserver"
set the user that will be connecting in to get the status of the UPS. This one is local.
password = PASSWORD_HERE
upsmon master
sudo chkconfig ups on
sudo service ups restart
It is possible to check the drive is starting up cleanly, If it does not make sure you are using the correct driver for your hardware and that all the options are set correctly.
With my APC ups I see the following:
Network UPS Tools - Generic HID driver 0.35 (2.6.1)
USB communication driver 0.31
Using subdriver: APC HID 0.95
Check that data is being returned correctly and providing a good status.
- OL - on line power
- OB - on battery
- LB - low battery
To check that all is running look at the verbose output from this command, which is a list of all the settings for your ups.
Where ups is the [name] from ups.conf and appears to be case insensitive for this command.
I also had to hack 
/etc/init.d/halt to stop the system going down completely. This was necessary to allow the system to come back up automatically after the power is restored.
[ "$INIT_HALT" != "HALT" ] && HALTARGS="$HALTARGS -p"
sleep 120
exec $command $HALTARGS
Test the whole thing is working by removing the power core from the UPS wait fort he message to say the UPS is on battery power and then run this command
If all is well the system should close down to the system has halted output and stay powered up. The UPS will then cut power to the system. When you put the power cord back in the UPS it will pop and squeak a bit and the lights should flash. After a short delay evertything will power backup again.
Pages: 1· 2
No feedback yet
Comment feed for this post