UPS help
From: ttjjekk119234 (ttjjekk119234_at_yahoo.com)
Date: 03/25/04
- Next message: Derrik Pates: "Re: can't mount USB pen drive"
- Previous message: james: "Re: No Framebuffer on Shuttle/GeForce4?"
- Next in thread: bmgz: "Re: UPS help"
- Reply: bmgz: "Re: UPS help"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 24 Mar 2004 20:46:29 -0500
I'm having problems with my UPS. It's an APC 725. When I pull the
plug on the UPS, it does not shutdown my box elegantly. I have
created a user 'upsmon'. My files are attached. I have upsmon, upsd
and hidups running. Is the fact that I'm running a USB cable causing
the problem?
I'm using NUT with hidups.
The setup is one linux server and one UPS. No other computers will be
protected by the UPS.
upsd.conf
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACCESS grant monitor localhost
ACCESS grant upsmon localhost thecorrectpassword
hosts.conf
MONITOR hidups@localhost "APC UPS"
ups.conf
[hidups]
driver = hidups
port = /dev/usb/hiddev0
upsmon.conf
#
--------------------------------------------------------------------------
# MINSUPPLIES <num>
#
# Give the number of power supplies that must be receiving power to
keep
# this system running. Most systems have one power supply, so you
would
# put "1" in this field.
#
# Large/expensive server type systems usually have more, and can run
with
# a few missing. The HP NetServer LH4 can run with 2 out of 4, for
example,
# so you'd set that to 2. The idea is to keep the box running as long
# as possible, right?
#
# Obviously you have to put the redundant supplies on different UPS
circuits
# for this to make sense! See big-servers.txt in the docs
subdirectory
# for more information and ideas on how to use this feature.
MINSUPPLIES 1
#
--------------------------------------------------------------------------
# SHUTDOWNCMD "<command>"
#
# upsmon runs this command when the system needs to be brought down.
#
# This should work just about everywhere ... if it doesn't, well,
change it.
SHUTDOWNCMD "/sbin/shutdown -h +0"
#
--------------------------------------------------------------------------
# NOTIFYCMD <command>
#
# upsmon calls this to send messages when things happen
#
# This command is called with the full text of the message as one
argument.
# The environment string NOTIFYTYPE will contain the type string of
# whatever caused this event to happen.
#
# Note that this is only called for NOTIFY events that have EXEC set
with
# NOTIFYFLAG. See NOTIFYFLAG below for more details.
#
# Making this some sort of shell script might not be a bad idea. For
more
# information and ideas, see pager.txt in the docs directory.
#
# Example:
# NOTIFYCMD /usr/local/ups/bin/notifyme
#
--------------------------------------------------------------------------
# POLLFREQ <n>
#
# Polling frequency for normal activities, measured in seconds.
#
# Adjust this to keep upsmon from flooding your network, but don't
make
# it too high or it may miss certain short-lived power events.
POLLFREQ 5
#
--------------------------------------------------------------------------
# POLLFREQALERT <n>
#
# Polling frequency in seconds while UPS on battery.
#
# You can make this number lower than POLLFREQ, which will make
updates
# faster when any UPS is running on battery. This is a good way to
tune
# network load if you have a lot of these things running.
#
# The default is 5 seconds for both this and POLLFREQ.
POLLFREQALERT 5
#
--------------------------------------------------------------------------
# HOSTSYNC - How long upsmon will wait before giving up on another
upsmon
#
# The master upsmon process uses this number when waiting for slaves
to
# disconnect once it has set the forced shutdown (FSD) flag. If they
# don't disconnect after this many seconds, it goes on without them.
#
# Similarly, upsmon slave processes wait up to this interval for the
# master upsmon to set FSD when a UPS they are monitoring goes
critical -
# that is, on battery and low battery. If the master doesn't do its
job,
# the slaves will shut down anyway to avoid damage to the file
systems.
#
# This "wait for FSD" is done to avoid races where the status changes
# to critical and back between polls by the master.
HOSTSYNC 15
#
--------------------------------------------------------------------------
# DEADTIME - Interval to wait before declaring a stale ups "dead"
#
# upsmon requires a UPS to provide status information every few
seconds
# (see POLLFREQ and POLLFREQALERT) to keep things updated. If the
status
# fetch fails, the UPS is marked stale. If it stays stale for more
than
# DEADTIME seconds, the UPS is marked dead.
#
# A dead UPS that was last known to be on battery is assumed to have
gone
# to a low battery condition. This may force a shutdown if it is
providing
# a critical amount of power to your system.
#
# Note: DEADTIME should be a multiple of POLLFREQ and POLLFREQALERT.
# Otherwise you'll have "dead" UPSes simply because upsmon isn't
polling
# them quickly enough. Rule of thumb: take the larger of the two
# POLLFREQ values, and multiply by 3.
DEADTIME 15
#
--------------------------------------------------------------------------
# POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master
system
#
# upsmon will create a file with this name in master mode when it's
time
# to shut down the load. You should check for this file's existence
in
# your shutdown scripts and run 'upsdrvctl shutdown' if it exists.
#
# See the shutdown.txt file in the docs subdirectory for more
information.
POWERDOWNFLAG /etc/killpower
#
--------------------------------------------------------------------------
# NOTIFYMSG - change messages sent by upsmon when certain events occur
#
# You can change the stock messages to something else if you like.
#
# NOTIFYMSG <notify type> "message"
#
# NOTIFYMSG ONLINE "UPS %s is getting line power"
# NOTIFYMSG ONBATT "Someone pulled the plug on %s"
#
# Note that %s is replaced with the identifier of the UPS in question.
#
# Possible values for <notify type>:
#
# ONLINE : UPS is back online
# ONBATT : UPS is on battery
# LOWBATT : UPS has a low battery (if also on battery, it's
"critical")
# FSD : UPS is being shutdown by the master (FSD = "Forced
Shutdown")
# COMMOK : Communications established with the UPS
# COMMBAD : Communications lost to the UPS
# SHUTDOWN : The system is being shutdown
# REPLBATT : The UPS battery is bad and needs to be replaced
# NOCOMM : A UPS is unavailable (can't be contacted for monitoring)
NOTIFYMSG ONBATT "Main Power has gone out. Network now on battery
back up. 20 minutes to shutdown"
NOTIFYMSG LOWBATT "Battery is nearly depleted. Save all data."
NOTIFYMSG SHUTDOWN "The server is now shutting down!"
#
--------------------------------------------------------------------------
# NOTIFYFLAG - change behavior of upsmon when NOTIFY events occur
#
# By default, upsmon sends walls (global messages to all logged in
users)
# and writes to the syslog when things happen. You can change this.
#
# NOTIFYFLAG <notify type> <flag>[+<flag>][+<flag>] ...
#
# NOTIFYFLAG ONLINE SYSLOG
# NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
#
# Possible values for the flags:
#
# SYSLOG - Write the message in the syslog
# WALL - Write the message to all users on the system
# EXEC - Execute NOTIFYCMD (see above) with the message
# Network UPS Tools: example upsmon configuration
#
# This file contains passwords, so keep it secure.
#
--------------------------------------------------------------------------
# RUN_AS_USER <userid>
#
# By default, upsmon splits into two processes. One stays as root and
# waits to run the SHUTDOWNCMD. The other one switches to another
userid
# and does everything else.
#
# The default nonprivileged user is set at compile-time with
# 'configure --with-user=...'.
#
# You can override it with '-u <user>' when starting upsmon, or just
# define it here for convenience.
#
# Note: if you plan to use the reload feature, this file (upsmon.conf)
# must be readable by this user! Since it contains passwords, DO NOT
# make it world-readable. Also, do not make it writable by the upsmon
# user, since it creates an opportunity for an attack by changing the
# SHUTDOWNCMD to something malicious.
#
# For best results, you should create a new normal user like "nutmon",
# then specify it here and make it the owner of your upsmon.conf, then
# set the mode on upsmon.conf to 0400.
#
RUN_AS_USER upsmon
#
--------------------------------------------------------------------------
# MONITOR <system> <powervalue> <username> <password>
("master"|"slave")
#
# List systems you want to monitor. Not all of these may supply power
# to the system running upsmon, but if you want to watch it, it has to
# be in this section.
#
# You must have at least one of these declared.
#
# <system> is a UPS identifier in the form
[<upsname>@]<hostname>[:<port>]
# like localhost, su700@mybox, etc.
#
# Simple entry:
#
# - "localhost" refers to the first UPS on the local system.
#
# Other possibilities:
#
# - "su700@mybox" means a UPS called "su700" on a system called
"mybox"
#
# - "elvis:1234" means the first UPS on a system called "elvis", port
1234.
#
# Finally, to use all of these options:
#
# - "fenton@bigbox:5678" is a UPS called "fenton" on a system called
# "bigbox" which runs upsd on port "5678". Phew!
#
# The UPS names like "su700" and "fenton" are set in your ups.conf
# in [brackets] which identify a section for a particular driver.
#
# If the ups.conf on host "doghouse" has a section called "snoopy",
the
# identifier for it would be "snoopy@doghouse".
#
# <powervalue> is an integer - the number of power supplies that this
UPS
# feeds on this system. Most computers only have one power supply, so
this
# is normally set to 1. You need a pretty big or special box to have
any
# other value here.
#
# You can also set this to 0 for a system that doesn't supply any
power,
# but you still want to monitor. Use this when you want to hear about
# changes for a given UPS without shutting down when it goes critical.
#
# <username> and <password> must match an entry in that system's
# upsd.users. If your username is "monmaster" and your password is
# "blah", the upsd.users would look like this:
#
# [monmaster]
# password = blah
# allowfrom = (whatever applies to this host)
# upsmon master (or slave)
#
# "master" means this system will shutdown last, allowing the slaves
# time to shutdown first.
#
# "slave" means this system shuts down immediately when power goes
critical.
#
# Examples:
#
# MONITOR myups@bigserver 1 monmaster blah master
# MONITOR su700@server.example.com 1 upsmon secretpass slave
MONITOR hidups@localhost 1 upsmon mycorrectpassword master
#
--------------------------------------------------------------------------
# MINSUPPLIES <num>
#
# Give the number of power supplies that must be receiving power to
keep
# this system running. Most systems have one power supply, so you
would
# put "1" in this field.
#
# Large/expensive server type systems usually have more, and can run
with
# a few missing. The HP NetServer LH4 can run with 2 out of 4, for
example,
# so you'd set that to 2. The idea is to keep the box running as long
# as possible, right?
#
# Obviously you have to put the redundant supplies on different UPS
circuits
# for this to make sense! See big-servers.txt in the docs
subdirectory
# for more information and ideas on how to use this feature.
MINSUPPLIES 1
#
--------------------------------------------------------------------------
# SHUTDOWNCMD "<command>"
#
# upsmon runs this command when the system needs to be brought down.
#
# This should work just about everywhere ... if it doesn't, well,
change it.
SHUTDOWNCMD "/sbin/shutdown -h +0"
#
--------------------------------------------------------------------------
# NOTIFYCMD <command>
#
# upsmon calls this to send messages when things happen
#
# This command is called with the full text of the message as one
argument.
# The environment string NOTIFYTYPE will contain the type string of
# whatever caused this event to happen.
#
# Note that this is only called for NOTIFY events that have EXEC set
with
# NOTIFYFLAG. See NOTIFYFLAG below for more details.
#
# Making this some sort of shell script might not be a bad idea. For
more
# information and ideas, see pager.txt in the docs directory.
#
# Example:
# NOTIFYCMD /usr/local/ups/bin/notifyme
#
--------------------------------------------------------------------------
# POLLFREQ <n>
#
# Polling frequency for normal activities, measured in seconds.
#
# Adjust this to keep upsmon from flooding your network, but don't
make
# it too high or it may miss certain short-lived power events.
POLLFREQ 5
#
--------------------------------------------------------------------------
# POLLFREQALERT <n>
#
# Polling frequency in seconds while UPS on battery.
#
# You can make this number lower than POLLFREQ, which will make
updates
# faster when any UPS is running on battery. This is a good way to
tune
# network load if you have a lot of these things running.
#
# The default is 5 seconds for both this and POLLFREQ.
POLLFREQALERT 5
#
--------------------------------------------------------------------------
# HOSTSYNC - How long upsmon will wait before giving up on another
upsmon
#
# The master upsmon process uses this number when waiting for slaves
to
# disconnect once it has set the forced shutdown (FSD) flag. If they
# don't disconnect after this many seconds, it goes on without them.
#
# Similarly, upsmon slave processes wait up to this interval for the
# master upsmon to set FSD when a UPS they are monitoring goes
critical -
# that is, on battery and low battery. If the master doesn't do its
job,
# the slaves will shut down anyway to avoid damage to the file
systems.
#
# This "wait for FSD" is done to avoid races where the status changes
# to critical and back between polls by the master.
HOSTSYNC 15
#
--------------------------------------------------------------------------
# DEADTIME - Interval to wait before declaring a stale ups "dead"
#
# upsmon requires a UPS to provide status information every few
seconds
# (see POLLFREQ and POLLFREQALERT) to keep things updated. If the
status
# fetch fails, the UPS is marked stale. If it stays stale for more
than
# DEADTIME seconds, the UPS is marked dead.
#
# A dead UPS that was last known to be on battery is assumed to have
gone
# to a low battery condition. This may force a shutdown if it is
providing
# a critical amount of power to your system.
#
# Note: DEADTIME should be a multiple of POLLFREQ and POLLFREQALERT.
# Otherwise you'll have "dead" UPSes simply because upsmon isn't
polling
# them quickly enough. Rule of thumb: take the larger of the two
# POLLFREQ values, and multiply by 3.
DEADTIME 15
#
--------------------------------------------------------------------------
# POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master
system
#
# upsmon will create a file with this name in master mode when it's
time
# to shut down the load. You should check for this file's existence
in
# your shutdown scripts and run 'upsdrvctl shutdown' if it exists.
#
# See the shutdown.txt file in the docs subdirectory for more
information.
POWERDOWNFLAG /etc/killpower
#
--------------------------------------------------------------------------
# NOTIFYMSG - change messages sent by upsmon when certain events occur
#
# You can change the stock messages to something else if you like.
#
# NOTIFYMSG <notify type> "message"
#
# NOTIFYMSG ONLINE "UPS %s is getting line power"
# NOTIFYMSG ONBATT "Someone pulled the plug on %s"
#
# Note that %s is replaced with the identifier of the UPS in question.
#
# Possible values for <notify type>:
#
# ONLINE : UPS is back online
# ONBATT : UPS is on battery
# LOWBATT : UPS has a low battery (if also on battery, it's
"critical")
# FSD : UPS is being shutdown by the master (FSD = "Forced
Shutdown")
# COMMOK : Communications established with the UPS
# COMMBAD : Communications lost to the UPS
# SHUTDOWN : The system is being shutdown
# REPLBATT : The UPS battery is bad and needs to be replaced
# NOCOMM : A UPS is unavailable (can't be contacted for monitoring)
NOTIFYMSG ONBATT "Main Power has gone out. Network now on battery
back up. 20 minutes to shutdown"
NOTIFYMSG LOWBATT "Battery is nearly depleted. Save all data."
NOTIFYMSG SHUTDOWN "The server is now shutting down!"
#
--------------------------------------------------------------------------
# NOTIFYFLAG - change behavior of upsmon when NOTIFY events occur
#
# By default, upsmon sends walls (global messages to all logged in
users)
# and writes to the syslog when things happen. You can change this.
#
# NOTIFYFLAG <notify type> <flag>[+<flag>][+<flag>] ...
#
# NOTIFYFLAG ONLINE SYSLOG
# NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
#
# Possible values for the flags:
#
# SYSLOG - Write the message in the syslog
# WALL - Write the message to all users on the system
# EXEC - Execute NOTIFYCMD (see above) with the message
# IGNORE - Don't do anything
#
# If you use IGNORE, don't use any other flags on the same line.
#
--------------------------------------------------------------------------
# RBWARNTIME - replace battery warning time in seconds
#
# upsmon will normally warn you about a battery that needs to be
replaced
# every 43200 seconds, which is 12 hours. It does this by triggering
a
# NOTIFY_REPLBATT which is then handled by the usual notify structure
# you've defined above.
#
# If this number is not to your liking, override it here.
RBWARNTIME 43200
#
--------------------------------------------------------------------------
# NOCOMMWARNTIME - no communications warning time in seconds
#
# upsmon will let you know through the usual notify system if it can't
# talk to any of the UPS entries that are defined in this file. It
will
# trigger a NOTIFY_NOCOMM by default every 300 seconds unless you
# change the interval with this directive.
NOCOMMWARNTIME 300
#
--------------------------------------------------------------------------
# FINALDELAY - last sleep interval before shutting down the system
#
# On a master, upsmon will wait this long after sending the
NOTIFY_SHUTDOWN
# before executing your SHUTDOWNCMD. If you need to do something in
between
# those events, increase this number. Remember, at this point your
UPS is
# almost depleted, so don't make this too high.
#
# Alternatively, you can set this very low so you don't wait around
when
# it's time to shut down. Some UPSes don't give much warning for low
# battery and will require a value of 0 here for a safe shutdown.
#
# Note: If FINALDELAY on the slave is greater than HOSTSYNC on the
master,
# the master will give up waiting for the slave to disconnect.
FINALDELAY 3
- Next message: Derrik Pates: "Re: can't mount USB pen drive"
- Previous message: james: "Re: No Framebuffer on Shuttle/GeForce4?"
- Next in thread: bmgz: "Re: UPS help"
- Reply: bmgz: "Re: UPS help"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
