Re: [Nut-upsuser] NUT-2.0.3 - problems on setting values
(As usual, just figured I only replied to Arnaud, not the list ... sigh) Arnaud Quette wrote: Meaby, these parameters decrease as soon as they are programmed. Reading them back never gives the programmed value. ups.delay.shutdown and ups.delay.start behaves like this on our MGE UPS. that's it. The value reported by upsc -1 appears odd to us as well. Default value ? or re-programmation failed ? default value. considering that any *.delay.* value is a timer (at least with mge units), these are decreased until 0 (action is realised, ie shutdown), and set back to -1 (not init'ed) Arnaud Interesting. Sounds reasonable, but also slightly confused me. :) How would the parameters have to be set up to shutdown outlet.1 or 2 automatically when reaching 20% battery charge then? Something on .switch and .switchable? As said, currently the server shuts down nicely and whenever it is off, we want to later shutdown outlet.1. Of course the server can just set the shutdown value for outlet.1 on shutdown, but is that the way to go for then? Is the ups.status: OL CHRG output common on MGE aswell? Thanks for pointing it out, Patrick and Arnaud. -- Andreas Rust ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT-2.0.3 - problems on setting values
[added back the list as cc] 2007/2/2, Andreas Rust [EMAIL PROTECTED]: Arnaud Quette wrote: btw, prefer to use, if possible, the latest nut release (2.0.5 currently) Would like to, but didn't feel like building an RPM and would like to stick to it for easier maintenance - especially since the UPS is physically inaccessible for me most of the time. How would the parameters have to be set up to shutdown outlet.1 or 2 automatically when reaching 20% battery charge then? Something on .switch and .switchable? this is what you seem to have already done, ie setting outlet.X.autoswitch.charge.low=20 no need to set the timer (*.delay.*) note that the outlet will directly cut the power, so you need to ensure that the things protected by this outlet are cleanly stopped before (ie calling a hook to stop a computer, ...) It's ok for the outlet to just cut off the power - but it didn't work on a test. We had set 90 for battery.charge.low and 80 for outlet.1.autoswitch.charge.low for a quick test, but outlet.1 never turned off. When we manually restored power the UPS was down to less than 70% battery charge. it work in the opposite way: set the outlet.1 to 90 and battery.charge.low to 80 if you really need the pc to shutdown first, and another appliance next, then you have to: - plug the pc into outlet.1, and set outlet.1.autoswitch.charge.low to ie 90 - plug the other appliance into outlet.2, and set outlet.1.autoswitch.charge.low to ie 80 But in this case, only the outlets will be stopped since the master pc will be off and not able to send the shutoff (UPS shutdown) order. another way would be to use the config param offdelay with a sufficient value to switch the UPS off after the outlet.2 is off (ie between 90 % and 80, you have 5 minutes, so you can set offdelay to 320 (5 mn * 60 sec + 20 sec more) The offdelay timer start at the end of the pc shutdown... I hope this will help you in finding a suitable solution to your needs. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT-2.0.3 - problems on setting values
Arnaud Quette schrieb: [completing a missing sentence...] be sure to read the mge-shut manpage, for more information and suitable value settings (ie modifying offdelay also implies to modify ondelay...) Arnaud Thanks a lot - will do! -- Andreas Rust ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] NUT-2.0.3 - problems on setting values
Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups is getting power again. To outlet.1 there are a few components like a router, a small switch and a phone connected. As to our understanding of , outlet.1.autoswitch.charge.low and outlet.1.switchable it should be possible to power off these devices at a given battery charge, right? However, using upsrw or upsset.cgi results in strange behaviour. Setting (ups|outlet.x).delay.(shutdown|start) to e.g. 120 returns some random value (102, 68, etc.). The value reported by upsc -1 appears odd to us as well. Also ups.status: OL CHRG looks strange, since the typical value should be OL only, right? Issuing upsc [EMAIL PROTECTED] results in the output: battery.charge: 100 battery.charge.low: 25 battery.runtime: 02025 driver.name: mge-shut driver.parameter.port: /dev/ttyS0 driver.version: 2.0.3 driver.version.internal: 0.65 input.frequency: 50 input.voltage: 221 outlet.0.desc: Main Outlet outlet.0.id: 0 outlet.0.switchable: 0 outlet.1.autoswitch.charge.low: 20 outlet.1.delay.shutdown: -1 outlet.1.delay.start: -1 outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 1 outlet.1.switch: 1 outlet.1.switchable: 1 outlet.2.autoswitch.charge.low: 20 outlet.2.delay.shutdown: -1 outlet.2.delay.start: -1 outlet.2.desc: PowerShare Outlet 2 outlet.2.id: 2 outlet.2.switch: 1 outlet.2.switchable: 1 output.frequency: 49 output.voltage: 222 output.voltage.target.battery: 230 output.voltage.target.line: 230 ups.delay.shutdown: -1 ups.delay.start: -1 ups.load: 21 ups.mfr: MGE UPS SYSTEMS ups.power.nominal: 800 ups.serial: unknown ups.status: OL CHRG ups.test.result: Done and passed As said, apart from control over outlet.1 and 2 things are working as we want them. Server sends me an email when it's going on battery or comes back, etc. All we'd like to achieve is to shut down outlet.1 (or 2) when battery charge drops down to 20%. On the previous server install we had FC4 running with a self-compiled nut-2.0.4 and had the exact same troubles. Any ideas? Been searching the mailing list and google without much success. Also, I currently don't have physical access to the UPS and only handle it remotely, so I cannot test much before the end of february. Just wonder if the problem is known or has been found elsewhere. l8r Andreas Rust ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT-2.0.3 - problems on setting values
At 15:26 01/02/2007, Andreas Rust wrote: Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups is getting power again. To outlet.1 there are a few components like a router, a small switch and a phone connected. As to our understanding of , outlet.1.autoswitch.charge.low and outlet.1.switchable it should be possible to power off these devices at a given battery charge, right? However, using upsrw or upsset.cgi results in strange behaviour. Setting (ups|outlet.x).delay.(shutdown|start) to e.g. 120 returns some random value (102, 68, etc.). Meaby, these parameters decrease as soon as they are programmed. Reading them back never gives the programmed value. ups.delay.shutdown and ups.delay.start behaves like this on our MGE UPS. The value reported by upsc -1 appears odd to us as well. Default value ? or re-programmation failed ? Also ups.status: OL CHRG looks strange, since the typical value should be OL only, right? Issuing upsc [EMAIL PROTECTED] results in the output: battery.charge: 100 battery.charge.low: 25 battery.runtime: 02025 driver.name: mge-shut driver.parameter.port: /dev/ttyS0 driver.version: 2.0.3 driver.version.internal: 0.65 input.frequency: 50 input.voltage: 221 outlet.0.desc: Main Outlet outlet.0.id: 0 outlet.0.switchable: 0 outlet.1.autoswitch.charge.low: 20 outlet.1.delay.shutdown: -1 outlet.1.delay.start: -1 outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 1 outlet.1.switch: 1 outlet.1.switchable: 1 outlet.2.autoswitch.charge.low: 20 outlet.2.delay.shutdown: -1 outlet.2.delay.start: -1 outlet.2.desc: PowerShare Outlet 2 outlet.2.id: 2 outlet.2.switch: 1 outlet.2.switchable: 1 output.frequency: 49 output.voltage: 222 output.voltage.target.battery: 230 output.voltage.target.line: 230 ups.delay.shutdown: -1 ups.delay.start: -1 ups.load: 21 ups.mfr: MGE UPS SYSTEMS ups.power.nominal: 800 ups.serial: unknown ups.status: OL CHRG ups.test.result: Done and passed As said, apart from control over outlet.1 and 2 things are working as we want them. Server sends me an email when it's going on battery or comes back, etc. All we'd like to achieve is to shut down outlet.1 (or 2) when battery charge drops down to 20%. On the previous server install we had FC4 running with a self-compiled nut-2.0.4 and had the exact same troubles. Any ideas? Been searching the mailing list and google without much success. Also, I currently don't have physical access to the UPS and only handle it remotely, so I cannot test much before the end of february. Just wonder if the problem is known or has been found elsewhere. l8r Andreas Rust Regards, Patrick Agrain ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT-2.0.3 - problems on setting values
salut Patrick and Andreas, 2007/2/1, Patrick Agrain [EMAIL PROTECTED]: At 15:26 01/02/2007, Andreas Rust wrote: Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups is getting power again. To outlet.1 there are a few components like a router, a small switch and a phone connected. As to our understanding of , outlet.1.autoswitch.charge.low and outlet.1.switchable it should be possible to power off these devices at a given battery charge, right? However, using upsrw or upsset.cgi results in strange behaviour. Setting (ups|outlet.x).delay.(shutdown|start) to e.g. 120 returns some random value (102, 68, etc.). Meaby, these parameters decrease as soon as they are programmed. Reading them back never gives the programmed value. ups.delay.shutdown and ups.delay.start behaves like this on our MGE UPS. that's it. The value reported by upsc -1 appears odd to us as well. Default value ? or re-programmation failed ? default value. considering that any *.delay.* value is a timer (at least with mge units), these are decreased until 0 (action is realised, ie shutdown), and set back to -1 (not init'ed) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
