Re: [Nut-upsuser] CyberPower Value 2200E-GP
Citeren David Varley davidavar...@gmail.com: I've just set up a CyberPower Value 2200E-GP on a system running Lucid AMD64, with the current NUT package via apt-get, and it seems to be working fine for me with the usbhid-ups driver, so I guess it can go in the HCL? Probably. We'll just need a little more information like the 'upsc' output for this UPS (to see if we need to add additional mappings). I'm using the system to host several virtual servers under KVM, and to make things simple I set it up to hibernate rather than shutdown, that way all the guest OS don't have to be shutdown, they just carry on happily from where they were after power is restored. To achieve this I timed how long it take to go into hibernation (30-40 seconds), and set the UPS to shutdown after 60 seconds via the driver offdelay setting. I then set: SHUTDOWNCMD /sbin/upsdrvctl shutdown;/usr/sbin/pm-hibernate and under test it works well. I'm don't know if there is a better or right way to do this, obviously the heuristically determined off delay is a bit of a risk, and as the system doesn't actually shut down perhaps there will be other problems with NUT? The /etc/killpower flag isn't deleted, for instance. Remember that the 'upsd' server will latch the FSD (forced shutdown) flag when it has detected an OB LB condition. The only way to reset this, is to restart NUT. Otherwise after resuming, NUT will immediately shutdown again. Many systems will allow you to run scripts when going into hibernation and after resuming. You'll want to stop NUT when hibernating and restart it when resuming (this will take care of the /etc/killpower flag as well). I'd prefer to run the 'upsdrvctl shutdown' command from the hibernation script as well. Also remember that there is a slight risk that if hibernation fails, the UPS will power off anyway. If that worries you, it might be better to stick with a full shutdown of the system. I've attached the output of *usbhid-ups -DDD -a 2200LCD* as there seem to be several errors reported in there. I can see the subdriver doesn't find the serial number, for example, while the pwrstat code supplied by CyberPower does. There are some issues with the usbhid-ups driver in nut-2.4.3. Most of these have been resolved in the development version of NUT. I would be grateful if you could try out this. Most (if not all) of the errors you're seeing now should be fixed. We could add some code to add reading the serial number, but we really need it before claiming the device (which seems to be broken in either your UPS or the version of libusb you're using). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Things seem to be working but upscmd does nothing
2010/12/15 Arjen de Korte nut+us...@de-korte.org nut%2bus...@de-korte.org Citeren Richard richard-...@rain4us.net: (...) upsd.users [nutmon] password = easy nutmon master # or upsmon slave If this is all there is in this file, you've missed setting up the permitted instcmds and actions for this user. See 'man 5 upsd.users' for an explanation. Failing to set this up, will default to not allowing instcmds and variable settings at all. Note that you have a typo error. the directive is upsmon master, not nutmon master. moreover, as Arjen stated, you need to tell if/what the NUT user can do. the prefered way is to have a separate user for this, like: [admin] password = dummypass actions = SET instcmds = ALL cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software 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] Setting Battery Runtime Low
2010/12/15 Arjen de Korte Citeren Poulton, Stuart W.L.: rcs-manage-1:/var/log # upsrw phys-eaton [battery.runtime.low] Remaining battery runtime when UPS switches to LB (seconds) Type: UNKNOWN (unrecognized) The definition in the MIB to NUT mapping is lacking a type for this variable. Clients expect it to be either a string or an enumerated value and the driver doesn't report either. This needs to be fixed in the driver, there is no workaround. I suspect from this that it may not be configurable. Maybe, but until this is fixed in the driver it's a driver bug. Note that the snmp-ups driver is currently in dire need of an active developer taking over the maintenance. indeed, and a full rewrite is also needed, to support the subdrivers approach as in usbhid-ups. this would fix various issues and limitations, and would also unblock a few patch that are stagging in my TODO stack. Since I don't have a SNMP capable UPS, I can't really work on it other than the occasional fix for an obvious problem. well, your NMC (in the evolution) is SNMP capable (beside the XML/HTTP channel). depending on your exact card reference and FW version, it will expose a minimum or full set of IETF + MGE MIBS. Arjen: if needed, I can also check to send you a more suitable card, but I know that you're already quite busy. so up to you, you know who to ask ;-) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software 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] Setting Battery Runtime Low
Citeren Arnaud Quette aquette@gmail.com: indeed, and a full rewrite is also needed, to support the subdrivers approach as in usbhid-ups. Yes. Although it would be possible to add the lookup (forward and reverse) functions like in usbhid-ups (which would allow for better conversion between IOD - NUT values), it would be much better to start from scratch here. Since I don't have a SNMP capable UPS, I can't really work on it other than the occasional fix for an obvious problem. well, your NMC (in the evolution) is SNMP capable (beside the XML/HTTP channel). Yes and no. It indeed does talk SNMP, but as far as I can see doesn't support changing variables. The only method for changing the 'battery.runtime.low' parameter, is through the HTTP interface. I've not been able to change a single variable through the SNMP interface. depending on your exact card reference and FW version, it will expose a minimum or full set of IETF + MGE MIBS. Currently it reports Network Management Card V6.00 HB (SNMP) Network Management Card/Mosaic 4M 16M/HB (XML) This is the latest firmware I could find for the NMC 66102 (technical level 09). Arjen: if needed, I can also check to send you a more suitable card, but I know that you're already quite busy. It would probably be easier to have access to a device with native SNMP support. I don't need physical access to it, it's enough if I can reach it through the net. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] upsdrvctl doesn't seem to start with init.d
I can run upsdrvctl start and it starts fine. On computer boot, however, it doesn't start properly. I'm trying to find the logs which would give more detail, but I'm not sure where they are. I see no logs in /etc/nut or /var/log. I don't know if this helps, but it looks like there's a problem with the PID file generation: when I run upsdrvctl stop I get an error about a missing PID file. My UPS driver is the apcsmart driver. Thank you for your help. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsdrvctl doesn't seem to start with init.d
2010/12/16 Zach La Celle lace...@roboticresearch.com I can run upsdrvctl start and it starts fine. On computer boot, however, it doesn't start properly. I'm trying to find the logs which would give more detail, but I'm not sure where they are. I see no logs in /etc/nut or /var/log. try running directly your driver in debug mode (as root), ie: $ /path/to/apcsmart -DDD -a upsname and send us back the output. have you also verified device privileges? (ie ls -l /dev/ttyS0 or something like that) cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software 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] CyberPower Value 2200E-GP
Arjen, I've appended the output of upsc I'll keep in mind your warning about the upsd server latching the FSD flag and requiring a restart, however I'm just running the packaged Ubuntu/Lucid version at this stage so I don't have too much flexibility. NUT seems to be set up as a service, so that it starts correctly on system boot, however it was probably assumed it would run until a system shutdown as the scripts don't handle stopping the service. When I : *sudo service nut stop* the NUT processes continue running. I doubt I'll have a chance to spend more time on this before Christmas. Regards, David da...@xeno:/etc/nut$ upsc 2200...@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3270 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: Value 2200E device.type: ups driver.name: usbhid-ups driver.parameter.offdelay: 60 driver.parameter.ondelay: 70 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0501 driver.parameter.vendorid: 0764 driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 263 input.transfer.low: -96 input.voltage: 240.0 input.voltage.nominal: 230 output.voltage: 240.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 14 ups.mfr: CPS ups.model: Value 2200E ups.productid: 0501 ups.realpower.nominal: 296 ups.status: FSD OL ups.test.result: Done and passed ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764 ___ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
