Bugzilla Bug 100614

When a powerfailure occurs, apcupsd issues the killpower command to the UPS.
But
it seems to do that in such a way that it won't support the feature
'Autorestart
of loads after UPS shutdown' on e.g. a Back-UPS RS (using USB cable). When the
power is restored, the UPS will not start up again. Leaving the server unaware
that it also can start up.


Reproducible: Always
Steps to Reproduce:
1. Install sys-power/apcupsd-3.0.15-r1
2. Startup apcupsd and remove power. Wait until PC and UPS has halted.
3. Restore power to the UPS.

Actual Results:  
The UPS is not powered up after power failure.

Expected Results:  
The UPS should power up after power failure.

I have tested the same thing with apcupsd-3.10.18 and it seems to power down
the
UPS is a way that it will restart after power failure.

emerge --info
Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.5-r0,
2.6.13-rc3 x86_64)
=================================================================
System uname: 2.6.13-rc3 x86_64 AMD Athlon(tm) 64 Processor 2800+
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://mirror.pudas.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://server1/gentoo-portage"
USE="amd64 X acpi alsa apache2 arts avi berkdb bitmap-fonts cdr crypt cups curl
dvd dvdr encode esd fam flac foomaticdb fortran gd gdbm gif gpm gtk gtk2
imagemagick imap imlib java jpeg junit kde libwww lzw lzw-tiff mad maildir
motif
mp3 mpeg mysql ncurses nls nptl nptlonly ogg oggvorbis opengl pam pdflib perl
png python qt quicktime readline samba sdl spell ssl tcltk tcpd tiff
truetype-fonts type1-fonts usb userlocales vorbis xml xml2 xmms xpm xv xvid
zlib
userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

The "switch power on for things connected to the ups when power returns" is set
up in the ups. On smart ups systems you can configure this feature over the
serial cable. I guess you can do this for the back ups rs as well over usb.
So i don't think this is not a software problem but an configuration problem as
the software is not running when the power comes back.

With the same configuration I get these messages while doing apcupsd
--killpower

3.10.15-r1:

apcupsd: linux-usb.c:1254 Kill power function CI_DelayBeforeShutdown ci=62
value=20 OK.
apcupsd: linux-usb.c:1281 Kill power function "CI_DelayBeforeShutdown" seems to
have worked. Continuing ...
apcupsd: linux-usb.c:1254 Kill power function CI_ShutdownRequested ci=42
value=1 OK.
apcupsd: linux-usb.c:1288 Kill power function "CI_ShutdownRequested" seems to
have worked. Continuing ...
apcupsd: linux-usb.c:1254 Kill power function CI_APCShutdownAfterDelay ci=18
value=30 OK.
apcupsd: linux-usb.c:1295 Kill power function "CI_APCShutdownAfterDelay" seems
to have worked. Continuing ...
apcupsd: linux-usb.c:1254 Kill power function CI_APCForceShutdown ci=61 value=1
OK.
apcupsd: linux-usb.c:1302 Kill power function "CI_APCForceShutdown" seems to
have worked. Done ...

3.10.18:

apcupsd: usb.c:682 UPS appears to support BackUPS style shutdown.

I don't know if it only a matter of different output format, but it for sure
shutdowns the UPS in different ways. The UPS won't turn on after the 3.10.15
shutdown but it will with 3.10.18.

I added apcupsd-3.10.18 to the tree.
Please test it and report back if your problem is fixed then.

Thanks, I will test it.

After installation of 3.10.18, I don't get the apache config file
/etc/apache2/conf/modules.d/60_apcupsd.conf installed. Here is probably the reason:

...
gmake[1]: Leaving directory
`/var/tmp/portage/apcupsd-3.10.18/work/apcupsd-3.10.18/autoconf'
cp: cannot stat `/3.10.18/apache.conf': No such file or directory
-------------------------------------------------------
You should not use ${D} with helpers.
  -->
-------------------------------------------------------
install: cannot stat `/var/tmp/portage/apcupsd-3.10.18/temp/60_apcupsd.conf': No
such file or directory
 * Applying smtp.patch ...                                                [ ok ]
...

I'm installing apcupsd with the following USE flags:

Calculating dependencies ...done!
[ebuild   R   ] sys-power/apcupsd-3.10.18  +apache2 +cgi -doc +ncurses +nls
-snmp -threads +usb 0 kB

Please sync again and try again. I fixed that bug for .18 some minutes after i
committed the .18 ebuild. Sorry ;)


gmake[1]: Entering directory
`/var/tmp/portage/apcupsd-3.10.18/work/apcupsd-3.10.18/autoconf'
gmake[1]: Nothing to be done for `install'.
gmake[1]: Leaving directory
`/var/tmp/portage/apcupsd-3.10.18/work/apcupsd-3.10.18/autoconf'
-------------------------------------------------------
You should not use ${D} with helpers.
  -->
-------------------------------------------------------
 * Applying smtp.patch ...                                                     
     [ ok ]
man:

But the file seems to be installed in the wrong place:

...
>>> /usr/sbin/smtp
>>> /usr/sbin/apcaccess
>>> /usr/sbin/powerflute
>>> /usr/sbin/apcnisd
>>> /usr/sbin/apctest
>>> /usr/sbin/apcupsd
>>> /60_apcupsd.conf
>>> Safely unmerging already-installed instance...
...

Please test again with -r1

Peter: Fixed or not?

Sorry for the delay, but it seems that my last message wasn't logged correctly
:-(

The 60_apcupsd.conf file is now installed as:

/etc/apache2/modules.d/60_apcupsd.conf

But, all the other packages (like webalizer, mod_php, apcupsd-3.10.15-r1)
install their files under:

/etc/apache2/conf/modules.d

Bump.

Could you please correct this last thing about where the 60_apcupsd.conf file is
placed during installation? Because it wont't work out-of-the box with
apache-2.0.54-r9.

You can close this one now when apache-2.0.54-r31 went stable.

Thanks for your help.