[Nut-upsuser] false low battery alarm
Hi, I have two types of UPS devices and one of them (APC) gave me a false low battery alert. I can't reproduce the problem... Also, there was nothing apparently wrong with the UPS at the time of the false alert. All I could do was grab the driver values within a minute after the low battery notification. These are the values: battery.runtime.low : 120 battery.voltage : 55.65 battery.voltage.nominal : 048 device.mfr : APC device.model : SMART-UPS 5000 RM DL4 device.serial : CS0603110575 device.type : ups driver.name : apcsmart driver.parameter.pollinterval : 2 driver.parameter.port : /dev/UPS-1 driver.version : 2.6.3 driver.version.internal : 3.0 input.frequency : 50.00 input.quality : FF input.sensitivity : H input.transfer.high : 253 input.transfer.low : 196 input.transfer.reason : simulated power failure or UPS test input.voltage : 224.9 input.voltage.maximum : 224.9 input.voltage.minimum : 223.6 output.voltage : 224.9 output.voltage.nominal : 230 ups.delay.shutdown : 020 ups.delay.start : 000 ups.firmware : 112.1DL4.I ups.id : UPS_IDEN ups.load : 069.6 ups.mfr : APC ups.mfr.date : 01/10/06 ups.model : SMART-UPS 5000 RM DL4 ups.serial : CS0603110575 ups.status : OL ups.temperature : 027.4 ups.test.interval : 1209600 ups.test.result : NO The NUT version installed is 2.6.3 and I'm using a serial-to-USB hub (1 usb port and 4 serial ports). The brand is ATEN, My upssched.conf contains: AT LOWBATT INF-APC@127.0.0.1 EXECUTE lowbatt-now-apc and my upssched custom script notified me of the LOWBATT event. My ups.conf contains: [INF-APC] driver = apcsmart port = /dev/UPS-1 desc = UPS Monitor - ATEN port 2 - APC UPS If I were to update to nut 2.6.5 (I can't do it for now) would I solve this issue (ie. is it a known issue?)? Thanks, Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] NUT on Windows Clients
I want to try to use NUT on Linux server, but most of the servers I need to shutdown are Windows. Before I try to install I wanted to ask you how stable is the Windows Beta of NUT ? I need only the client part of the Windows port, only to shut down the Windows servers ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT on Windows Clients
Although I am not on the latest version, actually it has been two years since I upgraded, I have several Windows clients running against a Linux master that monitors multiple UPS units. On Feb 28, 2013 4:12 AM, Ilia Shapira i...@logicnet.co.il wrote: I want to try to use NUT on Linux server, but most of the servers I need to shutdown are Windows. Before I try to install I wanted to ask you how stable is the Windows Beta of NUT ? I need only the client part of the Windows port, only to shut down the Windows servers ** ** ** ** ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
On Feb 28, 2013, at 4:10 AM, Vieri wrote: input.transfer.reason : simulated power failure or UPS test Sounds like it was the UPS self test? ups.mfr.date : 01/10/06 If this is the original battery, it is certainly possible that it has built up enough internal resistance that the voltage reads normal when idle, but it dips too low during a test. ups.test.interval : 1209600 1209600 seconds = 14 days, so if it does it again in two weeks... -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Charles Lepple clep...@gmail.com wrote: wrote: input.transfer.reason : simulated power failure or UPS test Sounds like it was the UPS self test? ups.mfr.date : 01/10/06 If this is the original battery, it is certainly possible that it has built up enough internal resistance that the voltage reads normal when idle, but it dips too low during a test. ups.test.interval : 1209600 1209600 seconds = 14 days, so if it does it again in two weeks... Thanks for the explanation. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Charles Lepple clep...@gmail.com wrote: ups.mfr.date : 01/10/06 If this is the original battery, it is certainly possible that it has built up enough internal resistance that the voltage reads normal when idle, but it dips too low during a test. BTW, would you suggest changing the battery or is it an overreaction? Thanks, Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
On 02/28/2013 04:12 PM, Vieri wrote: --- On Thu, 2/28/13, Charles Lepple clep...@gmail.com wrote: ups.mfr.date : 01/10/06 If this is the original battery, it is certainly possible that it has built up enough internal resistance that the voltage reads normal when idle, but it dips too low during a test. BTW, would you suggest changing the battery or is it an overreaction? Good batteries ( for instance Yaesu, as seen in APC UPSes ) last 4 years. Normal ( usual ) ones last 2. Do the math yourself Manuel ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: Good batteries ( for instance Yaesu, as seen in APC UPSes ) last 4 years. Normal ( usual ) ones last 2. Do the math yourself Thanks for that information. Just a side question: Will the ups.mfr.date value be updated automatically by the APC ups firmware when I change the battery or will I need to set it manually? I'm asking because I'm not sure if the current battery was really installed at the time indicated by this field. I also have another (maybe related) problem. I have another 2 APC devices I'd like to monitor (apparently same model and serial numbers). However, whenever I connect a serial cable to the port on the UPS, the whole device shuts down immediately. This happens only if I connect the other end of the serial cable to either a ttyS0 port on a running motherboard or a port on a rs232-to-usb adapter (even if the usb end ISN'T connected to a NUT monitoring server). What could be happening here? This is obviously slightly off-topic because it doesn't seem to be related to the nut ups drivers. I'm just wondering what could be happening and if old batteries on relatively high load (approx. 75%) could be a reason the UPS shuts down abruptly on connecting a serial cable on both ends. IT sounds really strange though. Also, the UPS won't switch on while the serial cable is connected even if I press the UPS power-on button several times. I have to disconnect it (or at least the far end of it) in order to boot the ups. Thoughts greatly appreciated. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
Vieri wrote, On 2/28/2013 9:41 AM: --- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: Good batteries ( for instance Yaesu, as seen in APC UPSes ) last 4 years. Normal ( usual ) ones last 2. Do the math yourself Thanks for that information. Just a side question: Will the ups.mfr.date value be updated automatically by the APC ups firmware when I change the battery or will I need to set it manually? I'm asking because I'm not sure if the current battery was really installed at the time indicated by this field. Where APC has provided a value for battery mfg date, it has always been the same as the UPS mfg date. The value isn't automatically updated and NUT doesn't (from what I've seen) provide a way to update it manually. Before getting new batteries, you might want to check the float voltage with a good multimeter. 55.65 is rather high (~2.32/cell), but I wouldn't trust what the UPS says. Smart-UPS's can be bad about overcharging their batteries. It can be adjusted by software in some cases. I also have another (maybe related) problem. I have another 2 APC devices I'd like to monitor (apparently same model and serial numbers). However, whenever I connect a serial cable to the port on the UPS, the whole device shuts down immediately. This happens only if I connect the other end of the serial cable to either a ttyS0 port on a running motherboard or a port on a rs232-to-usb adapter (even if the usb end ISN'T connected to a NUT monitoring server). What could be happening here? This is obviously slightly off-topic because it doesn't seem to be related to the nut ups drivers. I'm just wondering what could be happening and if old batteries on relatively high load (approx. 75%) could be a reason the UPS shuts down abruptly on connecting a serial cable on both ends. IT sounds really strange though. Also, the UPS won't switch on while the serial cable is connected even if I press the UPS power-on button several times. I have to disconnect it (or at least the far end of it) in order to boot the ups. Are you using APC's supplied serial cable? They have special wiring and it varies depending on UPS model. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Kris Jordan nut...@sagebrushnetworks.com wrote: Are you using APC's supplied serial cable? They have special wiring and it varies depending on UPS model. The 3 APC ups devices are identical (same model/serial number) and I'm successfully monitoring one of them with a serial cable connected to an RS232-USB adapter. I'm using the exact same serial cable (checked the pin layout) and the other 2 are dying on me. I DON'T have the original cables because these ups devices were already installed when I got there and noone bothered storing those cables somewhere. Maybe I could find the serial cable pin outs on the manufacturer's web site but I'm supposing the cable I'm using is fine since it's working with an identical model. Nevertheless I'll take some extra time to search for the ups cables just in case I do find them and they really are different. Thanks for the hint. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
On 02/28/2013 07:55 PM, Kris Jordan wrote: Vieri wrote, On 2/28/2013 9:41 AM: --- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: Good batteries ( for instance Yaesu, as seen in APC UPSes ) last 4 years. Normal ( usual ) ones last 2. Do the math yourself Thanks for that information. Just a side question: Will the ups.mfr.date value be updated automatically by the APC ups firmware when I change the battery or will I need to set it manually? I'm asking because I'm not sure if the current battery was really installed at the time indicated by this field. Where APC has provided a value for battery mfg date, it has always been the same as the UPS mfg date. The value isn't automatically updated and NUT doesn't (from what I've seen) provide a way to update it manually. I had to use apctest from the apcupsd suite to do that Before getting new batteries, you might want to check the float voltage with a good multimeter. 55.65 is rather high (~2.32/cell), but I wouldn't trust what the UPS says. Smart-UPS's can be bad about overcharging their batteries. It can be adjusted by software in some cases. I also have another (maybe related) problem. I have another 2 APC devices I'd like to monitor (apparently same model and serial numbers). However, whenever I connect a serial cable to the port on the UPS, the whole device shuts down immediately. This happens only if I connect the other end of the serial cable to either a ttyS0 port on a running motherboard or a port on a rs232-to-usb adapter (even if the usb end ISN'T connected to a NUT monitoring server). my APC SmartUPS 1000 -/SU1000I/ shuts down the very instant I connect it to my workstation using a serial cable that I had handy ( received together with a switch ). I guess that the incorrect wiring makes the UPS go nuts. What could be happening here? This is obviously slightly off-topic because it doesn't seem to be related to the nut ups drivers. I'm just wondering what could be happening and if old batteries on relatively high load (approx. 75%) could be a reason the UPS shuts down abruptly on connecting a serial cable on both ends. IT sounds really strange though. Also, the UPS won't switch on while the serial cable is connected even if I press the UPS power-on button several times. I have to disconnect it (or at least the far end of it) in order to boot the ups. Are you using APC's supplied serial cable? They have special wiring and it varies depending on UPS model. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Ben Kamen bka...@benjammin.net wrote: No. The mfr date is a constant. There IS a user modifiable field for the last battery changeout date. It's only edited by you (the user/admin) OK, thanks. I'll look for it. You batteries have died. If I cut the main power supply then the UPS batteries seem to work fine and serve the devices behind it for a few minutes (normal load: 75%). I'm not an expert in this field so I don't understand why the batteries die when connecting a serial cable but don't die when they're not powered anymore and the UPS is on battery. Maybe it's a wiring/short circuit issue or maybe it really is related to the batteries or both. It's wise to run a calibration once or twice a month with a self test filling in the weeks between (maybe once a week). I did more then a self test. I cut the main power off. But I'll perform another one soon just to make sure the batteries are ok. Thanks for all the feedback. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] (no subject)
I am working with a Middle Atlantic IP controllable UPS. I have found that it is made by CyberPower and is controlled via SNMP. There are some controls using the auto SNMP driver that do not show up with uspcmd -l $UPSNAME. Is there a way to use a manufacturer supplied .mib file to control this piece? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: my APC SmartUPS 1000 -SU1000I shuts down the very instant I connect it to my workstation using a serial cable that I had handy ( received together with a switch ). I guess that the incorrect wiring makes the UPS go nuts. Ah... great, well sort of. At least now I know it could be a serial cable wiring issue. Still, I can't understand why the serial cable I'm using on 1 APC model works fine but if I use that same cable on another (identical) APC then it shuts down immediately. (I double-checked model name and serial numbers behind the UPS devices) Anyway, I'll try to get the official serial cables just to rule out wiring issues. Thanks for helping. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
Ben Kamen wrote, On 2/28/2013 10:08 AM: On 2013-02-28 11:55 AM, Kris Jordan wrote: Vieri wrote, On 2/28/2013 9:41 AM: --- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: Will the ups.mfr.date value be updated automatically by the APC ups firmware when I change the battery or will I need to set it manually? I'm asking because I'm not sure if the current battery was really installed at the time indicated by this field. Where APC has provided a value for battery mfg date, it has always been the same as the UPS mfg date. The value isn't automatically updated and NUT doesn't (from what I've seen) provide a way to update it manually. The Nut Gnome client does allow updating the battery changeout value. the field in question is: battery.date I've only seen it as a read-only value (not in upsrw). Have you tried changing it in that client? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
Ben Kamen wrote, On 2/28/2013 11:52 AM: On 2013-02-28 1:48 PM, Kris Jordan wrote: Ben Kamen wrote, On 2/28/2013 10:08 AM: On 2013-02-28 11:55 AM, Kris Jordan wrote: Vieri wrote, On 2/28/2013 9:41 AM: --- On Thu, 2/28/13, Manuel Wolfshant wo...@nobugconsulting.ro wrote: Will the ups.mfr.date value be updated automatically by the APC ups firmware when I change the battery or will I need to set it manually? I'm asking because I'm not sure if the current battery was really installed at the time indicated by this field. Where APC has provided a value for battery mfg date, it has always been the same as the UPS mfg date. The value isn't automatically updated and NUT doesn't (from what I've seen) provide a way to update it manually. The Nut Gnome client does allow updating the battery changeout value. the field in question is: battery.date I've only seen it as a read-only value (not in upsrw). Have you tried changing it in that client? Yep. Just did it again now as a sanity check. Seems to work (barring a complete shutdown of my web/dns/mail server and all systems to make sure it sticks in the UPS too) Restarting NUT should be enough to check. So NUT probably does support it on certain models. I have a bunch of APC RS's that can have their battery date updated using apctest, but not with NUT. Not a big deal though. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
Vieri wrote, On 2/28/2013 10:17 AM: --- On Thu, 2/28/13, Kris Jordan nut...@sagebrushnetworks.com wrote: Are you using APC's supplied serial cable? They have special wiring and it varies depending on UPS model. Nevertheless I'll take some extra time to search for the ups cables just in case I do find them and they really are different. Look for a code on the cable, like 940-0024C. http://www.networkupstools.org/cables.html http://www.apcupsd.com/manual/manual.html#cables ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] false low battery alarm
--- On Thu, 2/28/13, Kris Jordan nut...@sagebrushnetworks.com wrote: Oh, same cable from another identical UPS that works. Try resetting that UPS; it goes something like this: Unplug, disconnect the batteries, and press/hold the buttons to make sure the ups is completely dead. Does that help? I'm going to have to move the production servers to another UPS (actually most servers have dual power supplies each connected to a different UPS but network switches don't). I'll try that asap in a few days. Thanks for pointing that out. Vieri ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple clep...@gmail.com wrote: On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? Haven't tried... An Emerson support person sent me an updated version of their software, which offers me an USB port to connect but it fails to communicate with the UPS... Tomorrow will be windows tested... -- Charles Lepple clepple@gmail -- Marcelo ¿No será acaso que esta vida moderna está teniendo más de moderna que de vida? (Mafalda) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
