Summary: | sys-power/apcupsd-3.10.18-r1: /usr/sbin/apcupsd missing (after emerge) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel <deepee> |
Component: | New packages | Assignee: | Michael Imhof (RETIRED) <tantive> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | critical | CC: | bugs.gentoo, david.gardner, hellabri, henkjans_bagger, lebedev.ri, lema, me |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel
2007-04-28 11:12:14 UTC
After keywording apcupsd using ~x86, the problem is half-solved... ;-) These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-power/apcupsd-3.12.4 USE="ncurses nls snmp threads usb vhosts -cgi -doc" 0 kB Init-script still does not find the daemon-binary: hostname # /etc/init.d/apcupsd start * Caching service dependencies ... [ok] * Starting APC UPS daemon ... /sbin/start-stop-daemon: stat /usr/sbin/apcupsd: No such file or directory (No such file or directory) [!!] But now the daemon "apcupsd" is found under /sbin/apcupsd (see below) ?!?!?! hostname sbin # find / -type f -name apcupsd /var/lib/init.d/exitcodes/apcupsd /sbin/apcupsd /etc/init.d/apcupsd Just guessing: It seems to me the location of apcupsd has been changed to /sbin but the init-script has not been updated. /sbin/apcupsd makes sense to me, because apcupsd perhabs is needed there in case of system-shutdown when all other filesystems have been unmounted before, to finally shutdown the UPS-Hardware itself. ups! In addition to my second message: Keywording completely solved my problem: Shame on my, I've just forgotten to "etc-update" - sorry for that false-positive! ;-) Nevertheless: the Problem described in msg 1 still exists. (In reply to comment #1) > After keywording apcupsd using ~x86, the problem is half-solved... ;-) > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild R ] sys-power/apcupsd-3.12.4 USE="ncurses nls snmp threads usb > vhosts -cgi -doc" 0 kB > > Init-script still does not find the daemon-binary: > > hostname # /etc/init.d/apcupsd start > * Caching service dependencies ... > > [ok] > * Starting APC UPS daemon ... > /sbin/start-stop-daemon: stat /usr/sbin/apcupsd: No such file or directory (No > such file or directory) [!!] > > But now the daemon "apcupsd" is found under /sbin/apcupsd (see below) ?!?!?! > > hostname sbin # find / -type f -name apcupsd > /var/lib/init.d/exitcodes/apcupsd > /sbin/apcupsd > /etc/init.d/apcupsd > > Just guessing: > It seems to me the location of apcupsd has been changed to /sbin but the > init-script has not been updated. /sbin/apcupsd makes sense to me, because > apcupsd perhabs is needed there in case of system-shutdown when all other > filesystems have been unmounted before, to finally shutdown the UPS-Hardware > itself. > does 3.14.0 work ? i see olso some problems with the older versions here, installed 3.14.0 works here now Hy, This seems to be USE related. I solved te problem for me by adding the following line to /etc/portage/package.use : sys-power/apcupsd -apache2 -snmp -threads -doc nls I've got two different servers to be run with apcupsd. One just installed fine, the other didn't. They have different USE enabled. So I just tuned the USE for the one with the binaries missing to match the good one. I decided to have a look here, if other have related troubles. Et voila: I posted this. I do not know what USE flag(s) exactly are the solution. I got no time for that... Good Luck (In reply to comment #4) > Hy, > This seems to be USE related. > I solved te problem for me by adding the following line to > /etc/portage/package.use : > sys-power/apcupsd -apache2 -snmp -threads -doc nls > > I've got two different servers to be run with apcupsd. One just installed fine, > the other didn't. They have different USE enabled. So I just tuned the USE for > the one with the binaries missing to match the good one. > I decided to have a look here, if other have related troubles. Et voila: I > posted this. > > I do not know what USE flag(s) exactly are the solution. I got no time for > that... > > Good Luck > hi! yes there seem to be USE flag depedencies. i recompiled it with this use flags: sys-power/apcupsd -apache2 -snmp -threads -doc nls usb cgi and now it runs again after having the same problem as described above... HTH snIP3r hit the same problem today, this reminded me of having hit that 2 or 3 times before ... USE=-snmp emerge apcupsd (in fact I edited package.use ...) solved it for me, compilation failed otherwise without throwing an explicit error at the end of emerge-output (had to scroll up to see the failing steps ...) I have found this too, and noticed that the emerge transcript shows a build error that does not get trapped. gmake[1]: Entering directory `/tmp/portage/portage/sys-power/apcupsd-3.10.17-r1/work/apcupsd-3.10.17/src' gcc -g -O apcupsd.o apcoptd.o apcnet.o apcreports.o apcaction.o apcnis.o apcdevice.o /tmp/portage/portage/sys-power/apcupsd-3.10.17-r1/work/apcupsd-3.10.17/src/drivers/libdrivers.a /tmp/portage/portage/sys-power/apcupsd-3.10.17-r1/work/apcupsd-3.10.17/src/lib/libapc.a -o apcupsd apcupsd.o: In function `main': apcupsd.c:(.text+0x3f6): undefined reference to `attach_driver' collect2: ld returned 1 exit status distcc[3811] ERROR: compile (null) on localhost failed gmake[1]: *** [apcupsd] Error 1 gmake[1]: Leaving directory `/tmp/portage/portage/sys-power/apcupsd-3.10.17-r1/work/apcupsd-3.10.17/src' *** Bug 189730 has been marked as a duplicate of this bug. *** I have the same problem. When I set USE="-snmp" then it works perfectly. I suppose there should be not stable version with this terrible error. There should be disabled "snmp" use flag! Seems to be related to the parallel build. For me, "MAKEOPTS= emerge -v apcupsd" always succeeds while e.g. "MAKEOPTS=-j4 emerge -v apcupsd" never does. I had same problem, after upgrading to testing 3.14.1 problem went away, newer version seems to work. The init script uses /sbin. Did you etc-update the init script as well as you config file? This error is indeed the result of a parallel build error as pointed out in comment #10. Also on my system (x86) using makeopts=-j3 does not generate the /usr/sbin/apcupsd file, while makeopts=-j1 does generate the file and the startup script works again. Please fix this soon as this one could catch people badly leading to corrupt filesystems (xfs!!) after power-outage. ps) On my system(x86) the init-script refers to /usr/sbin/apcupsd, I guess comment #11 is from testing?? I just committed the updated ebuilds. Can anyone confirm that -j1 solves the problem? If so we can close this bug. |