LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices



Reply
 
Search this Thread
Old 01-25-2011, 11:23 AM   #1
davide123
Member
 
Registered: Jan 2010
Location: tampa bay fl
Distribution: fedora redhat 9 10 11 12 13 &14 x86_64 & i686; Peppermint, MintOne; RHEL 4 5 6, Ubuntu, SliTaz etc,
Posts: 102

Rep: Reputation: 16
APCUPSD Problem, apcaccess status is blank


Does not show online or offline, apctest says apcupsd getline failed apparently the link is not up?
here is my conf file:
Code:
## apcupsd.conf v1.1 ##
# 
#  for apcupsd release 3.14.8 (16 January 2010) - redhat
#
# "apcupsd" POSIX config file

#
# ========= General configuration parameters ============
#

# UPSNAME xxx
#   Use this to give your UPS a name in log files and such. This
#   is particulary useful if you have multiple UPSes. This does not
#   set the EEPROM. It should be 8 characters or less.
UPSNAME Rack3

# UPSCABLE <cable>
#   Defines the type of cable connecting the UPS to your computer.
#
#   Possible generic choices for <cable> are:
#     simple, smart, ether, usb
#
#   Or a specific cable model number may be used:
#     940-0119A, 940-0127A, 940-0128A, 940-0020B,
#     940-0020C, 940-0023A, 940-0024B, 940-0024C,
#     940-1524C, 940-0024G, 940-0095A, 940-0095B,
#     940-0095C, M-04-02-2000
#
UPSCABLE 940-1524C

# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE   DEVICE           Description
# apcsmart  /dev/tty**       Newer serial character device, appropriate for 
#                            SmartUPS models using a serial cable (not USB).
#
# usb       <BLANK>          Most new UPSes are USB. A blank DEVICE
#                            setting enables autodetection, which is
#                            the best choice for most installations.
#
# net       hostname:port    Network link to a master apcupsd through apcupsd's 
#                            Network Information Server. This is used if the
#                            UPS powering your computer is connected to a 
#                            different computer for monitoring.
#
# snmp      hostname:port:vendor:community
#                            SNMP network link to an SNMP-enabled UPS device.
#                            Hostname is the ip address or hostname of the UPS 
#                            on the network. Vendor can be can be "APC" or 
#                            "APC_NOTRAP". "APC_NOTRAP" will disable SNMP trap 
#                            catching; you usually want "APC". Port is usually 
#                            161. Community is usually "private".
#
# netsnmp   hostname:port:vendor:community
#                            OBSOLETE
#                            Same as SNMP above but requires use of the 
#                            net-snmp library. Unless you have a specific need
#                            for this old driver, you should use 'snmp' instead.
#
# dumb      /dev/tty**       Old serial character device for use with 
#                            simple-signaling UPSes.
#
# pcnet     ipaddr:username:passphrase
#                            PowerChute Network Shutdown protocol which can be 
#                            used as an alternative to SNMP with the AP9617 
#                            family of smart slot cards.ipaddr is the IP 
#                            address of the UPS mgmtcard. username and 
#                            passphrase are the credentials for which the card 
#                            has been configured.
#
UPSTYPE dumb
DEVICE /dev/ttyS0 

# POLLTIME <int>
#   Interval (in seconds) at which apcupsd polls the UPS for status. This
#   setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb, 
#   dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting
#   will improve apcupsd's responsiveness to certain events at the cost of
#   higher CPU utilization. The default of 60 is appropriate for most
#   situations.
POLLTIME 60

# LOCKFILE <path to lockfile>
#   Path for device lock file. Not used on Win32.
LOCKFILE /var/lock

# SCRIPTDIR <path to script directory>
#   Directory in which apccontrol and event scripts are located.
SCRIPTDIR /etc/apcupsd

# PWRFAILDIR <path to powerfail directory>
#   Directory in which to write the powerfail flag file. This file
#   is created when apcupsd initiates a system shutdown and is
#   checked in the OS halt scripts to determine if a killpower
#   (turning off UPS output power) is required.
PWRFAILDIR /etc/apcupsd

# NOLOGINDIR <path to nologin directory>
#   Directory in which to write the nologin file. The existence
#   of this flag file tells the OS to disallow new logins.
NOLOGINDIR /etc


#
# ======== Configuration parameters used during power failures ==========
#

# The ONBATTERYDELAY is the time in seconds from when a power failure
#   is detected until we react to it with an onbattery event.
#
#   This means that, apccontrol will be called with the powerout argument
#   immediately when a power failure is detected.  However, the
#   onbattery argument is passed to apccontrol only after the 
#   ONBATTERYDELAY time.  If you don't want to be annoyed by short
#   powerfailures, make sure that apccontrol powerout does nothing
#   i.e. comment out the wall.
ONBATTERYDELAY 6

# 
# Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so
# the first that occurs will cause the initation of a shutdown.
#

# If during a power failure, the remaining battery percentage
# (as reported by the UPS) is below or equal to BATTERYLEVEL, 
# apcupsd will initiate a system shutdown.
BATTERYLEVEL 5

# If during a power failure, the remaining runtime in minutes 
# (as calculated internally by the UPS) is below or equal to MINUTES,
# apcupsd, will initiate a system shutdown.
MINUTES 3

# If during a power failure, the UPS has run on batteries for TIMEOUT
# many seconds or longer, apcupsd will initiate a system shutdown.
# A value of 0 disables this timer.
#
#  Note, if you have a Smart UPS, you will most likely want to disable
#    this timer by setting it to zero. That way, you UPS will continue
#    on batteries until either the % charge remaing drops to or below BATTERYLEVEL,
#    or the remaining battery runtime drops to or below MINUTES.  Of course,
#    if you are testing, setting this to 60 causes a quick system shutdown
#    if you pull the power plug.   
#  If you have an older dumb UPS, you will want to set this to less than
#    the time you know you can run on batteries.
TIMEOUT 0

#  Time in seconds between annoying users to signoff prior to
#  system shutdown. 0 disables.
ANNOY 120

# Initial delay after power failure before warning users to get
# off the system.
ANNOYDELAY 60

# The condition which determines when users are prevented from
# logging in during a power failure.
# NOLOGON <string> [ disable | timeout | percent | minutes | always ]
NOLOGON disable

# If KILLDELAY is non-zero, apcupsd will continue running after a
# shutdown has been requested, and after the specified time in
# seconds attempt to kill the power. This is for use on systems
# where apcupsd cannot regain control after a shutdown.
# KILLDELAY <seconds>  0 disables
KILLDELAY 0

#
# ==== Configuration statements for Network Information Server ====
#

# NETSERVER [ on | off ] on enables, off disables the network
#  information server. If netstatus is on, a network information
#  server process will be started for serving the STATUS and
#  EVENT data over the network (used by CGI programs).
NETSERVER on

# NISIP <dotted notation ip address>
#  IP address on which NIS server will listen for incoming connections.
#  This is useful if your server is multi-homed (has more than one
#  network interface and IP address). Default value is 0.0.0.0 which
#  means any incoming request will be serviced. Alternatively, you can
#  configure this setting to any specific IP address of your server and 
#  NIS will listen for connections only on that interface. Use the
#  loopback address (127.0.0.1) to accept connections only from the
#  local machine.
NISIP 127.0.0.1

# NISPORT <port> default is 3551 as registered with the IANA
#  port to use for sending STATUS and EVENTS data over the network.
#  It is not used unless NETSERVER is on. If you change this port,
#  you will need to change the corresponding value in the cgi directory
#  and rebuild the cgi programs.
NISPORT 3551

# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
EVENTSFILE /var/log/apcupsd.events

# EVENTSFILEMAX <kilobytes>
#  By default, the size of the EVENTSFILE will be not be allowed to exceed
#  10 kilobytes.  When the file grows beyond this limit, older EVENTS will
#  be removed from the beginning of the file (first in first out).  The
#  parameter EVENTSFILEMAX can be set to a different kilobyte value, or set
#  to zero to allow the EVENTSFILE to grow without limit.
EVENTSFILEMAX 10

#
# ========== Configuration statements used if sharing =============
#            a UPS with more than one machine

#
# Remaining items are for ShareUPS (APC expansion card) ONLY
#

# UPSCLASS [ standalone | shareslave | sharemaster ]
#   Normally standalone unless you share an UPS using an APC ShareUPS
#   card.
UPSCLASS standalone

# UPSMODE [ disable | share ]
#   Normally disable unless you share an UPS using an APC ShareUPS card.
UPSMODE disable

#
# ===== Configuration statements to control apcupsd system logging ========
#

# Time interval in seconds between writing the STATUS file; 0 disables
STATTIME 0

# Location of STATUS file (written to only if STATTIME is non-zero)
STATFILE /var/log/apcupsd.status

# LOGSTATS [ on | off ] on enables, off disables
# Note! This generates a lot of output, so if         
#       you turn this on, be sure that the
#       file defined in syslog.conf for LOG_NOTICE is a named pipe.
#  You probably do not want this on.
LOGSTATS off

# Time interval in seconds between writing the DATA records to
#   the log file. 0 disables.
DATATIME 0

# FACILITY defines the logging facility (class) for logging to syslog. 
#          If not specified, it defaults to "daemon". This is useful 
#          if you want to separate the data logged by apcupsd from other
#          programs.
FACILITY DAEMON

#
# ========== Configuration statements used in updating the UPS EPROM =========
#

#
# These statements are used only by apctest when choosing "Set EEPROM with conf
# file values" from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD.
#

# UPS name, max 8 characters 
#UPSNAME UPS_IDEN

# Battery date - 8 characters
#BATTDATE mm/dd/yy

# Sensitivity to line voltage quality (H cause faster transfer to batteries)  
# SENSITIVITY H M L        (default = H)
#SENSITIVITY H

# UPS delay after power return (seconds)
# WAKEUP 000 060 180 300   (default = 0)
#WAKEUP 60

# UPS Grace period after request to power off (seconds)
# SLEEP 020 180 300 600    (default = 20)
#SLEEP 180

# Low line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 106 103 100 097
#    M 177 172 168 182
#    A 092 090 088 086
#    I 208 204 200 196     (default = 0 => not valid)
#LOTRANSFER  208

# High line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 127 130 133 136
#    M 229 234 239 224
#    A 108 110 112 114
#    I 253 257 261 265     (default = 0 => not valid)
#HITRANSFER 253

# Battery charge needed to restore power
# RETURNCHARGE 00 15 50 90 (default = 15)
#RETURNCHARGE 15

# Alarm delay 
# 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never
# BEEPSTATE 0 T L N        (default = 0)
#BEEPSTATE T

# Low battery warning delay in minutes
# LOWBATT 02 05 07 10      (default = 02)
#LOWBATT 2

# UPS Output voltage when running on batteries
# The permitted values depend on your model as defined by last letter 
#  of FIRMWARE or APCMODEL. Some representative values are:
#    D 115
#    M 208
#    A 100
#    I 230 240 220 225     (default = 0 => not valid)
#OUTPUTVOLTS 230

# Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on
# SELFTEST 336 168 ON OFF  (default = 336)
#SELFTEST 336

Code:
# apcaccess 
APC      : 001,018,0474
DATE     : 2011-01-25 11:25:54 -0500  
HOSTNAME : stpfedoratest
VERSION  : 3.14.8 (16 January 2010) redhat
UPSNAME  : Rack3
CABLE    : APC Cable 940-1524C
MODEL    : DUMB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2011-01-25 11:25:52 -0500  
STATUS   : 
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
NUMXFERS : 0
TONBATT  : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
STATFLAG : 0x07000000 Status Flag
END APC  : 2011-01-25 11:25:54 -0500
Mod edit: Changed "Quote" blocks to "Code" blocks to reduce clutter.
--Rick aka archtoad6

Last edited by archtoad6; 01-31-2011 at 05:08 PM. Reason: change "Quote" blocks to "Code" blocks
 
Old 01-26-2011, 07:55 AM   #2
michaelk
Moderator
 
Registered: Aug 2002
Posts: 12,168

Rep: Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784
When running apctest make sure that apcupsd has been shut down.
When running apcaccess apcupsd should be running. Does it start successfully?
What is the model number of your UPS? Does it connect via USB or serial port?
 
Old 01-27-2011, 12:31 PM   #3
davide123
Member
 
Registered: Jan 2010
Location: tampa bay fl
Distribution: fedora redhat 9 10 11 12 13 &14 x86_64 & i686; Peppermint, MintOne; RHEL 4 5 6, Ubuntu, SliTaz etc,
Posts: 102

Original Poster
Rep: Reputation: 16
Connected via serial cable 940-0024C, APC = Smart UPS 2200 XL. apcupsd does start successfully, as per /var/log/messages. When running apctest; apcupsd is shutdown. I get the option screen (weird thing is that I could only get this by setting UPS type to "dumb"); but when I hit option 1 to get comm info from the UPS it says
Quote:
Getline failed. Apparently link is not up
I also get a communication error using Power Chute Biz Entp. software, and APC tech support was telling me to "brain dead" the UPS, but unfortunately that is not possible at this time, as there are servers plugged in that cannot go down at the moment. I am trying to complete whatever troubleshooting I can while I wait for a good time to shut down everything...

Last edited by davide123; 01-27-2011 at 12:39 PM.
 
Old 01-27-2011, 01:33 PM   #4
michaelk
Moderator
 
Registered: Aug 2002
Posts: 12,168

Rep: Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784
Have you tried using the correct cable type and the apcsmart device settings?
 
Old 01-27-2011, 04:06 PM   #5
davide123
Member
 
Registered: Jan 2010
Location: tampa bay fl
Distribution: fedora redhat 9 10 11 12 13 &14 x86_64 & i686; Peppermint, MintOne; RHEL 4 5 6, Ubuntu, SliTaz etc,
Posts: 102

Original Poster
Rep: Reputation: 16
Umm....
I was under the impression 940-0024C is the correct cable type to use? It is an option in the apcupsd.conf file.
I have tried using apcsmart, instead of dumb, but then when i do apctest, it fails to connect and will not even pull up the first option screen with the 6 choces you can make (apctest)
 
Old 01-28-2011, 10:19 AM   #6
michaelk
Moderator
 
Registered: Aug 2002
Posts: 12,168

Rep: Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784
http://www.apcupsd.com/manual/manual...iguration-file. For smart UPSs might want to try this:
Quote:
UPSCABLE smart
UPSTYPE smartups
DEVICE /dev/ttyS0
LOCKFILE /var/lock
UPSCLASS standalone
UPSMODE disable
 
Old 02-04-2011, 09:45 AM   #7
davide123
Member
 
Registered: Jan 2010
Location: tampa bay fl
Distribution: fedora redhat 9 10 11 12 13 &14 x86_64 & i686; Peppermint, MintOne; RHEL 4 5 6, Ubuntu, SliTaz etc,
Posts: 102

Original Poster
Rep: Reputation: 16
@Michaelk.....exactly how I have it configured.... Its so weird. I have also tried APC Power Chute Business Enterprise edition on Fedora, Peppermint (Ubuntu), and XP SP3...I can connect to my UPS, and then it immediately shuts down the Virtual Machine...But not the server. PS-- the batteries are relatively new installed July '10 and the battery indicators on the front of the UPS say it has almost full power...either way I think everything would run even if a battery was not installed because it is hooked up to bldg power.....
Logs for Power Chute says :

Quote:
1/31/11 16:06:55 Shutdown process started
1/31/11 16:06:55 Low Battery
1/31/11 16:06:55 Power Failed
1/31/11 16:06:54 Communication Established
1/31/11 16:06:54 Monitoring Started
Everytime *UGH*

I thought it maybe an over voltage issue as per this post
Quote:
fs483 (TechnicalUser)
22 Jan 07 23:09
Ok, for the Over-voltage issue, is your UPS plugged into a dedicated circuit ? If this UPS shares an electrical outlet with some other power hungry device, then it WILL cause the over-voltage error. When a UPS runs on over-voltage for extended periods, the battery life and circuitry life is reduced. If I'm not mistaken, when a over-voltage is detected, the UPS's circuit disconnects the AC and runs on the battery until the over-voltage is back to normal. In doing so, you end up draining the battery EVEN though there's no power failure. I would have an electrician test the circuit to be sure everything is fine. I would also avoid plugging anything else into this outlet/circuit. I have a dozen of those 1500VA (running on 120V) on a dozen different circuits all fed from the electrical panel and I sometimes notice some of the UPSes kick into action more often than others. I'm leaving it as is because I will be remodeling my server room. http://www.tek-tips.com/viewthread.c...1321803&page=6
However I had our guys check the load on the circuit breaker... It's pulling less than a third of the MAX Current.

I don't know at this point I am so lost

Last edited by davide123; 02-04-2011 at 09:47 AM.
 
Old 02-04-2011, 10:24 AM   #8
michaelk
Moderator
 
Registered: Aug 2002
Posts: 12,168

Rep: Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784
Quote:
.I can connect to my UPS, and then it immediately shuts down the Virtual Machine...But not the server.
Please explain. Are you running apcupsd from a VM?
 
Old 02-04-2011, 02:51 PM   #9
davide123
Member
 
Registered: Jan 2010
Location: tampa bay fl
Distribution: fedora redhat 9 10 11 12 13 &14 x86_64 & i686; Peppermint, MintOne; RHEL 4 5 6, Ubuntu, SliTaz etc,
Posts: 102

Original Poster
Rep: Reputation: 16
I have VMWare Esxi 4.1 running on an IBM X3650 M2 server. I have run APCUPSD on both Fedora, and Peppermint ICE.

APCUPSD did not shut down my VM's.... If you read the beginning of my thread, I explained that I could only get my smart ups picked up by apcupsd if I set the .conf file to UPS Type = dumb and then when I run apctest, and I try option 1 to read serial data, I get cannot connect to UPS. It will not work at all (well cant even get a status) when I have UPS Type = Smart.


I have also tried Power Chute BE....
On Fedora, Peppermint, and XP
With this software it either says over-voltage or low battery and initiates the shutdown sequence...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
cman_tool status says member of cluster, yet nodes & votes = 0, and other blank value ineloquucius Linux - Server 0 01-26-2010 07:05 PM
Can halevt update status after a blank disc is written? nemesis9 Linux - Desktop 1 10-16-2009 09:25 AM
What's the Current Status of apcupsd, or Any Alternatives MQMan Linux - Software 1 01-03-2009 03:55 PM
Problem with apcupsd jnojr Linux - Software 0 12-21-2007 02:17 PM
APCUPSD - apcaccess problems. Riddick Linux - Software 1 01-05-2005 05:30 PM


All times are GMT -5. The time now is 11:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration