Re: [Nut-upsuser] Spurious messages on start
! /sbin/upsdrvctl start /dev/null 21 echo -n (upsdrvctl failed) start-stop-daemon -S -q -p $upsd_pid -x $upsd /dev/null 21 start-stop-daemon -S -q -p $upsmon_pid -x $upsmon /dev/null 21 Can you add '-D' as a parameter to the startup of upsmon and post the output of all three of these redirected to a single file? And preferably, also the relevant output of the system log file (since that will also tell us something about the relation in time). Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] CyberPower PR2200
Hi, guys. I have a new CyberPower PR2200 which I'm trying to control using NUT. It has a serial port and I'm connected serially. I am using the cyberpower driver and before a power failure it seems to mostly be working: [EMAIL PROTECTED]:~$ upsc [EMAIL PROTECTED] battery.charge: 000 driver.name: cyberpower driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 1.00 input.frequency: 60.0 input.voltage: 114 ups.firmware: 1.100 ups.load: 040 ups.mfr: CyberPower ups.model: Unknown model - 22 ups.status: OL ups.temperature: 8.0 I'm a little concerned that it says battery.charge: 000 there Anyway, when I unplug the UPS, I get a notification that the system is running on battery. Then, about 3 minutes later, the UPS clicks off and the whole thing is down. I also noticed that during this time the LED's on the UPS that show load all blink in a repeating pattern. This is a big UPS powering one machine, so I would expect it to last longer than 3 minutes. I did the same test without NUT running. After 15 minutes, the UPS still showed 75% charge level. I don't know how long it would last. Also, the LED's were not blinking. So, I suspect that the cyberpower driver is doing something to the UPS that tells it to shut down. The syslog shows the initial event with the unit going on battery, but nothing further. It doesn't appear that nut intentionally shut down the UPS. No shutdown was ever started on the machine, so it just hard crashes. Any ideas on this? I might just be out of luck with this UPS, I guess. It's a shame because these things are half the price of a comparable APC. Jeff ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] CyberPower PR2200
Jeff Tucker wrote: Hi, guys. I have a new CyberPower PR2200 which I'm trying to control using NUT. It has a serial port and I'm connected serially. I am using the cyberpower driver and before a power failure it seems to mostly be working: [EMAIL PROTECTED]:~$ upsc [EMAIL PROTECTED] battery.charge: 000 driver.name: cyberpower driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 1.00 input.frequency: 60.0 input.voltage: 114 ups.firmware: 1.100 ups.load: 040 ups.mfr: CyberPower ups.model: Unknown model - 22 ups.status: OL ups.temperature: 8.0 I'm a little concerned that it says battery.charge: 000 there Anyway, when I unplug the UPS, I get a notification that the system is running on battery. Then, about 3 minutes later, the UPS clicks off and the whole thing is down. I also noticed that during this time the LED's on the UPS that show load all blink in a repeating pattern. This is a big UPS powering one machine, so I would expect it to last longer than 3 minutes. I did the same test without NUT running. After 15 minutes, the UPS still showed 75% charge level. I don't know how long it would last. Also, the LED's were not blinking. So, I suspect that the cyberpower driver is doing something to the UPS that tells it to shut down. The syslog shows the initial event with the unit going on battery, but nothing further. It doesn't appear that nut intentionally shut down the UPS. No shutdown was ever started on the machine, so it just hard crashes. Any ideas on this? I might just be out of luck with this UPS, I guess. It's a shame because these things are half the price of a comparable APC. That is what my CyberPower 1200 does.. I changed the drivers around to work somewhat, but as you see, they don't work well. I've been working on coming up for the proper commands for the ups, but I haven't had time to swap out the UPS and hook it to my windows machine to do some serial debugging. I plan to do this during my christmas break.. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] (no subject)
I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 Any ideas? Thanks Mike ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] (no subject)
Mike Hill wrote: I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 Any ideas? If you want to use USB with NUT, you need to install the latest development version. The newhidups driver is very much 'work in progress' and a lot of problems from earlier versions have been fixed by now. Having said that, your UPS should be supported through the USB port then. Kind regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] (no subject)
On 11/15/06, Mike Hill [EMAIL PROTECTED] wrote: I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working with an MGE Pulsar Evolution 500, but I cannot get the USB interface to work. When I plug in the USB cable I get the following message in my system log: kernel: usbhid: probe of 2-1:1.0 failed with error -5 actually, this part is normal. The device is blacklisted from the kernel usbhid driver so that it can be claimed in userspace by newhidups. Did you see any error messages from the driver or other NUT components? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Spurious messages on start
On 11/14/06, Pedro Côrte-Real [EMAIL PROTECTED] wrote: On 11/14/06, Arjen de Korte [EMAIL PROTECTED] wrote: Did you also try adding a 5 second sleep between starting upsdrvctl and upsd? I think the problem lies there, upsd is trying to connect to the driver that is still in the process of starting up. Since upsd will periodically retry connecting to the driver if it failed, it will try to reconnect after 15 seconds (if memory serves). A 20 second delay for starting upsmon would blank reporting this problem. Yes, this was what I tried first and it made no difference. upsdrvctl seems to wait until the driver is fully initialized and only then goes into the background. Looks like I hadn't tried it with a 30 second sleep. Putting a sleep 30 between upsdrvctl and upsd also works so I guess the problem is there. Using -D on upsd seems to stop it from going in the background, so upsmon doesn't get to run. Since the problem seems to be between the driver and upsd that's probably ok. /var/log/daemon.log shows this: Nov 16 00:48:46 ulisses newhidups[5196]: Startup successful Nov 16 00:48:46 ulisses upsd[5197]: /etc/nut/upsd.conf is world readable Nov 16 00:48:46 ulisses upsd[5197]: Connected to UPS [mge1200]: newhidups-auto Nov 16 00:48:46 ulisses upsd[5197]: /etc/nut/upsd.users is world readable Nov 16 00:48:55 ulisses upsd[5197]: Pinging UPS [mge1200] Nov 16 00:48:57 ulisses upsd[5197]: UPS [mge1200]: dump is done Nov 16 00:49:02 ulisses upsd[5197]: Got PONG from UPS [mge1200] Nov 16 00:49:10 ulisses upsd[5197]: Pinging UPS [mge1200] Nov 16 00:49:14 ulisses upsd[5197]: Got PONG from UPS [mge1200] Nov 16 00:49:22 ulisses upsd[5197]: Pinging UPS [mge1200] Nov 16 00:49:22 ulisses upsd[5197]: Got PONG from UPS [mge1200] Nov 16 00:49:30 ulisses upsd[5197]: Pinging UPS [mge1200] Nov 16 00:49:34 ulisses upsd[5197]: Got PONG from UPS [mge1200] Nov 16 00:49:42 ulisses upsd[5197]: Pinging UPS [mge1200] (...) And outputs on the command line: /etc/nut/upsd.conf is world readable Connected to UPS [mge1200]: newhidups-auto /etc/nut/upsd.users is world readable Network UPS Tools upsd 2.0.4 Synchronizing giving up Pinging UPS [mge1200] UPS [mge1200]: dump is done Got PONG from UPS [mge1200] Pinging UPS [mge1200] Got PONG from UPS [mge1200] Pinging UPS [mge1200] (...) I guess the problem is that Synchronizing... step. Pedro. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite OMNI900LCD
Hi Bryan, thanks for your report. I am not sure what issue you are referring to. All the output you posted appears to be normal. Did the driver give you any particular problems? -- Peter Bryan Bond wrote: I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [EMAIL PROTECTED] bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 = (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable (ups.test.result) does not exist If I run ./newhidups -u root -DD auto, I get this scrolling gibberish = until I ctrl-c the process, it will continue forever if I let it. [EMAIL PROTECTED] bin]$ sudo ./newhidups -u root -DD auto Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 = (2.1.0) debug level is '2' Checking device (09AE/2005) (002/005) - VendorID: 09ae - ProductID: 2005 - Manufacturer: Tripp Lite - Product: TRIPP LITE UPS - Serial Number: 692195 B - Bus: 002 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... trying again to claim USB device... Warning: two different HID descriptors retrieved (Reportlen =3D 459 vs. = 618) HID descriptor retrieved (Reportlen =3D 618) Report descriptor retrieved (Reportlen =3D 618) Found HID device Report Descriptor size =3D 618 Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 1.00 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 2.00 Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 3.00 Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, Value: = 120.00 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, Value: = 2.00 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 24.00 Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 2.00 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, Value: 83.00 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: = 83.00 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value: = 100.00 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, = Value: 0.00 Can't find object UPS.PowerSummary.PresentStatus.TLACPresent Path: UPS.PowerSummary.PresentStatus.TLACPresent, Type: Input Can't find object UPS.PowerSummary.PresentStatus.TLCharging Path: UPS.PowerSummary.PresentStatus.TLCharging, Type: Input Can't find object UPS.PowerSummary.PresentStatus.TLDischarging Path: UPS.PowerSummary.PresentStatus.TLDischarging, Type: Input Can't find object UPS.PowerSummary.PresentStatus.TLNeedReplacement Path: UPS.PowerSummary.PresentStatus.TLNeedReplacement, Type: Input Path: UPS.PowerSummary.PresentStatus., Type: Input Path: UPS.PowerSummary.PresentStatus., Type: Input Path: UPS.PowerSummary.PresentStatus., Type: Input Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, = Value: 0.00 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: = 1.00 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, Value: = 1.00 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, Value: = 0.00Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: = Feature, Value: 0.00 Path: UPS.PowerSummary.PresentStatus., Type: Feature Path: UPS.PowerSummary.PresentStatus., Type: Feature Path: UPS.PowerSummary.PresentStatus., Type: Feature Path: UPS.BatterySystem.Battery.ConfigVoltage, Type: Feature, Value: = 12.00 Path: UPS.BatterySystem.Battery.PresentStatus.Charging, Type: Feature, = Value: 1.00 Path: UPS.BatterySystem.Battery.PresentStatus.Discharging, Type: = Feature, Value: 0.00 Path: UPS.BatterySystem.Battery.PresentStatus.NeedReplacement, Type: = Feature, Value: 0.00 Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature Path: UPS.BatterySystem.Test, Type: Feature, Value: 0.00 Path: UPS.Flow.ConfigVoltage, Type: Feature, Value: 120.00 Path: UPS.Flow.ConfigFrequency, Type: Feature, Value: 60.00 Path: UPS.Flow.ConfigApparentPower, Type: Feature, Value: 900.00 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: Feature, Value: = 65535.00 Path: UPS.OutletSystem.Outlet.0091, Type: Feature, Value: 0.00 Path: UPS.OutletSystem.Outlet.0092, Type: Feature, Value: 0.00 Path: UPS.OutletSystem.Outlet.00c7, Type: Feature, Value: 1.00 Path: UPS.0010[1].007d, Type:
[Fwd: Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)]
Jeff Tucker wrote: Doug Reynolds wrote: That is what my CyberPower 1200 does.. I changed the drivers around to work somewhat, but as you see, they don't work well. I've been working on coming up for the proper commands for the ups, but I haven't had time to swap out the UPS and hook it to my windows machine to do some serial debugging. I plan to do this during my christmas break.. OK, thanks, Doug. So, if I want a 1500-2000 VA class UPS but don't want to pay for an APC, does anyone have a recommendation for something that works right now? Hopefully something that's stable and tested as opposed to experimental. What about the CyberPower AVR1500? It doesn't have to be CyberPower, but they seem inexpensive. The docs claim it is supported. Does anyone have one that works well Help might be coming soon. I did some extensive testing tonight. I found out a lot of interesting things. I have a 1200AVR. I found out from the website that you can program Windows XP to use it as a contact-closure type of UPS. The generic windows custom UPS settings are: Power Fail/On Battery - Negative, Low Battery - Negative, UPS Shutdown - Positive. I checked these settings with a serial port monitor. When the UPS is online, CTS is ON. When UPS is on battery, CTS is OFF. I wasn't able to check out the low battery or the other settings (it takes a lot of juice to kill these ups.. at 220W, it took 45min or so). Perhaps one of the maintainers know which generic drive types that will work with the windows settings I gave. The serial cable that came with mine is a straight thru cable (black). I check it myself with an ohm meter. The ups is also a smart ups once you initialize it with a few commands.. the windows monitor program (that comes with the ups) sends: ** 0D 50 34 0D 50 34 0D 50 33 0D 50 32 0D 50 31 0D .P4.P4.P3.P2.P1. 50 37 0D 50 36 0D 50 38 0D 50 39 0D 44 0D 43 0D P7.P6.P8.P9.D.C. 44 0D 44 0D 44 0D 44 0D 44 0D 44 0D 44 0D 44 0D D.D.D.D.D.D.D.D.** and the ups sends back: ** 23 32 0D 23 42 43 31 32 30 30 20 20 20 20 2C 31 #2.#BC1200,1 2E 36 30 30 2C 30 30 30 30 30 30 30 30 30 30 30 .600,000 30 2C 43 59 42 45 52 20 50 4F 57 45 52 20 20 20 0,CYBER POWER 20 0D 23 42 43 31 32 30 30 20 20 20 20 2C 31 2E.#BC1200,1. 36 30 30 2C 30 30 30 30 30 30 30 30 30 30 30 30 600, 2C 43 59 42 45 52 20 50 4F 57 45 52 20 20 20 20 ,CYBER POWER 0D 23 31 32 2E 30 2C 30 30 32 2C 30 30 38 2E 30 .#12.0,002,008.0 2C 30 30 0D 23 31 32 30 30 2C 30 37 32 30 2C 31 ,00.#1200,0720,1 32 30 2C 34 37 2C 36 33 0D 23 31 32 30 2C 31 33 20,47,63.#120,13 38 2C 30 38 38 2C 33 35 0D 23 30 38 30 2C 30 38 8,088,35.#080,08 31 2C 30 38 32 2C 30 38 33 2C 30 38 34 2C 30 38 1,082,083,084,08 35 2C 30 38 36 2C 30 38 37 2C 30 38 38 2C 30 38 5,086,087,088,08 39 2C 30 39 30 0D 23 31 33 30 2C 31 33 31 2C 31 9,090.#130,131,1 33 32 2C 31 33 33 2C 31 33 34 2C 31 33 35 2C 31 32,133,134,135,1 33 36 2C 31 33 37 2C 31 33 38 2C 31 33 39 2C 31 36,137,138,139,1 34 30 0D 23 32 30 2C 32 35 2C 33 30 2C 33 35 2C 40.#20,25,30,35, 34 30 2C 34 35 2C 35 30 2C 35 35 2C 36 30 2C 36 40,45,50,55,60,6 35 0D 23 C3 D0 F0 0D 23 49 31 31 38 2E 30 4F 31 5.#ÃÐð.#I118.0O1 31 38 2E 30 4C 30 30 33 42 30 37 35 54 30 34 31 18.0L003B075T041 46 30 36 30 2E 30 53 80 80 0D 23 30 0D 23 49 31 F060.0S€€.#0.** once the UPS is ready to roll, the program polls the ups with a D and a carriage return, and the UPS sends the current info back: #I118.0O118.0L003B075T041F060.0S€€ the I118 is the line voltage. when the UPS is on battery, this drops to I000 the O0118 is the battery voltage, stays ~ 0120 until the ups dies the 0L003 is the power being used by the UPS. multiply that number by 7.2 for the waltage been supplied through the UPS (whether is it on or off line) the B075 is the percentage of battery left. 100 = 100%, 75=75% etc etc I haven't figured out what the F060 or the 0S is. they always stayed the same. when the UPS went dead and turned off, it would still reply with the same reply, but all the numbers were zeros.€€ if anyone can help me put this into a driver, let me know... I also just tried running mine as genericups upstype=7, and it seems to be showing online/onbattery, so until I finish a smart driver, that one should work. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Spurious messages on start
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote: /etc/nut/upsd.conf is world readable /etc/nut/upsd.users is world readable That is probably a really bad idea, since /usr/etc/upsd.users contains passwords that would allow any user to shut down your machine. -- Peter ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Fwd: Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)]
Hi Doug, ons 2006-11-15 klockan 22:22 -0500 skrev Doug Reynolds: 8snip I haven't figured out what the F060 or the 0S is. they always stayed the same. when the UPS went dead and turned off, it would still reply with the same reply, but all the numbers were zeros.€€ 8snip I think the F is line frequency 60Hz. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
