Re: [CentOS] apcupsd-3.14.14
> -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R > Pierce > Sent: Saturday, December 24, 2016 8:13 PM > To: centos@centos.org > Subject: Re: [CentOS] apcupsd-3.14.14 > > On 12/24/2016 5:02 PM, TE Dukes wrote: > > I have an older Smart APC UPS. Replaced the batteries twice. It might > > be time to upgrade. This has been broken for a while but batteries are > > cheaper than replacing the whole unit. > > if it only has the non-serial port serial port control signalling, where CTS/RTS > etc are used to signal the UPS, and requires a very specific APC > "serial" cable, then I'd consider retiring it.I prefer my UPS's to > have ethernet based power management > Not using an APC cable, just USB. It doesn't have an Ethernet connection, just USB and a serial port. Its an APC Smart 750. Not looking for run time, but a safe shutdown. It may be worth upgrading. Checked Newegg the other day and they have come down in price big time. About time for another battery change anyway. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd-3.14.14
On 12/24/2016 5:02 PM, TE Dukes wrote: I have an older Smart APC UPS. Replaced the batteries twice. It might be time to upgrade. This has been broken for a while but batteries are cheaper than replacing the whole unit. if it only has the non-serial port serial port control signalling, where CTS/RTS etc are used to signal the UPS, and requires a very specific APC "serial" cable, then I'd consider retiring it.I prefer my UPS's to have ethernet based power management -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd-3.14.14
> -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R > Pierce > Sent: Saturday, December 24, 2016 7:44 PM > To: centos@centos.org > Subject: Re: [CentOS] apcupsd-3.14.14 > > On 12/24/2016 4:33 PM, TE Dukes wrote: > > Looking for a apcupsd 3.14.14 rpm. > > > > Been getting communication lost errors. I read there was a problem > > with the > > 3.14.12 version regarding a usb connection which I'm using, but has > > been corrected in 3.14.14. > > > > I found a Fedora 25 Rawhide src version, but the link must be bad. Was > > hoping I could rebuild it for Cento 6. > > > > Looks like apcupsd no longer producing the rpms. > > > > I could build one from the source but would prefer to use an rpm. > > look into NUT, the Network UPS Tools. much better way to manage UPS's, > either on a single system or network-wide. Thanks!! I have an older Smart APC UPS. Replaced the batteries twice. It might be time to upgrade. This has been broken for a while but batteries are cheaper than replacing the whole unit. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd-3.14.14
On 12/24/2016 4:33 PM, TE Dukes wrote: Looking for a apcupsd 3.14.14 rpm. Been getting communication lost errors. I read there was a problem with the 3.14.12 version regarding a usb connection which I'm using, but has been corrected in 3.14.14. I found a Fedora 25 Rawhide src version, but the link must be bad. Was hoping I could rebuild it for Cento 6. Looks like apcupsd no longer producing the rpms. I could build one from the source but would prefer to use an rpm. look into NUT, the Network UPS Tools. much better way to manage UPS's, either on a single system or network-wide. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd on c7 and logging
On 03/16/15 21:26, Joseph L. Casale wrote: Anyone else running the above and seeing logstats enabled even though the configuration has it off? All my hosts running apcupsd generate an enormous amount of useless logging... We're not, and we have over a dozen UPSes being monitored, each by a different server. You might see if there's a log level parm in /etc/apcupsd/apcupsd.conf. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Realizing that this thread is a bit old ... I've used apcupsd for years on a variety of enterprise- and consumer-class UPSes, on a variety of UNIXes. When I have seen a system that reports long battery lifetime in its stats but shuts down immediately, these are the likely culprits in order of likelihood: - one of the conf values was tuned down for initial testing and never turned up again. Another poster mentioned MINUTES but the one I usually use for testing and have forgotten to change is the TIMEOUT value; for testing I would often set it to 60 but in production it should (on my systems) be zero. There are a few other such parameters in the config file; review them all. - one or more batteries in your chain is EOL. Shut down apcupsd and initiate the battery test mode. Batteries will typically last not more than 5 years (yes, there is variation both ways) - your battery runtime is not calibrated and so the stats you're seeing are misleading. This can happen from not being calibrated to begin with, from not calibrating after replacing batteries, or having batteries deteriorate over time. See the apcupsd docs or mailing list for calibration details. Note that if your load is significantly less than your battery capacity (like 15% or similar), calibration will not in general work. - your UPS is EOL (fairly rare, but I occasionally retire a UPS because it no longer behaves in a predictable manner despite new batteries) If that doesn't solve it, I'd suggest taking it to the apcupsd mailing list. One thing that *is* more on-topic for CentOS and apcupsd, be aware that system updates don't clobber the patched /etc/rc.d/init.d/halt script needed for apcupsd to actually shut down your system. I have a cron job on such systems that looks for the string 'apcupsd' in that file; if it doesn't exist, an email alert goes out to me so that I know that I have to re-patch it. Devin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Am 16.02.2013 um 18:33 schrieb Devin Reade g...@gno.org: ... One thing that *is* more on-topic for CentOS and apcupsd, be aware that system updates don't clobber the patched /etc/rc.d/init.d/halt script needed for apcupsd to actually shut down your system. I have a cron job on such systems that looks for the string 'apcupsd' in that file; if it doesn't exist, an email alert goes out to me so that I know that I have to re-patch it. what about /sbin/halt.local this file could be used for such thing. (check /etc/rc.d/init.d/halt to see what ist done with /sbin/halt.local) -- LF ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
From: m.r...@5-cent.us m.r...@5-cent.us The entire contents of that incident. I see nothing in messages. 2013-02-07 17:38:19 -0500 Power failure. 2013-02-07 17:38:21 -0500 Battery power exhausted. 2013-02-07 17:38:21 -0500 Initiating system shutdown! 2013-02-07 17:38:21 -0500 User logins prohibited 2013-02-07 17:38:23 -0500 Power is back. UPS running on mains. 2013-02-07 17:38:23 -0500 Allowing logins I guess you already tried the UPS self test or the apctest utility...? Did you do a battery recalibration? When all else fails... power off/on! ^_^ JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
On Fri, Feb 8, 2013 at 8:23 AM, m.r...@5-cent.us wrote: As we have every day, we had a power blip overnight. one, at least, of the servers connected to a SmartUPS via cable, announced that power exhausted, initiating shutdown (which I've disabled). The thing is, I know the servers on that UPS draw a ridiculous amount of power, but I don't see that on the others... and this was three seconds, not minutes, after it announced there was a power outage. Has anyone else seen this behavior? You mean UPS's behaving badly? Yes, they break like everything else, especially the batteries. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Les Mikesell wrote: On Fri, Feb 8, 2013 at 8:23 AM, m.r...@5-cent.us wrote: As we have every day, we had a power blip overnight. one, at least, of the servers connected to a SmartUPS via cable, announced that power exhausted, initiating shutdown (which I've disabled). The thing is, I know the servers on that UPS draw a ridiculous amount of power, but I don't see that on the others... and this was three seconds, not minutes, after it announced there was a power outage. Has anyone else seen this behavior? You mean UPS's behaving badly? Yes, they break like everything else, especially the batteries. Nah, I think it's something with apcupsd. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
On Fri, Feb 8, 2013 at 9:54 AM, m.r...@5-cent.us wrote: As we have every day, we had a power blip overnight. one, at least, of the servers connected to a SmartUPS via cable, announced that power exhausted, initiating shutdown (which I've disabled). The thing is, I know the servers on that UPS draw a ridiculous amount of power, but I don't see that on the others... and this was three seconds, not minutes, after it announced there was a power outage. Has anyone else seen this behavior? You mean UPS's behaving badly? Yes, they break like everything else, especially the batteries. Nah, I think it's something with apcupsd. Doesn't it log the message as received from the UPS? It if has a network interface you should be get messages via syslog, email, snmp, etc., and there is probably a web interface with status showing expected battery capacity at the current load. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Les Mikesell wrote: On Fri, Feb 8, 2013 at 9:54 AM, m.r...@5-cent.us wrote: As we have every day, we had a power blip overnight. one, at least, of the servers connected to a SmartUPS via cable, announced that power exhausted, initiating shutdown (which I've disabled). The thing is, I know the servers on that UPS draw a ridiculous amount of power, but I don't see that on the others... and this was three seconds, not minutes, after it announced there was a power outage. Has anyone else seen this behavior? You mean UPS's behaving badly? Yes, they break like everything else, especially the batteries. Nah, I think it's something with apcupsd. Doesn't it log the message as received from the UPS? It if has a network interface you should be get messages via syslog, email, snmp, etc., and there is probably a web interface with status showing expected battery capacity at the current load. The entire contents of that incident. I see nothing in messages. 2013-02-07 17:38:19 -0500 Power failure. 2013-02-07 17:38:21 -0500 Battery power exhausted. 2013-02-07 17:38:21 -0500 Initiating system shutdown! 2013-02-07 17:38:21 -0500 User logins prohibited 2013-02-07 17:38:23 -0500 Power is back. UPS running on mains. 2013-02-07 17:38:23 -0500 Allowing logins Two seconds? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
service apcupsd status (or cat /var/log/apcupsd.events) Craig On Feb 8, 2013, at 9:54 AM, m.r...@5-cent.us wrote: Les Mikesell wrote: On Fri, Feb 8, 2013 at 9:54 AM, m.r...@5-cent.us wrote: As we have every day, we had a power blip overnight. one, at least, of the servers connected to a SmartUPS via cable, announced that power exhausted, initiating shutdown (which I've disabled). The thing is, I know the servers on that UPS draw a ridiculous amount of power, but I don't see that on the others... and this was three seconds, not minutes, after it announced there was a power outage. Has anyone else seen this behavior? You mean UPS's behaving badly? Yes, they break like everything else, especially the batteries. Nah, I think it's something with apcupsd. Doesn't it log the message as received from the UPS? It if has a network interface you should be get messages via syslog, email, snmp, etc., and there is probably a web interface with status showing expected battery capacity at the current load. The entire contents of that incident. I see nothing in messages. 2013-02-07 17:38:19 -0500 Power failure. 2013-02-07 17:38:21 -0500 Battery power exhausted. 2013-02-07 17:38:21 -0500 Initiating system shutdown! 2013-02-07 17:38:21 -0500 User logins prohibited 2013-02-07 17:38:23 -0500 Power is back. UPS running on mains. 2013-02-07 17:38:23 -0500 Allowing logins Two seconds? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Craig White ~ craig.wh...@ttiltd.com 1.800.869.6908 ~~ www.ttiassessments.com Improving Productivity and Communication in the Workplace Webinar https://www4.gotomeeting.com/register/353378831 February 21, 2013, 11am EST Enhanced productivity begins with effective communication -- providing clear information, communicating honestly, listening, asking questions, letting others talk, and bringing a positive approach when engaging in difficult conversations. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds Now, the shutting down annoys me, since it *appears* that by creating the script that it calls that returns, per the documentation, a -99, it sets a flag *somewhere*, that's never, ever changed. Just for grins, I restarted apcupsd, it's all fine, online, and the battery light is not telling me it needs to be changed, but it still reads SHUTTING DOWN. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds You can specify in the conf file that shutdown occurs when it hits X minutes of runtime left - MINUTES should be the parameter. You're at 10.0 minutes left if you have it set to something 10.0 or greater, it's probably gonna want to shutdown immediately at any AC power loss. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Toby Bluhm wrote: On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds You can specify in the conf file that shutdown occurs when it hits X minutes of runtime left - MINUTES should be the parameter. You're at 10.0 minutes left if you have it set to something 10.0 or greater, it's probably gonna want to shutdown immediately at any AC power loss. I'm afraid you've missed the whole beginning of this thread - I suggest you read it. I know what you were saying; it's the response of apcupsd to a power blip this morning that's the issue: as much as these servers draw, there's no way that the UPS is out of power in 3 seconds. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
On 2/8/2013 2:26 PM, m.r...@5-cent.us wrote: Toby Bluhm wrote: On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds You can specify in the conf file that shutdown occurs when it hits X minutes of runtime left - MINUTES should be the parameter. You're at 10.0 minutes left if you have it set to something 10.0 or greater, it's probably gonna want to shutdown immediately at any AC power loss. I'm afraid you've missed the whole beginning of this thread - I suggest you read it. I know what you were saying; it's the response of apcupsd to a power blip this morning that's the issue: as much as these servers draw, there's no way that the UPS is out of power in 3 seconds. I'm not saying it's out of battery power. I'm saying you may be telling it to shutdown when it has, by it's own calculations, 10 minutes of battery run time left. I believe the default is 3 or 5 in apcupsd.conf. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
On Feb 8, 2013, at 12:26 PM, m.r...@5-cent.us wrote: Toby Bluhm wrote: On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds You can specify in the conf file that shutdown occurs when it hits X minutes of runtime left - MINUTES should be the parameter. You're at 10.0 minutes left if you have it set to something 10.0 or greater, it's probably gonna want to shutdown immediately at any AC power loss. I'm afraid you've missed the whole beginning of this thread - I suggest you read it. I know what you were saying; it's the response of apcupsd to a power blip this morning that's the issue: as much as these servers draw, there's no way that the UPS is out of power in 3 seconds. You can configure the anticipation of how many minutes are necessary for powering down because it's definitely not instantaneous and in fact, powering down is likely to cause an increase of power consumption. That said, 55% load capacity is very high and obviously fits into the calculation that APCUPSD is making when it instructs connected server(s) to shut down. Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Toby Bluhm wrote: On 2/8/2013 2:26 PM, m.r...@5-cent.us wrote: Toby Bluhm wrote: On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds You can specify in the conf file that shutdown occurs when it hits X minutes of runtime left - MINUTES should be the parameter. You're at 10.0 minutes left if you have it set to something 10.0 or greater, it's probably gonna want to shutdown immediately at any AC power loss. I'm afraid you've missed the whole beginning of this thread - I suggest you read it. I know what you were saying; it's the response of apcupsd to a power blip this morning that's the issue: as much as these servers draw,there's no way that the UPS is out of power in 3 seconds. I'm not saying it's out of battery power. I'm saying you may be telling it to shutdown when it has, by it's own calculations, 10 minutes of battery run time left. I believe the default is 3 or 5 in apcupsd.conf. Oh, sorry, you weren't clear. Nope, apcupsd.conf is at its default of MINUTES 3. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, odd behavior
Craig White wrote: On Feb 8, 2013, at 12:26 PM, m.r...@5-cent.us wrote: Toby Bluhm wrote: On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote: Craig White wrote: service apcupsd status (or cat /var/log/apcupsd.events) Already posted the latter; the former, hey, neat results, excerpted here: MODEL: Smart-UPS 3000 RM STATUS : SHUTTING DOWN LINEV: 118.0 Volts LOADPCT : 55.9 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 10.0 Minutes ... TONBATT : 0 seconds CUMONBATT: 27 seconds snip That said, 55% load capacity is very high and obviously fits into the calculation that APCUPSD is making when it instructs connected server(s) to shut down. Heh. You think 55% is bad? with the 48 core servers, and esp. with the 64 core ones, when someone's running a job on the cluster, under no circumstances can I have more than three servers plugged into a 3000... and even then, I've seen it around 90%. I still don't believe that it would be run dry in 2-3 seconds. And I'm still perturbed about it still telling me it's shutting down. Haven't figured out how to tell that to stop. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
I wrote: Stephen Harris wrote: On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.r...@5-cent.us wrote: Anyone else around using apcupsd? I seem to be seeing a problem, and I'd snip apccontrol isn't flagged as a config file in the rpm snip The script says # WARNING: the apccontrol file will be overwritten every time you update your # apcupsd, doing `make install'. Your own customized scripts will _not_ be # overwritten. If you wish to make changes to this file (discouraged), you # should change apccontrol.sh.in and then rerun the configure process. If you can't change apcupsd.conf config to meet your needs then _don't_ change apccontrol; add a custom script that does an exit 99 to prevent the shutdown from running. It looks like you're right... EXCEPT that you missed the part about changing apccontrol.sh.in, which appears to me to be something you get if you build snipo Ok, finally had time to go back and read carefully. And then, with a little googling, saw someone else's reaction as the same as mine: apccontrol has a *lot* of options. Does this mean that I need to write a script names poweroff so that it doesn't shut down, *and* have symlinks to that from loadlimit, runlimit, doreboot, onbattery, failing, and timeout? If so, that's ugly mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
On 6 Nov 2012, at 21:56, m.r...@5-cent.us m.r...@5-cent.us wrote: Anyone else around using apcupsd? I seem to be seeing a problem, and I'd like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). Odd behaviour. I have it running on CentOS 5, OpenBSD and windows and none of these show this behaviour. I installed through yum. What settings do you have on the UPS itself? Are the servers attached to a control group with low priority? Mike ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.r...@5-cent.us wrote: Anyone else around using apcupsd? I seem to be seeing a problem, and I'd Yes like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). It wouldn't normally do that, until the battery is almost drained. Taken from apcupsd.conf: # 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 Basically, systems shouldn't shutdown with a '2 second blip' unless your battery is dead. it, I found that the config file was set to the original code... and I apccontrol isn't flagged as a config file in the rpm ./etc/apcupsd/apccontrol . c /etc/apcupsd/apcupsd.conf . c /etc/apcupsd/changeme . c /etc/apcupsd/commfailure . c /etc/apcupsd/commok . c /etc/apcupsd/offbattery . c /etc/apcupsd/onbattery . c /etc/logrotate.d/apcupsd Has anyone seen this behavior? The script says # WARNING: the apccontrol file will be overwritten every time you update your # apcupsd, doing `make install'. Your own customized scripts will _not_ be # overwritten. If you wish to make changes to this file (discouraged), you # should change apccontrol.sh.in and then rerun the configure process. If you can't change apcupsd.conf config to meet your needs then _don't_ change apccontrol; add a custom script that does an exit 99 to prevent the shutdown from running. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
Stephen Harris wrote: On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.r...@5-cent.us wrote: Anyone else around using apcupsd? I seem to be seeing a problem, and I'd Yes like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). It wouldn't normally do that, until the battery is almost drained. I dunno, but it appears to, sometimes. And we have such *wonderful* power in this building, there's at least one major blip, for a second or two, every night snip it, I found that the config file was set to the original code... and I apccontrol isn't flagged as a config file in the rpm ./etc/apcupsd/apccontrol . c /etc/apcupsd/apcupsd.conf . c /etc/apcupsd/changeme . c /etc/apcupsd/commfailure . c /etc/apcupsd/commok . c /etc/apcupsd/offbattery . c /etc/apcupsd/onbattery . c /etc/logrotate.d/apcupsd Has anyone seen this behavior? The script says # WARNING: the apccontrol file will be overwritten every time you update your # apcupsd, doing `make install'. Your own customized scripts will _not_ be # overwritten. If you wish to make changes to this file (discouraged), you # should change apccontrol.sh.in and then rerun the configure process. If you can't change apcupsd.conf config to meet your needs then _don't_ change apccontrol; add a custom script that does an exit 99 to prevent the shutdown from running. It looks like you're right... EXCEPT that you missed the part about changing apccontrol.sh.in, which appears to me to be something you get if you build apcusd, rather than just install it via yum. And there's no other obvious way to deal with not wanting to shut it down if you have multiple machines, and don't want to ever have it tell everybody to shut down. Suggestions on what I can do *other* than build the package myself? I dunno, the times I see it shut down have *not* shut down for 3 or 5 min, nor do I think that was the max left runtime. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
On Tue, 6 Nov 2012, m.r...@5-cent.us wrote: To: CentOS mailing list centos@centos.org From: m.r...@5-cent.us Subject: [CentOS] apcupsd Anyone else around using apcupsd? I seem to be seeing a problem, and I'd like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). What's happened is that a machine shut down the other day, and looking at it, I found that the config file was set to the original code... and I *KNOW*, for a fact, that I went through every single server that's attached to a UPS many months ago, after something important shut down, and fixed all of them. So, it looks like an upgrade undid my change, rather than creating apccontrol.rpmnew. Hi Mark. I've been using apcupsd for years. I'm on Centos 5.8. Don't you mean apcupsd.conf for your configuration settings? That's the one I use to configure apcupsd. Keith --- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] --- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
On Tue, Nov 06, 2012 at 05:49:57PM -0500, m.r...@5-cent.us wrote: Stephen Harris wrote: # WARNING: the apccontrol file will be overwritten every time you update your # apcupsd, doing `make install'. Your own customized scripts will _not_ be # overwritten. If you wish to make changes to this file (discouraged), you # should change apccontrol.sh.in and then rerun the configure process. If you can't change apcupsd.conf config to meet your needs then _don't_ change apccontrol; add a custom script that does an exit 99 to prevent the shutdown from running. It looks like you're right... EXCEPT that you missed the part about changing apccontrol.sh.in, which appears to me to be something you get if No I didn't. It's not relevant to rpm installs. you build apcusd, rather than just install it via yum. And there's no other obvious way to deal with not wanting to shut it down if you have multiple machines, and don't want to ever have it tell everybody to shut down. Yes there is; create a custom script for the command ($1) that you want to trap and make it exit 99; then apccontrol will not continue on to the shutdown part. Which I said previously. Suggestions on what I can do *other* than build the package myself? I Read what apccontrol does; determine the commands you want to trap (probably doshutdown, doreboot) and create a script of that name in /etc/apcupsd/ and make it exit 99. FWIW, my UPS trips many times... eg Oct 8 10:03:11 myhost apcupsd[9774]: Power failure. Oct 8 10:03:15 myhost apcupsd[9774]: Power is back. UPS running on mains. Oct 10 20:57:12 myhost apcupsd[9774]: Power failure. Oct 10 20:57:14 myhost apcupsd[9774]: Power is back. UPS running on mains. Oct 11 18:51:35 myhost apcupsd[9774]: Power failure. Oct 11 18:51:38 myhost apcupsd[9774]: Power is back. UPS running on mains. You might want to check apcaccess for expected runtime $ apcaccess | egrep 'STATUS|LOADPCT|BCHARGE|TIMELEFT|MBATTCHG|MINTIMEL' STATUS : ONLINE LOADPCT : 24.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 36.1 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, APC UPSs, and batteries, resolved
On 27 March 2010 04:47, m.r...@5-cent.us wrote: Well, here's the tale: we got a replacement kit for some APC SmartUPS 3000 - rackmount UPSs. The kit, costing about half of what APC is asking, is just the batteries, and you pull the tray out, open it up, and swap out the batteries. Except, I did this on one... and the replace battery light never went out. Not using apcupsd's apctest, not pushing the button. The five lights on the right that show power level went down to about one or two, and took an hour or two to come back up. apctest just said replace battery was the status. I put another set in. I swapped it with another UPS, and its lights went on, so it wasn't just that one. Also, these are just batteries, not chipped like an Epson inkjet print cartridge. I did the same on another a few weeks ago, and the same. Finally - I believe these had been replaced before - I went back online, and found the exact same ones. Got them in yesterday, replaced one that I'd replaced before, waited a couple hours, and pushed the test button. It thought about it, did the test, the power level only went down *one*... and the replace battery light went out. apcupsd also reports everything's wonderful. The ones that didn't do it were PowerSonic 1250 F2's. The ones that worked were BBHR5.8012. I *think* the difference is the HR. So, now I'll be going back to the original vendor, and asking for a replacement set - he doesn't seem to have BB, but if he can give me some other HR, I'll try that. The HR is high rate, which I assume means high rate of dis/charge. I'll let y'all know what happens, but at this time, my opinion is that if you see a replacement kit for RBC43's, make *SURE* that they're HR. It could be worse... Be very careful with third party kits, especially if the vendor is selling batteries not rated for high discharge rates or without any discharge rate information... Had one UPS that became ball shaped after having worked OK for 6 months with the replacements... Suffice it to say, the cost of a new UPS was more than the saving in buying cheaper batteries... d ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd, APC UPSs, and batteries, resolved
m.r...@5-cent.us wrote: Well, here's the tale: we got a replacement kit for some APC SmartUPS 3000 - rackmount UPSs. The kit, costing about half of what APC is asking, is just the batteries, and you pull the tray out, open it up, and swap out the batteries. Except, I did this on one... and the replace battery light never went out. Not using apcupsd's apctest, not pushing the button. The five lights on the right that show power level went down to about one or two, and took an hour or two to come back up. apctest just said replace battery was the status most UPS's suggest a 24 hour charge before checking. just a comment, but the *first* thing I do when I have a battery fault is break out my volt meter and measure the voltage of the whole string and the voltage of the invidivual batteries. '12V' batteries are about 13.6V when fully charged, and if they are only 12v, they are at least 80% discharged.however, when they first come off a charger, they have a 'surface charge' a half volt or so higher, so you need to let them 'rest' for awhile (4 hours?) before reading hte voltage if you want an accurate result. '6V' batteries, half these numbers. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
m.r...@5-cent.us wrote: Here's an odd one: I installed apcupsd, and it works with most of our UPSs. I'd swear it worked on this one. Then I replaced the Gin-u-wine APC batteries, which were dead, with new ones, non-APC. They're just dumb batteries, no chips or whatever on them. If I hook it up using a serial cable, I can get info. If I hook it up the way I had it, with APC's weird USB cable - and this is the way it was working before - it fails. I run apctest, and it gives me: Attached to driver: usb sharenet.type = DISABLE cable.type = USB_CABLE You are using a USB cable type, so I'm entering USB test mode mode.type = USB_UPS Setting up the port ... Hello, this is the apcupsd Cable Test program. This part of apctest is for testing USB UPSes. Getting UPS capabilities...SUCCESS Then I tell it to do the self test, and get: This test instructs the UPS to perform a self-test operation and reports the result when the test completes. Clearing previous self test result...CLEARED Initiating self test...INITIATED Waiting for test to complete...ERROR READING STATUS 12.976 apcupsd: linux-usb.c:802 HIDIOCGREPORT for function SelftestStatus failed. ERR=Input/output error Now, I've even found an rpm that was *not* two+ years old, as what comes with CentOS 5.4, current update, and get the same error. In addition, even though the batteries are fully charged, and the info I get via the serial cable says they're at 100%, the red change battery light is still on on the front of the UPS. Hitting the test button doesn't help; I was hoping running the self-test that's available via the USB connection would reset it, but I can't do that. Any clues for the poor? mark Funny, after reading the above, I decided to try the apcupsd with my new fancy APC with the LCD display and everything. Got very similar results. Gnome Power Manager recognizes it from the get go, just with decreased functionality. It would be nice to have Centos able to 'plug' into all of its features and diagnostics. I'm running 5.4 on a hardware raid 10 serverold Adaptec 2400A with 128 megs of cache. This machine seems to have problems with the partition managers as well. Could LVM be getting in the way somehow? Ed ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] apcupsd
m.r...@5-cent.us wrote: Here's an odd one: I installed apcupsd, and it works with most of our UPSs. I'd swear it worked on this one. Then I replaced the Gin-u-wine APC batteries, which were dead, with new ones, non-APC. They're just dumb batteries, no chips or whatever on them. If I hook it up using a serial cable, I can get info. If I hook it up the way I had it, with APC's weird USB cable - and this is the way it was working before - it fails. I run apctest, and it gives me: Attached to driver: usb sharenet.type = DISABLE cable.type = USB_CABLE You are using a USB cable type, so I'm entering USB test mode mode.type = USB_UPS Setting up the port ... Hello, this is the apcupsd Cable Test program. This part of apctest is for testing USB UPSes. Getting UPS capabilities...SUCCESS Then I tell it to do the self test, and get: This test instructs the UPS to perform a self-test operation and reports the result when the test completes. Clearing previous self test result...CLEARED Initiating self test...INITIATED Waiting for test to complete...ERROR READING STATUS 12.976 apcupsd: linux-usb.c:802 HIDIOCGREPORT for function SelftestStatus failed. ERR=Input/output error Now, I've even found an rpm that was *not* two+ years old, as what comes with CentOS 5.4, current update, and get the same error. In addition, even though the batteries are fully charged, and the info I get via the serial cable says they're at 100%, the red change battery light is still on on the front of the UPS. Hitting the test button doesn't help; I was hoping running the self-test that's available via the USB connection would reset it, but I can't do that. Any clues for the poor? Funny, after reading the above, I decided to try the apcupsd with my new fancy APC with the LCD display and everything. Got very similar results. Gnome Power Manager recognizes it from the get go, just with decreased functionality. It would be nice to have Centos able to 'plug' into all of its features and diagnostics. I'm running 5.4 on a hardware raid 10 serverold Adaptec 2400A with 128 megs of cache. This machine seems to have problems with the partition managers as well. Could LVM be getting in the way somehow? Nope - we're not using LVM. And apcupsd's apctest is command line. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] APCUPSD port 3551 permission problem
On Sat, 2009-03-28 at 14:36 -0600, Joseph L. Casale wrote: I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. Ok port 3551 udp/tcp has been added to the (running) firewall. Are you attempting to run the agent on a machine *without* the ups comm connected to it, such that it will receive status from the server that does have it connected and shutdown when that remote agent that *is* monitoring the ups suggests it should? I don't think so, I think your ups is connected to the server that is running the agent. You need not add this port to the firewall. It talks to itself over the loopback adapter. You're quite correct sir. My misunderstanding on how a firewall and the computer software may interconnect. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ?Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the problem? What should I name it? apcupsd? Group? Below your gui correctly identifies that data field as the pid:) My sincere apologies. I know better. I must have been too tired. The status field of the Service Configuration GUI says: apcupsd (pid 2419) is running... Error contacting host localhost port 3551: Connection refused You have suggested the NETSERVER directive be off, but you want a client side app to communicate with it:) Turn that on and restart it. OK. Did that. Now listening on 127.0.0.1:3551 tcp instead of Unix DGRAM. Thanks for the help! -- Bob Taylor ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] APCUPSD port 3551 permission problem
I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. Ok port 3551 udp/tcp has been added to the (running) firewall. Are you attempting to run the agent on a machine *without* the ups comm connected to it, such that it will receive status from the server that does have it connected and shutdown when that remote agent that *is* monitoring the ups suggests it should? I don't think so, I think your ups is connected to the server that is running the agent. You need not add this port to the firewall. It talks to itself over the loopback adapter. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ?Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the problem? What should I name it? apcupsd? Group? Below your gui correctly identifies that data field as the pid:) The status field of the Service Configuration GUI says: apcupsd (pid 2419) is running... Error contacting host localhost port 3551: Connection refused You have suggested the NETSERVER directive be off, but you want a client side app to communicate with it:) Turn that on and restart it. jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
