apcupsd 3.4.10 fails to install
Hello- I'm having troubling installing apcupsd 3.4.10 on a FreeBSD 9.0 machine. This is what I get: aries# pwd /usr/ports/sysutils/apcupsd aries# make install clean === Building for apcupsd-3.14.10 src src/lib src/drivers src/drivers/apcsmart src/drivers/dumb src/drivers/net src/drivers/pcnet src/drivers/usb src/drivers/usb/generic src/libusbhid LDsrc/apcupsd /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.o): In function `astring::assign(char const*, int)': astring.cpp:(.text+0xbb): undefined reference to `operator new[](unsigned int)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.o): In function `astring::realloc(unsigned int)': astring.cpp:(.text+0x23c): undefined reference to `operator new[](unsigned int)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.o): In function `astring::vformat(char const*, char*)': astring.cpp:(.text+0x4a5): undefined reference to `operator new[](unsigned int)' gmake[2]: *** [apcupsd] Error 1 gmake[1]: *** [all] Error 2 gmake: *** [src_DIR] Error 2 *** Error code 1 Stop in /usr/ports/sysutils/apcupsd. *** Error code 1 Stop in /usr/ports/sysutils/apcupsd. aries# This system was compiled from svn sources. The ARIES kernel conf is as follows: aries# less /usr/src/sys/i386/conf/ARIES # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # ..snip.. # # $FreeBSD: releng/9.0/sys/i386/conf/GENERIC 227305 2011-11-07 13:40:54Z marius $ include GENERIC nocpu I486_CPU nocpu I586_CPU ident ARIES options KVA_PAGES=512 # increase system memory usage from 1GB to 2GB for ZFS usage nodeviceeisa nodevicefdc Contents of make.conf: aries# less /etc/make.conf # added by DSS 2/23/09 #.if $(.CURDIR:M*/sysutils/bacula-client) || \ #$(.CURDIR:M*/sysutils/bacula-client) #CONFIGURE_ARGS+=--enable-static-fd #.endif WITHOUT_X11=yes # added by use.perl 2012-09-21 10:18:17 PERL_VERSION=5.14.2 ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: apcupsd 3.4.10 fails to install
I'm having troubling installing apcupsd 3.4.10 on a FreeBSD 9.0 machine. This is what I get: aries# pwd /usr/ports/sysutils/apcupsd aries# make install clean === Building for apcupsd-3.14.10 src src/lib src/drivers src/drivers/apcsmart src/drivers/dumb src/drivers/net src/drivers/pcnet src/drivers/usb src/drivers/usb/generic src/libusbhid LDsrc/apcupsd /usr/ports/sysutils/apcupsd/work/apcupsd- 3.14.10/src/lib/libapc.a(astring.o): In function `astring::assign(char const*, int)': astring.cpp:(.text+0xbb): undefined reference to `operator new[](unsigned int)' /usr/ports/sysutils/apcupsd/work/apcupsd- 3.14.10/src/lib/libapc.a(astring.o): In function `astring::realloc(unsigned int)': astring.cpp:(.text+0x23c): undefined reference to `operator new[](unsigned int)' /usr/ports/sysutils/apcupsd/work/apcupsd- 3.14.10/src/lib/libapc.a(astring.o): In function `astring::vformat(char const*, char*)': astring.cpp:(.text+0x4a5): undefined reference to `operator new[](unsigned int)' gmake[2]: *** [apcupsd] Error 1 gmake[1]: *** [all] Error 2 gmake: *** [src_DIR] Error 2 *** Error code 1 Stop in /usr/ports/sysutils/apcupsd. *** Error code 1 Stop in /usr/ports/sysutils/apcupsd. aries# This system was compiled from svn sources. The ARIES kernel conf is as follows: aries# less /usr/src/sys/i386/conf/ARIES # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # #http://www.FreeBSD.org/doc/en_US.ISO8859- 1/books/handbook/kernelconfig-config.html # ..snip.. # # $FreeBSD: releng/9.0/sys/i386/conf/GENERIC 227305 2011-11-07 13:40:54Z marius $ include GENERIC nocpu I486_CPU nocpu I586_CPU ident ARIES options KVA_PAGES=512 # increase system memory usage from 1GB to 2GB for ZFS usage nodeviceeisa nodevicefdc Contents of make.conf: aries# less /etc/make.conf # added by DSS 2/23/09 #.if $(.CURDIR:M*/sysutils/bacula-client) || \ #$(.CURDIR:M*/sysutils/bacula-client) #CONFIGURE_ARGS+=--enable-static-fd #.endif WITHOUT_X11=yes # added by use.perl 2012-09-21 10:18:17 PERL_VERSION=5.14.2 I played around with the selecting/deselecting config options and got apcupsd to install. Previously I had the following options selected: aries# make showconfig === The following configuration options are available for apcupsd-3.14.10: APCSMART_DRV=on: Compile APC SmartUPS serial driver APCDUMB_DRV=on: Compile dumb UPS driver CLIENT_ONLY=off: Only NIS client (no network server or drivers) CGI=off: Compile with CGI programms to show status PCNET_DRV=on: Compile PowerChute Network Shutdown driver USB=on: Compile with USB Support driver SNMP_DRV=on: Compile with SNMP driver SNMP_DRV_OLD=off: Compile with old SNMP driver TCP_WRAPPERS=on: Compile with TCP_WRAPPERS support TEST_DRV=off: Compile TEST driver GAPCMON=off: Build GTK GUI front-end === Use 'make config' to modify these settings aries# The install with the above options failed. Next I ran make with the following options: aries# make showconfig === The following configuration options are available for apcupsd-3.14.10: APCSMART_DRV=on: Compile APC SmartUPS serial driver APCDUMB_DRV=off: Compile dumb UPS driver CLIENT_ONLY=off: Only NIS client (no network server or drivers) CGI=off: Compile with CGI programms to show status PCNET_DRV=on: Compile PowerChute Network Shutdown driver USB=off: Compile with USB Support driver SNMP_DRV=off: Compile with SNMP driver SNMP_DRV_OLD=off: Compile with old SNMP driver TCP_WRAPPERS=on: Compile with TCP_WRAPPERS support TEST_DRV=off: Compile TEST driver GAPCMON=off: Build GTK GUI front-end === Use 'make config' to modify these settings aries# This time make succeeded and I was able to install. What appears to be missing from my kernel file? Since the UPS is a SmartUPS 450SC, I really do not need the USB option. Nor do I need the APCDUMB_DRV option. This leaves the SNMP_DRV as a potential culprit. Does the kernel need to be compiled with SNMP? I was able to install apcupsd on other FreeBSD machines. The only difference is that these other machines are running the RELEASE version kernel instead of a compiled kernel. ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Still 2 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE AMD64
The time of the first post of the original topic 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE was some 20 days ago, and there are still 2 problems remained. So I copy the unsolved problems here, plus the thing I did. Any help will be greatly appreciated. = OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE ((using DEVICE ugen0 yields the same problem)) - Other lines are default. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - I have applied Tetcu's suggestion, disabling all USB-related configurations in my kernel, and put the following 3 lines in /boot/loader.conf, but the problems still exist: usb_load=YES ugen_load=YES umass_load=YES Here is my /var/run/dmesg.boot: http://www.ivangelion.tw/~cfliao/dmesg.boot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE
On Mon, May 11, 2009 at 2:00 AM, Frank Shute fr...@shute.org.uk wrote: On Sun, May 10, 2009 at 05:08:03PM +0800, Chun-fan Ivan Liao wrote: OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE - Other lines are default. I've got an APC SmartUPS 750 (USB on 6.4-RELEASE). When I hacked my apcupsd.conf (sometime ago now), I put in: DEVICE ugen0 I don't know if that's your problem i.e: you haven't specified the DEVICE. The reason that I did not specify the DEVICE is because the instruction in apcupsd.conf said so. And specifying DEVICE ugen0 yielded the same result. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - 3. Contiuning 2, changing the port to plug the USB will do, and /var/log/messages reads: - May 10 16:41:07 aura-cosmetics root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub1 May 10 16:41:08 aura-cosmetics kernel: ugen0: American Power Conversion Back-UPS RS 1000 FW:7.g9a.D USB FW:g9a, class 0/0, rev 1.10/1.06, addr 2 on uhub1 - But when starting the apcupsd now using [apcupsd start], there is no freebsd startup succeeded message appearing in /var/log/messages. However using [ps ax| grep apcupsd], there is the following associated procedure in the standard output: - 1264 ?? Ss 0:00.01 apcupsd start - 4. The last problem continuing 3, if stopping the apcupsd now using [apcupsd stop], the following error messages occur in /var/log/messages: - May 10 16:48:11 aura-cosmetics apcupsd[1270]: Valid lock file for pid=1264, but not ours pid=1270 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:48:11 aura-cosmetics apcupsd[1271]: Valid lock file for pid=1264, but not ours pid=1271 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd error shutdown completed - Any help will be greatly appreciated. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE
On Sun, May 10, 2009 at 8:23 PM, Ion-Mihai Tetcu ite...@freebsd.org wrote: On Sun, 10 May 2009 17:08:03 +0800 Chun-fan Ivan Liao i...@ivangelion.tw wrote: OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE - Other lines are default. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - Please post your /var/run/dmesg.boot after a roobot. Please see http://www.ivangelion.tw/~cfliao/dmesg.boot. 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - I'd say we hava a problem here. I'd be curios to know if you see the same thing with a kernel w/o usb in it and the following klds loaded: usb.ko, ugen.ko, umass.ko The result is the same. I've commented all the usb devices in my kernel, and put the following 3 lines in /boot/loader.conf: usb_load=YES ugen_load=YES umass_load=YES -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE
OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE - Other lines are default. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - 3. Contiuning 2, changing the port to plug the USB will do, and /var/log/messages reads: - May 10 16:41:07 aura-cosmetics root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub1 May 10 16:41:08 aura-cosmetics kernel: ugen0: American Power Conversion Back-UPS RS 1000 FW:7.g9a.D USB FW:g9a, class 0/0, rev 1.10/1.06, addr 2 on uhub1 - But when starting the apcupsd now using [apcupsd start], there is no freebsd startup succeeded message appearing in /var/log/messages. However using [ps ax| grep apcupsd], there is the following associated procedure in the standard output: - 1264 ?? Ss 0:00.01 apcupsd start - 4. The last problem continuing 3, if stopping the apcupsd now using [apcupsd stop], the following error messages occur in /var/log/messages: - May 10 16:48:11 aura-cosmetics apcupsd[1270]: Valid lock file for pid=1264, but not ours pid=1270 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:48:11 aura-cosmetics apcupsd[1271]: Valid lock file for pid=1264, but not ours pid=1271 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd error shutdown completed - Any help will be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE
On Sun, 10 May 2009 17:08:03 +0800 Chun-fan Ivan Liao i...@ivangelion.tw wrote: OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE - Other lines are default. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - Please post your /var/run/dmesg.boot after a roobot. 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - I'd say we hava a problem here. I'd be curios to know if you see the same thing with a kernel w/o usb in it and the following klds loaded: usb.ko, ugen.ko, umass.ko -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE
On Sun, May 10, 2009 at 05:08:03PM +0800, Chun-fan Ivan Liao wrote: OS version: FreeBSD 7.2 RELEASE apcupsd version: 3.14.5 UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW) UPS cable type: usb 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf: - UPSCABLE usb UPSTYPE usb DEVICE - Other lines are default. I've got an APC SmartUPS 750 (USB on 6.4-RELEASE). When I hacked my apcupsd.conf (sometime ago now), I put in: DEVICE ugen0 I don't know if that's your problem i.e: you haven't specified the DEVICE. Problem Description: 1. The APC box cannot be detected when connected to the FreeBSD system on system boot. (apcupsd_enable=YES is set in /etc/rc.conf ) The associated messages in /var/log/messages: - May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed - 2. Continuing 1, if I unplug the connecting USB then re-plug it to the same port, the USB cannot be identified. The associated message in /var/log/messages: - May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem (TIMEOUT), disabling port 3 - 3. Contiuning 2, changing the port to plug the USB will do, and /var/log/messages reads: - May 10 16:41:07 aura-cosmetics root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub1 May 10 16:41:08 aura-cosmetics kernel: ugen0: American Power Conversion Back-UPS RS 1000 FW:7.g9a.D USB FW:g9a, class 0/0, rev 1.10/1.06, addr 2 on uhub1 - But when starting the apcupsd now using [apcupsd start], there is no freebsd startup succeeded message appearing in /var/log/messages. However using [ps ax| grep apcupsd], there is the following associated procedure in the standard output: - 1264 ?? Ss 0:00.01 apcupsd start - 4. The last problem continuing 3, if stopping the apcupsd now using [apcupsd stop], the following error messages occur in /var/log/messages: - May 10 16:48:11 aura-cosmetics apcupsd[1270]: Valid lock file for pid=1264, but not ours pid=1270 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd FATAL ERROR in bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. May 10 16:48:11 aura-cosmetics apcupsd[1271]: Valid lock file for pid=1264, but not ours pid=1271 May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd error shutdown completed - Any help will be greatly appreciated. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Issue with apcupsd and gd.h missing?
Eric Sheesley-2 wrote: When trying to do a portupgrade of apcupsd I received the following error: checking for gd2/gd.h... no configure: error: Found system GD library but no header file. Please find the file gd.h in your system include directories and report its location to apcupsd-users at lists.sourceforge.net The system is Freebsd 7.1. I checked and gd.h does exist so I'm a bit confused as to what is going on. The file is located in /usr/local/include, a path that it appears the port checks. Anyone else experiencing this? Any suggestions on how to fix it? gd is installed. [snip] Eric, I am seeing exactly the same thing, and I also have gd installed. As described in the error message, I sent the requested output to the maintainer, ite...@freebsd.org. Regards, Steve -- View this message in context: http://www.nabble.com/Issue-with-apcupsd-and-gd.h-missing--tp22523557p22539828.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Issue with apcupsd and gd.h missing?
When trying to do a portupgrade of apcupsd I received the following error: checking for gd2/gd.h... no configure: error: Found system GD library but no header file. Please find the file gd.h in your system include directories and report its location to apcupsd-users at lists.sourceforge.net The system is Freebsd 7.1. I checked and gd.h does exist so I'm a bit confused as to what is going on. The file is located in /usr/local/include, a path that it appears the port checks. Anyone else experiencing this? Any suggestions on how to fix it? gd is installed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Power off and network apcupsd
Hello, I would like to know if this is possible to keep the network during a shutdown as describe and explained below for a Linux system. How could we do that? This will be used in a procedure to shutdown the UPS and the system after a Power Failure has been detected. Any experience with that will be of high interest to me. --- You may need to take steps to ensure networking stays active during your OS’s shutdown sequence in order for the PCNET driver to power off the UPS (the so-called ”killpower” operation). On a Linux distro, you can use commands such as... chkconfig --level 0 network on chkconfig --level 0 iptables on ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ P Please consider your environmental responsibility before printing this e-mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Power off and network apcupsd
Hello, I would like to know if this is possible to keep the network during a shutdown as describe and explained below for a Linux system. How could we do that? This will be used in a procedure to shutdown the UPS and the system after a Power Failure has been detected. Any experience with that will be of high interest to me. --- You may need to take steps to ensure networking stays active during your OS’s shutdown sequence in order for the PCNET driver to power off the UPS (the so-called ”killpower” operation). On a Linux distro, you can use commands such as... chkconfig --level 0 network on chkconfig --level 0 iptables on «?»¥ «?»§ «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ Grégory Bernard 11, rue de la Tour Directeur 75116 Paris France www.ToDoo.biz tel : +(33) 1 40 26 43 14 «?»¥ «?»§ «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ ¯ PGP ID -- 0x1BA3C2FD P Please consider your environmental responsibility before printing this e-mail Ce message et les pièces qui y sont éventuellement jointes sont exclusivement transmis à l'intention des personnes physiques ou morales auxquelles ils sont destinés. Si vous avez reçu ce message par erreur, merci d'en avertir immédiatement la société ToDoo par téléphone ou par courrier électronique de retour à l'expéditeur et de supprimer toute copie de ce message. Par ailleurs, il vous est notifié que toute divulgation, reproduction, distribution ou utilisation quelconque de tout ou partie de ce message (y compris de ses éventuelles pièces jointes) et des informations qui y sont contenues est interdite. Internet ne permettant pas d'assurer l'intégrité de ce message, ToDoo et l'expéditeur déclinent toute responsabilité au cas où il aurait été intercepté ou modifié par quiconque. This message and any possible attachments are transmitted for the exclusive use of the intended recipient(s). Should you receive this message by mistake, please notify ToDoo or the sender at once by telephone or return e-mail and delete it from your system. Moreover, any form of reproduction dissemination, copying, disclosure, modification, distribution and/or use of this message - or part of its contents, as well as its possible attachments by any unauthorized person or legal entity, is strictly prohibited. The nature of the Internet means that the integrity of this message cannot be guaranteed. ToDoo and the sender therefore disclaim any liability whatsoever in the event of this message having been intercepted and/or altered. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Power off and network apcupsd
bsd b...@todoo.biz writes: I would like to know if this is possible to keep the network during a shutdown as describe and explained below for a Linux system. How could we do that? This will be used in a procedure to shutdown the UPS and the system after a Power Failure has been detected. Any experience with that will be of high interest to me. I use the apcupsd port on a couple of FreeBSD machines, with both powered by my APC UPS. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: APCUPSD with Belkin Model F6C900-UNV UPS on FreeBSD 6.2?
O/H L Goodwin έγραψε: I'm still looking for the right UPS for a server running FreeBSD 6.2. Staples has the Belkin Enterprise Series 900VA UPS (model F6C900-UNV) on sale for $89.99. Will apcupsd on FreeBSD 6.2 work with this unit??? Theoretically no (http://www.apcupsd.org/manual/Supported_UPSes_Cables.html) unless someone with hands-on experience on this unit can say otherwise. -- RTFM and STFW before anything bad happens _ Thanos Rizoulis Electronic Computing Systems Engineer Larissa, Greece FreeBSD/PCBSD user ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
APCUPSD with Belkin Model F6C900-UNV UPS on FreeBSD 6.2?
I'm still looking for the right UPS for a server running FreeBSD 6.2. Staples has the Belkin Enterprise Series 900VA UPS (model F6C900-UNV) on sale for $89.99. Will apcupsd on FreeBSD 6.2 work with this unit??? FYI, I'm posting to freebsd-questions because I've had zero replies to my posts about three different UPS brands/models to the apcupsd-user mailing list. Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
usb-serial and apcupsd
I have a usb-serial controller attached to my freebsd 5.4 box it is loaded as ucom0. I have connect the serial cable from the UPC to it. when it first starts I have no problems but after a while I get an error message saying that the serial connection to the UPS is lost. The message repeats about once every 30 sec or so. what could be causing this? TIA, Tomok Taniguchi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
Dan O'Connor wrote: My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Nope. Same thing. Well, first off, try setting UPSTYPE to apcsmart then just set UPSCABLE to smart... To the OP: Is it a BACKUPS __PRO__ 650 or just a BACKUPS 650? If it's the latter then the dumb UPSTYPE should be correct. I have two boxes running this model with apcupsd without issue. Incidentally, based on your original description it almost sounds like your battery is dead (or very low charge) which would explain why apcupsd wants to shutdown immediately. Try running the ups without load for a few hours to see. G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Nope. Same thing. Well, first off, try setting UPSTYPE to apcsmart then just set UPSCABLE to smart... ~Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
troubles with apcupsd (basic setup)
Hello. I have an APC BackUPS 650 and I want to have my FreeBSD 5.4 system shutdown on power failure. I received a cable with the unit but there are no identifying markings. When I run apcupsd it thinks there is a power failure and proceeds to shut me down. Can anyone help? My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
Peter wrote: Hello. I have an APC BackUPS 650 and I want to have my FreeBSD 5.4 system shutdown on power failure. I received a cable with the unit but there are no identifying markings. When I run apcupsd it thinks there is a power failure and proceeds to shut me down. Can anyone help? My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Try this cable: 940-0020C hope that helps you, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubles with apcupsd (basic setup)
--- Greg Maruszeczka [EMAIL PROTECTED] wrote: Peter wrote: Hello. I have an APC BackUPS 650 and I want to have my FreeBSD 5.4 system shutdown on power failure. I received a cable with the unit but there are no identifying markings. When I run apcupsd it thinks there is a power failure and proceeds to shut me down. Can anyone help? My config file: UPSNAME APC_BACKUPS_650 UPSCABLE 940-0020B UPSTYPE dumb DEVICE /dev/cuaa0 LOCKFILE /var/spool/lock ONBATTERYDELAY 10 BATTERYLEVEL 20 MINUTES 5 TIMEOUT 600 Try this cable: 940-0020C Nope. Same thing. Warning power loss detected. Power failure. Running on UPS batteries. __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
apcupsd with usb
Hi there, a few months back there was already a question in this list regarding usb support in apcupsd since afaik only usb with linux is still supported. But there was a beta version named apcupsd-3.10.16-test2 which delivered the functions I need. Sad but true the link was broken. Has anyone a working (beta) version of this freebsd-apcupsd with usb-support? When will be usb officialy supported? (And no, I can not workaround with serial, since the 1U-server doesn't have any) Thanks in advance Chris P.S.: Sorry for any inconveniences caused, if this is not the correct list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
apcupsd with usb
Ing. Christian Sudec writes: a few months back there was already a question in this list regarding usb support in apcupsd since afaik only usb with linux is still supported. But there was a beta version named apcupsd-3.10.16-test2 which delivered the functions I need. Sad but true the link was broken. Has anyone a working (beta) version of this freebsd-apcupsd with usb-support? When will be usb officialy supported? (And no, I can not workaround with serial, since the 1U-server doesn't have any) The folks at apcupsd are in the middle of rolling a new version - to be tagged either 3.10.17 or 3.11, I'm a little unclear - which will include the beta (I would call it gamma) FreeBSD USB code. The code is actually there, and can probably be had from their CVS; what's holding up the formal release (and therefore the port) is getting the documentation in sync. You may want to subscribe to the mailing list for more information. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd with usb
On Tue, 05 Apr 2005 11:27:55 +0200, in sentex.lists.freebsd.questions you wrote: Hi there, a few months back there was already a question in this list regarding usb support in apcupsd since afaik only usb with linux is still supported. But there was a beta version named apcupsd-3.10.16-test2 which delivered the functions I need. Sad but true the link was broken. Hi, the version I downloaded from sourceforge works great so far (apcupsd-3.10.17) I was just playing with it today actually. Couple of caveats-- make sure the device is assigned to ugen, not uhid. To compile, ./configure --prefix=/usr/local --sbindir=/usr/local/sbin --enable-usb --sysconfdir=/usr/local/etc [releng5-865]# usbdevs addr 1: UHCI root hub, Intel addr 2: Back-UPS ES 725 FW:802.n2.D USB FW:n2, APC addr 3: U.S. Robotics 56K Faxmodem USB, U.S. Robotics addr 1: UHCI root hub, Intel addr 2: USB FAST SERIAL ADAPTER, FTDI addr 3: USB Communicator, STMicroelectronics addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel [releng5-865]# Here is my minimal config [releng5-865]# grep -v ^# apcupsd.conf | strings UPSNAME usb-test UPSCABLE smart UPSTYPE usb DEVICE usb /dev/uhid0 LOCKFILE /var/spool/lock ONBATTERYDELAY 6 BATTERYLEVEL 5 MINUTES 3 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 0.0.0.0 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 0 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 [releng5-865]# [releng5-865]# apcaccess status APC : 001,033,0842 DATE : Tue Apr 05 22:32:02 EDT 2005 HOSTNAME : releng5-865.sentex.ca RELEASE : 3.10.17 VERSION : 3.10.17 (18 March 2005) freebsd UPSNAME : usb-test CABLE: Custom Cable Smart MODEL: Back-UPS ES 725 UPSMODE : Stand Alone STARTTIME: Tue Apr 05 17:40:20 EDT 2005 STATUS : ONLINE LINEV: 119.0 Volts LOADPCT : 12.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 42.5 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 138.0 Volts ALARMDEL : Always BATTV: 13.5 Volts NUMXFERS : 0 TONBATT : 0 seconds CUMONBATT: 0 seconds XOFFBATT : N/A STATFLAG : 0x0208 Status Flag MANDATE : 2002-10-23 SERIALNO : AB0243121472 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 02.n2.D USB FW:n2 APCMODEL : Back-UPS ES 725 END APC : Tue Apr 05 22:32:05 EDT 2005 [releng5-865]# If I kill the power Broadcast Message from [EMAIL PROTECTED] (no tty) at 22:32 EDT... Warning power loss detected. Broadcast Message from [EMAIL PROTECTED] (no tty) at 22:32 EDT... Power failure. Running on UPS batteries. [releng5-865]# apcaccess status APC : 001,034,0884 DATE : Tue Apr 05 22:32:55 EDT 2005 HOSTNAME : releng5-865.sentex.ca RELEASE : 3.10.17 VERSION : 3.10.17 (18 March 2005) freebsd UPSNAME : usb-test CABLE: Custom Cable Smart MODEL: Back-UPS ES 725 UPSMODE : Stand Alone STARTTIME: Tue Apr 05 17:40:20 EDT 2005 STATUS : ONBATT LINEV: 001.0 Volts LOADPCT : 10.0 Percent Load Capacity BCHARGE : 099.0 Percent TIMELEFT : 44.4 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 138.0 Volts ALARMDEL : Always BATTV: 12.6 Volts NUMXFERS : 1 XONBATT : Tue Apr 05 22:32:45 EDT 2005 TONBATT : 11 seconds CUMONBATT: 11 seconds XOFFBATT : N/A STATFLAG : 0x02068010 Status Flag MANDATE : 2002-10-23 SERIALNO : AB0243121472 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 02.n2.D USB FW:n2 APCMODEL : Back-UPS ES 725 END APC : Tue Apr 05 22:32:56 EDT 2005 Broadcast Message from [EMAIL PROTECTED] (no tty) at 22:33 EDT... Power has returned... [releng5-865]# [releng5-865]# apcaccess status APC : 001,034,0908 DATE : Tue Apr 05 22:33:15 EDT 2005 HOSTNAME : releng5-865.sentex.ca RELEASE : 3.10.17 VERSION : 3.10.17 (18 March 2005) freebsd UPSNAME : usb-test CABLE: Custom Cable Smart MODEL: Back-UPS ES 725 UPSMODE : Stand Alone STARTTIME: Tue Apr 05 17:40:20 EDT 2005 STATUS : ONLINE LINEV: 118.0 Volts LOADPCT : 10.0 Percent Load Capacity BCHARGE : 082.0 Percent TIMELEFT : 36.8 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 138.0 Volts ALARMDEL : Always BATTV: 12.6 Volts NUMXFERS : 1 XONBATT : Tue Apr 05 22:32:45 EDT 2005 TONBATT : 0 seconds CUMONBATT: 25 seconds XOFFBATT : Tue Apr 05 22:33:10 EDT 2005 STATFLAG : 0x0208 Status Flag MANDATE : 2002-10-23 SERIALNO : AB0243121472 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 02.n2.D USB FW:n2 APCMODEL : Back-UPS ES 725 END APC : Tue Apr 05 22:33:15 EDT 2005 [releng5-865]# ---Mike Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 [EMAIL PROTECTED], (http://www.tancsa.com) ___ freebsd-questions
apcupsd vs FreeBSD-5.2.x
Hello, I've installed apcupsd (latest in ports) on a FreeBSD-5.2.x server. The server has an APC BackUPS Pro 1000i ups system connected to it via the APC supplied 940-0020B serial signalling cable. After installing apcupsd, the message from pkg-message appears, instructing the following: ** NOTE IF you install a apcupsd server: Change to /dev and create a softlink to usv from the serial line the USV is connected to, e.g. cd /dev ln -s cuaa1 usv Read the MANUAL to do site specific configuration assigenments! Especially have a detailed look into the chapter describing the shutdown procedure. ** So this is what I did. Here's what I've then figured I need to do for my apcupsd.conf file: ## apcupsd.conf v1.1 ## # # for apcupsd release 3.10.13 (16 April 2004) - freebsd # # 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. UPSNAME apc # # UPSCABLE [ simple| smart | ether | usb | #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 ] # # defines the type of cable that you have. UPSCABLE 940-0020B # # Old types, still valid, are mapped to the new drivers # # keyword driver used # UPSTYPE [ backupsdumb # | sharebasic dumb # | netups dumb # | backupspro apcsmart # | smartvsups apcsmart # | newbackupspro apcsmart # | backupspropnp apcsmart # | smartups apcsmart # | matrixups apcsmart # | sharesmart apcsmart # # *** New driver names. They can be used directly # rather than using one of the above aliases. # # UPSTYPE [ dumb | apcsmart | net | usb | snmp | test] # # defines the type of UPS you have. UPSTYPE dumb # # #DEVICE string /dev/serial port # name of your UPS device # # Here a table of the possible devices related with the UPS drivers. # # NOTE!!! for USB devices, please use a form indicated below # including the [0-15] as written! # # Driver DeviceDescription # dumb /dev/tty**Serial character device # apcsmart /dev/tty**Serial character device # usb /dev/usb/hiddev[0-15] On most systems # net hostname:port Network link to a master apcupsd #through NIS # snmp hostname:port:vendor:community #SNMP Network link to an SNMP-enabled #UPS device. Vendor is the MIB used by #the UPS device: can be APC or RFC #where APC is the powernet MIB and RFC #is the IETF's rfc1628 UPS-MIB. #Port is usually 161. DEVICE /dev/usv # #LOCKFILE path to lockfile # path for serial port lock file LOCKFILE /var/spool/lock # Note in the above, that UPSTYPE is set to dumb, as with the type being set to backupspro (which is what I would have thought I should need), apcupsd complains that the wrong upstype has been configured, and that its decided to use backups instead. The DEVICE /dev/usv is also there by default, and I didn't change this, thinking that this is somehow related to the message in pkg-message. However, despite my being able to start apcupsd fromcmdline okay enough, on reboot, apcupsd does not start. I've (after backing up the original), copied the sample shell startup file to apcupsd.sh and checked that its executable: -r-xr-xr-x 1 root wheel 1486 Jul 25 14:10 /usr/local/etc/rc.d/apcupsd.sh* So, why is it not starting automatically on reboot? The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. Is there something that I've missed out somewhere that is causing apcupsd not to start automatically on reboot? Here is what I am able to see fromk apcaccess status: $ apcaccess status localhost:3551 APC : 001,019,0499 DATE : Mon Jul 26 20:50:45 BST 2004 HOSTNAME : thor.vickiandstacey.com RELEASE : 3.10.13 VERSION : 3.10.13 (16 April 2004) freebsd UPSNAME : apc CABLE: APC Cable 940-0020B MODEL: DUMB UPS Driver UPSMODE : Stand Alone STARTTIME: Mon Jul 26 20:45:10 BST 2004 STATUS : ONLINE MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds NUMXFERS : 0 TONBATT : 0 seconds CUMONBATT: 0 seconds XOFFBATT : N/A STATFLAG
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Is there something that I've missed out somewhere that is causing apcupsd not to start automatically on reboot? I imagine this is the same problem. Peter. If there is any more information I should post that would of use to anyone wanting to assist, please let me know. Thanks for the time. Regards, Stacey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd vs FreeBSD-5.2.x
Hi Peter, Thanks for the reply. - Original Message - From: Peter Risdon [EMAIL PROTECTED] To: To Stacey Roberts Date: Tue, 27 Jul, 2004 20:12 BST Subject: Re: apcupsd vs FreeBSD-5.2.x Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Ah.., yes.., Do you mind checking my syntax, please? According to your suggestion, I'd be adding: link /dev/cuaa1 /dev/usv to /etc/devfs.conf, and that should be it? Whislt I'm keen to try this out, could I then ask the obvious question, is there some reason why in apcupsd.conf I am not allowed to simply use /dev/cuaa1? Thanks again for taking the time. Regards, Stacey Is there something that I've missed out somewhere that is causing apcupsd not to start automatically on reboot? I imagine this is the same problem. Peter. If there is any more information I should post that would of use to anyone wanting to assist, please let me know. Thanks for the time. Regards, Stacey pgpRsr12podE2.pgp Description: PGP signature
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: Hi Peter, Thanks for the reply. Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Ah.., yes.., Do you mind checking my syntax, please? According to your suggestion, I'd be adding: link /dev/cuaa1 /dev/usv to /etc/devfs.conf, and that should be it? No - look at the file, there are sample entries there: # Commonly used by many ports linkacd0cdrom linkcuaa0 pilot So you'd want: link cuaa1 usv Whislt I'm keen to try this out, could I then ask the obvious question, is there some reason why in apcupsd.conf I am not allowed to simply use /dev/cuaa1? I'm afraid I'm not sufficiently familiar with this software to answer. But it would almost certainly be less problematic to stick with the suggested link. Thanks again for taking the time. My pleasure, hope it helps. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd vs FreeBSD-5.2.x
Hi Peter, - Original Message - From: Peter Risdon [EMAIL PROTECTED] To: To Stacey Roberts Date: Tue, 27 Jul, 2004 21:00 BST Subject: Re: apcupsd vs FreeBSD-5.2.x Stacey Roberts wrote: Hi Peter, Thanks for the reply. Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Ah.., yes.., Do you mind checking my syntax, please? According to your suggestion, I'd be adding: link /dev/cuaa1 /dev/usv to /etc/devfs.conf, and that should be it? No - look at the file, there are sample entries there: # Commonly used by many ports linkacd0cdrom linkcuaa0 pilot So you'd want: link cuaa1 usv Okay, I understand. And I take it that if the serial signalling cable is actually connected to (labeled) serial port 1, then the corresponding device tobe used here would be cuaa0? Whislt I'm keen to try this out, could I then ask the obvious question, is there some reason why in apcupsd.conf I am not allowed to simply use /dev/cuaa1? I'm afraid I'm not sufficiently familiar with this software to answer. But it would almost certainly be less problematic to stick with the suggested link. I understand., seems to be there for what I imagine to be for some good reason. This has been really helpful, Peter. Thanks again. Regards, Stacey Thanks again for taking the time. My pleasure, hope it helps. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgp6lXncUcKKK.pgp Description: PGP signature
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: Hi Peter, - Original Message - From: Peter Risdon [EMAIL PROTECTED] [snip] So you'd want: link cuaa1 usv Okay, I understand. And I take it that if the serial signalling cable is actually connected to (labeled) serial port 1, then the corresponding device tobe used here would be cuaa0? The numbering of serial ports in FreeBSD starts at 0, so what would be called com1 in DOS/Windows is cuaa0 in FreeBSD. If the numbering of the ports on your computer follows the same pattern, then serial port 1 would map to cuaa0. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd vs FreeBSD-5.2.x
Hi, - Original Message - From: Peter Risdon [EMAIL PROTECTED] To: To Stacey Roberts Date: Tue, 27 Jul, 2004 22:56 BST Subject: Re: apcupsd vs FreeBSD-5.2.x Stacey Roberts wrote: Hi Peter, - Original Message - From: Peter Risdon [EMAIL PROTECTED] [snip] So you'd want: link cuaa1 usv Okay, I understand. And I take it that if the serial signalling cable is actually connected to (labeled) serial port 1, then the corresponding device tobe used here would be cuaa0? The numbering of serial ports in FreeBSD starts at 0, so what would be called com1 in DOS/Windows is cuaa0 in FreeBSD. Yes, I knew this.., If the numbering of the ports on your computer follows the same pattern, then serial port 1 would map to cuaa0. Thanks for that clarification. I just thought that the pkg-message using cuaa1 was somewhat strange as this is in effect serial 2 and not the first serial interface. I would have thought that the example would have used the first (cuaa0) for the example by default. Cheers for this. Regards, Stacey Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpKywdmwa90E.pgp Description: PGP signature
APC Back-UPS Pro1000 vs apcupsd
Hello, Has anyone gotten an APC Back-UPS Pro1000 ups system working with FreeBSD (4.x / 5.x), using the supplied cable: 940-0020B? I've just attempted to install this on one of my systems, but can't seem to get this to do anything but (supposedly) start, with the corresonding message in /var/log/messages: apcupsd 3.10.13 (16 April 2004) freebsd startup succeeded. The test (from the online manual) that suggests that pulling the serial cable from the back of either the server or ups unit will cause a message to be written to messages after two seconds fails - well, nothing gets written to messages, actually, waited about 10 minutes and still nothing. What I'm really confused about is the fact that this ups is supposed to somewhat of the cleverer line, but given the serial cable's product code, apcupsd docs say that I'm not going to get much out of this unit. Using this same model under Solaris 9 and RH Linux / Fedora Core2 with the PowerChute software included, provides quite a lot of capability with this APC model, that I hoped would be available with apcupsd running under FreeBSD. Is there a FreeBSD-ish specific howto somewhere that I can check out to see if I'm barking up the wrong tree here to begin with? Any pointers to any information would be appreciated. Thanks for the time. Regards, Stacey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd port not starting
dave wrote: Hello, I've got the latest apcupsd port installed on my 5.2.1 machine. I've got an APC xs1500va UPS which is supported. I'm going by the apcupsd user's guide and have set both UPSTYPE and UPSCABLE to usb however when i start apcupsd i keep getting the message: apcupsd driver type usb not found and it suggests i rerun configure with the --enable-usb option. I check the port and one of the args passed to it's configure is --enable-usb. Any help appreciated. Thanks. Dave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Check the archives. I seem to recall others stating that support for usb UPS in FBSD is minimal at best. Try serial or perhaps a usb-9-pin converter (if such a thing exists (?)) EB ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd and 'shutdown -p'
Rishi Chopra wrote:
I'd like apcupsd to call 'shutdown -p' when halting the system.
Currently the daemon works OK but allows for a race condition (e.g.
battery is not dead but power is restored, leaving the system waiting
for a key to be pressed)...
Anyone have any ideas on how to accomplish this?
Problem has been solved. Command can be aliased through shell variable
manipulation -or- as Neil Darlow suggested on the apcupsd mailing list
([apcupsd-users] apcupsd and 'shutdown -p', 4/23/2004, 1:20AM):
Just change the shutdown command in the doshutdown case within
apccontrol to the following:
doshutdown)
echo UPS ${2} initiated Shutdown Sequence | wall
${SHUTDOWN} -p now apcupsd UPS ${2} initiated shutdown
;;
Note: this will require APM or ACPI to be enabled in your BIOS and system
configuration (i.e. run apmd at startup for APM or enable ACPI in your
kernel). ACPI is still experimental, your mileage may vary.
NOTE: files referenced located in /usr/local/etc/apcupsd
--
Rishi Chopra
http://www.ocf.berkeley.edu/~rchopra
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
apcupsd and 'shutdown -p'
I'd like apcupsd to call 'shutdown -p' when halting the system. Currently the daemon works OK but allows for a race condition (e.g. battery is not dead but power is restored, leaving the system waiting for a key to be pressed)... Anyone have any ideas on how to accomplish this? -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with ATEN UC232 apcupsd
Hey guys/gals, I realize this may not be a FreeBSD problem, but I thought I'd post it and see if anyone else has seen it. I want to connect an APC SmartUPS to a legacy-free FreeBSD system. I recently used another of these USB to serial converters with a home automation system, and it seems to work fairly well - but for some reason, the apcupsd software will not work with the converter. Here is the dmesg output for the device: uplcom1: ATEN International Serial adapter, rev 1.10/0.01, addr 3 I don't get any errors in the dmesg output, but the apcupsd daemon errors out saying it can't communicate with the UPS. I know the converter seems to work, as I can cat /dev/ucom1, and I get a stream of SM messages (from the UPS), and I can even log in interactively using tip (I have a management card in the UPS). Any ideas what's going on? Alternately, this UPS does have a USB port. Is there a way a to get FreeBSD to use it via that method? Thanks, Seth Henry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with ATEN UC232 apcupsd
Hey guys/gals, I forgot to include the versions! I'm using FreeBSD 4.8-REL, and apcupsd version 3.8.6 Sorry, and thanks again! Seth Henry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (UPDATE) apcupsd 3.10.8 master/slave setup(whoops 3.10.6)
For the record. The quick fix for Apcupsd 3.10.6 hangup problems was to delete the apcaccess status parts out of the scripts in /usr/local/etc/apcupsd/. (commok, onbattery, etc...). Event messages still get walled and mail still gets sent. Just non of the UPS status information in messages. The status info can still be gotten by doing a apcaccess status on the command line (which used to not work, either). What was happening was that when the power to the UPS was pulled...the master server's apcupsd got stuck in the script(or something associate with the status part of the script) which stalled apcupsd. No slaves could contact the master and, when power was restored, apcupsd wouldn't respond to the event. I believe this also happened when in standalone mode, come to think of it. Anyway, thanks to Lewis Watson in the apcupsd-user list. __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
apcupsd 3.10.8 master/slave setup
Anyone have a master/slave or an NIS setup working correctly that can share some insight? If power is pulled from UPS, the master sends the warning to its console but... -the slaves lose their connection to the master -an apcaccess status on the master after plug is pulled will hang. -when ups is plugged back in to power outlet there is no status change sent. - here is the apcupsd stuff from 'ps -aux' -- root 31938 0.0 0.3 3864 1536 ?? Is4:49PM 0:00.27 /usr/local/sbin/apcupsd --kill-on-powerfail root 32071 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/apccontrol onbattery RACK_UPS 1 0 root 32072 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32074 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32075 0.0 0.1 992 564 ?? I 5:03PM 0:00.01 /usr/bin/mail -s master.mydomain.net Power Failure !!! root root 32076 0.0 0.3 3312 1352 ?? I 5:03PM 0:00.01 /usr/local/sbin/apcaccess status -- master config is stock slave config is stock with below changed UPSCABLE ether UPSTYPE net DEVICE master.mydomain.net:3551 The above configs are recommended from http://www.apcupsd.com/3.10.x-manual/ch04s06.html __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd 3.10.8 master/slave setup
My bad Subject should be apcupsd 3.10.6 master/slave setup (from ports) --- Dave McCammon [EMAIL PROTECTED] wrote: Anyone have a master/slave or an NIS setup working correctly that can share some insight? If power is pulled from UPS, the master sends the warning to its console but... -the slaves lose their connection to the master -an apcaccess status on the master after plug is pulled will hang. -when ups is plugged back in to power outlet there is no status change sent. - here is the apcupsd stuff from 'ps -aux' -- root 31938 0.0 0.3 3864 1536 ?? Is4:49PM 0:00.27 /usr/local/sbin/apcupsd --kill-on-powerfail root 32071 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/apccontrol onbattery RACK_UPS 1 0 root 32072 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32074 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32075 0.0 0.1 992 564 ?? I 5:03PM 0:00.01 /usr/bin/mail -s master.mydomain.net Power Failure !!! root root 32076 0.0 0.3 3312 1352 ?? I 5:03PM 0:00.01 /usr/local/sbin/apcaccess status -- master config is stock slave config is stock with below changed UPSCABLE ether UPSTYPE net DEVICE master.mydomain.net:3551 The above configs are recommended from http://www.apcupsd.com/3.10.x-manual/ch04s06.html __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd 3.10.8 master/slave setup(whoops 3.10.6)
Did forget to mention that I made the port with --enable-net --- Dave McCammon [EMAIL PROTECTED] wrote: Anyone have a master/slave or an NIS setup working correctly that can share some insight? If power is pulled from UPS, the master sends the warning to its console but... -the slaves lose their connection to the master -an apcaccess status on the master after plug is pulled will hang. -when ups is plugged back in to power outlet there is no status change sent. - here is the apcupsd stuff from 'ps -aux' -- root 31938 0.0 0.3 3864 1536 ?? Is4:49PM 0:00.27 /usr/local/sbin/apcupsd --kill-on-powerfail root 32071 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/apccontrol onbattery RACK_UPS 1 0 root 32072 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32074 0.0 0.1 632 264 ?? I 5:03PM 0:00.00 /bin/sh /usr/local/etc/apcupsd/onbattery RACK_UPS 1 0 root 32075 0.0 0.1 992 564 ?? I 5:03PM 0:00.01 /usr/bin/mail -s master.mydomain.net Power Failure !!! root root 32076 0.0 0.3 3312 1352 ?? I 5:03PM 0:00.01 /usr/local/sbin/apcaccess status -- master config is stock slave config is stock with below changed UPSCABLE ether UPSTYPE net DEVICE master.mydomain.net:3551 The above configs are recommended from http://www.apcupsd.com/3.10.x-manual/ch04s06.html __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Serial Port /dev for apcupsd
I am purchasing a APC Smart-UPS 420VA (with serial interface) for use with apcupsd PORTVERSION=3.10.6 on a 5.1-RELEASE system, and have a question about the correct /dev to specify in apcupsd.conf. My machine has one, standard serial port. From the Handbook, there appear to be two options, both of which exist in /dev. From the Handbook: * Call-in ports are named /dev/ttydN where N is the port number, starting from zero. Generally, you use the call-in port for terminals. Call-in ports require that the serial line assert the data carrier detect (DCD) signal to work correctly. * Call-out ports are named /dev/cuaaN. You usually do not use the call-out port for terminals, just for modems. You may use the call-out port if the serial cable or the terminal does not support the carrier detect signal. Which is the correct /dev to use in apcupsd.conf? Thanks, Barry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd
Barry Skidmore writes: OS: 5.1-RELEASE FreeBSD 5.1-CURRENT #0: Tue Oct 21 23:17:38 EDT 2003 UPS: Back-UPS 650, serial interface Back-UPS Pro 650, serial interface Cable: 940-0020B 940-0095A With the above setup apcupsd detects a power failure, but not a return of power, and thus does not send a notification email. Mine (v 3.8.6) works fine, except for sometimes reporting Low Batt when it clearly isn't. Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd
--- HOLLOW, CHRISTOPHER [EMAIL PROTECTED] wrote: Hi... I have the same UPS and cable running with apcupsd on FreeBSD 4.8. I have nothing but good things to say about the UPS and apcupsd. Detects and reports power failures and power restores. Properly halts the system upon reaching remaining-charge-percentage or time-until-failure thresholds. I have messages logging to stdout and to apcupsd.log via syslog. apcupsd does not send out email notification (AFAIK) but I have swatch configured to email me any apcupsd syslog messages. I receive bi-weekly self-test messages. It has been working flawlessly for about 18 months. Chris Barry Skidmore wrote: OS: 5.1-RELEASE UPS: Back-UPS 650, serial interface Cable: 940-0020B With the above setup apcupsd detects a power failure, but not a return of power, and thus does not send a notification email. Also, apcupsd does not halt the system. I noticed in the docs that for this to work on FreeBSD you need a Smart UPS, and use the --kill-on-powerfail option at the command line. Since I do not have a Smart UPS, I have not tried this option. My question is what model number of APC UPS is working well for you with apcupsd 3.10.6 My current setup did work fine with Red Hat 9.0 and upcupsd 3.8.0, so I do not think this is an issue with the cable. Thanks, Barry On Mon, 2003-12-08 at 01:22, Robert Huff wrote: Hello: Are there any users of apcupsd on the list? If so, please respond to me privately. I have a question about recommended UPS's that work well with FreeBSD. There are. :-) QHat's the question? Robert Huff [snip] I've got 4 FBSD 4.9 servers, 1 Win2k server, 1 FBSD 5.1 server running on a apc Smart-UPS 1400XL w/extra battery(all rack mount) with APCUPSD 3.8.6. One of the FBSD 4.9 servers is the master. I've got two W2k servers running on a Smart-UPS 1000XL w/extra batter. Both running APCUPSD 3.8.6. One master, the other slave. And there is another FBSD 4.9 server running on a Smart-UPS 620 running APCUPSD 3.8.6 as a standalone. The FBSD master on 1400xl collects info from the standalone and W2K master for the web based network monitor. All host send email to root when there is an event(except tests). The mail is sent by the scripts(changeme, commfailure, commok, mainsback, and onbattery) called from apccontrol in the /usr/local/etc/apcupsd directory. 3.8.6 works like a charm, except for the zombie process that happens on the FBSD master and standalone which doesn't seemed to cause any problems. Dave __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd
Barry Skidmore wrote: Are there any users of apcupsd on the list? If so, please respond to me privately. I have a question about recommended UPS's that work well with FreeBSD. I have used apcupsd before. I have an ancient old APC Back-UPS Pro 420 with serial cable, and everything was working just dandy. Seems that almost any recent APC Back-UPS Pro or Smart-UPS is supposed to work with apcupsd. However, mine does not work with apcupsd anymore. I think this was my fault, as I tried to send data from my FreeBSD machine to the UPS, and later realised that my model does not allow this. So I think I may have fried the UPS data-line. Possibly it was something else, though, so let's hope some more intelligent UPS+FreeBSD users post to this thread. -- Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd
Hi... I have the same UPS and cable running with apcupsd on FreeBSD 4.8. I have nothing but good things to say about the UPS and apcupsd. Detects and reports power failures and power restores. Properly halts the system upon reaching remaining-charge-percentage or time-until-failure thresholds. I have messages logging to stdout and to apcupsd.log via syslog. apcupsd does not send out email notification (AFAIK) but I have swatch configured to email me any apcupsd syslog messages. I receive bi-weekly self-test messages. It has been working flawlessly for about 18 months. Chris Barry Skidmore wrote: OS: 5.1-RELEASE UPS: Back-UPS 650, serial interface Cable: 940-0020B With the above setup apcupsd detects a power failure, but not a return of power, and thus does not send a notification email. Also, apcupsd does not halt the system. I noticed in the docs that for this to work on FreeBSD you need a Smart UPS, and use the --kill-on-powerfail option at the command line. Since I do not have a Smart UPS, I have not tried this option. My question is what model number of APC UPS is working well for you with apcupsd 3.10.6 My current setup did work fine with Red Hat 9.0 and upcupsd 3.8.0, so I do not think this is an issue with the cable. Thanks, Barry On Mon, 2003-12-08 at 01:22, Robert Huff wrote: Hello: Are there any users of apcupsd on the list? If so, please respond to me privately. I have a question about recommended UPS's that work well with FreeBSD. There are. :-) QHat's the question? Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Christopher Hollow - Technical Consultant Infrastructure Technology Support Toronto, ON ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apcupsd
Chris, May I ask what version of apcupsd you are running? When I switched from linux to FreeBSD, I also upgraded apcupsd from 3.8.0 to 3.10.6 Also note that we are using different versions of FreeBSD (4.8 -vs- 5.1). Thanks, Barry On Mon, 2003-12-08 at 12:58, HOLLOW, CHRISTOPHER wrote: I have the same UPS and cable running with apcupsd on FreeBSD 4.8. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
apcupsd
Are there any users of apcupsd on the list? If so, please respond to me privately. I have a question about recommended UPS's that work well with FreeBSD. Thanks, Barry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Need help with apcupsd startup script
Hi all,
I am using apcupsd installed from ports with no mods.
apcupsd itself runs fine but the script /usr/local/etc/rc.d/apcupsd.sh
returns:
apcupsd.sh: Cannot determine the PREFIX
when I try it.
I assume there are some Linux specific paths in there?
First lines of the script goes:
if ! PREFIX=$(expr $0 : \(/.*\)/etc/rc\.d/$(basename $0)\$); then
echo $0: Cannot determine the PREFIX 2
exit 1
fi
# If there is a global system configuration file, suck it in.
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
source_rc_confs
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
apcupsd_enable=${apcupsd_enable:-YES}
apcupsd_program=${apcupsd_program:-${PREFIX}/sbin/apcupsd}
apcupsd_flags=${apcupsd_flags:---kill-on-powerfail}
apcupsd_pidfile=${apcupsd_pidfile:-/var/run/apcupsd.pid}
apcupsd_lockfile=${apcupsd_pidfile:-/var/spool/lock/apcupsd.lock}
thanks,
/per olof
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Need help with apcupsd startup script
On Fri, Jul 19, 2002 at 12:58:42PM +0200, Per olof Ljungmark wrote:
Hi all,
I am using apcupsd installed from ports with no mods.
apcupsd itself runs fine but the script /usr/local/etc/rc.d/apcupsd.sh
returns:
apcupsd.sh: Cannot determine the PREFIX
when I try it.
I assume there are some Linux specific paths in there?
How are you calling the script? You must give the absolute path on
the command line, or the first block (if ! ...) will make it bomb out
with the error message.
HTH
Dan
First lines of the script goes:
if ! PREFIX=$(expr $0 : \(/.*\)/etc/rc\.d/$(basename $0)\$); then
echo $0: Cannot determine the PREFIX 2
exit 1
fi
# If there is a global system configuration file, suck it in.
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
source_rc_confs
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
apcupsd_enable=${apcupsd_enable:-YES}
apcupsd_program=${apcupsd_program:-${PREFIX}/sbin/apcupsd}
apcupsd_flags=${apcupsd_flags:---kill-on-powerfail}
apcupsd_pidfile=${apcupsd_pidfile:-/var/run/apcupsd.pid}
apcupsd_lockfile=${apcupsd_pidfile:-/var/spool/lock/apcupsd.lock}
thanks,
/per olof
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
--
Daniel Bye
PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC
_
ASCII ribbon campaign ( )
- against HTML, vCards and X
- proprietary attachments in e-mail / \
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Need help with apcupsd startup script
At 12:10 7/19/2002 +0100, Daniel Bye wrote: On Fri, Jul 19, 2002 at 12:58:42PM +0200, Per olof Ljungmark wrote: Hi all, I am using apcupsd installed from ports with no mods. apcupsd itself runs fine but the script /usr/local/etc/rc.d/apcupsd.sh returns: apcupsd.sh: Cannot determine the PREFIX when I try it. I assume there are some Linux specific paths in there? How are you calling the script? You must give the absolute path on the command line, or the first block (if ! ...) will make it bomb out with the error message. HTH Dan You are correct. /usr/local/etc/rc.d/apcupsd.sh start|stop will work. Now, how would I modify the script to make sh apcupsd.sh start|stop executed from /usr/local/etc/rc.d/ work? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Need help with apcupsd startup script
On Fri, Jul 19, 2002 at 01:53:13PM +0200, Per olof Ljungmark wrote: At 12:10 7/19/2002 +0100, Daniel Bye wrote: On Fri, Jul 19, 2002 at 12:58:42PM +0200, Per olof Ljungmark wrote: Hi all, I am using apcupsd installed from ports with no mods. apcupsd itself runs fine but the script /usr/local/etc/rc.d/apcupsd.sh returns: apcupsd.sh: Cannot determine the PREFIX when I try it. I assume there are some Linux specific paths in there? How are you calling the script? You must give the absolute path on the command line, or the first block (if ! ...) will make it bomb out with the error message. HTH Dan You are correct. /usr/local/etc/rc.d/apcupsd.sh start|stop will work. Now, how would I modify the script to make sh apcupsd.sh start|stop executed from /usr/local/etc/rc.d/ work? You can remove the first if block, but I would recommend you leave it as is - all the scripts installed in /usr/local/etc/rc.d tend to run this check, so I guess for sanity's sake rc must make use of it to ensure it is running a valid script. If it really bugs you typing the full path, I guess you could try a shell alias? This will work, in sh or bash: # alias apcupsd=/usr/local/etc/rc.d/apcupsd.sh $@ Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Need help with apcupsd startup script
On Fri, Jul 19, 2002 at 01:53:13PM +0200, Per olof Ljungmark wrote:
At 12:10 7/19/2002 +0100, Daniel Bye wrote:
On Fri, Jul 19, 2002 at 12:58:42PM +0200, Per olof Ljungmark wrote:
Hi all,
I am using apcupsd installed from ports with no mods.
apcupsd itself runs fine but the script /usr/local/etc/rc.d/apcupsd.sh
returns:
apcupsd.sh: Cannot determine the PREFIX
when I try it.
I assume there are some Linux specific paths in there?
How are you calling the script? You must give the absolute path on
the command line, or the first block (if ! ...) will make it bomb out
with the error message.
You are correct.
/usr/local/etc/rc.d/apcupsd.sh start|stop
will work.
Now, how would I modify the script to make sh apcupsd.sh start|stop
executed from /usr/local/etc/rc.d/ work?
That's not needed, if the script is executable it will be started
at boot time.
Edwin
--
Edwin Groothuis |Personal website: http://www.MavEtJu.org
[EMAIL PROTECTED]|Weblog: http://www.mavetju.org/weblog/weblog.php
bash$ :(){ :|:};: | Interested in MUDs? http://www.FatalDimensions.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
