Re: [Fwd: Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)]

2006-11-15 Thread Kjell Claesson
Hi Doug, ons 2006-11-15 klockan 22:22 -0500 skrev Doug Reynolds: 8 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 num

Re: [Nut-upsuser] Tripp Lite OMNI900LCD

2006-11-15 Thread Bryan Bond
I spent much more time with it tonight, and it appears to be working correctly. I will let you know if I am still having issues. Peter Selinger <[EMAIL PROTECTED]> wrote: Hi Bryan, thanks for your report. I am not sure what issue you are referring to. All the output you posted appears to be nor

Re: [Nut-upsuser] Spurious messages on start

2006-11-15 Thread Pedro Côrte-Real
On 11/16/06, Peter Selinger <[EMAIL PROTECTED]> wrote: =?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 do

Re: [Nut-upsuser] Spurious messages on start

2006-11-15 Thread Peter Selinger
=?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 __

[Fwd: Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)]

2006-11-15 Thread Doug Reynolds
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 ho

Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)

2006-11-15 Thread Doug Reynolds
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 hoo

Re: [Nut-upsuser] Tripp Lite OMNI900LCD

2006-11-15 Thread Peter Selinger
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

Re: [Nut-upsuser] Spurious messages on start

2006-11-15 Thread Pedro Côrte-Real
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

Re: [Nut-upsuser] (no subject)

2006-11-15 Thread Charles Lepple
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: p

Re: [Nut-upsuser] Recommendation for big UPS (was CyberPower PR2200)

2006-11-15 Thread Jeff Tucker
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 m

Re: [Nut-upsuser] (no subject)

2006-11-15 Thread Arjen de Korte
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 fail

[Nut-upsuser] Tripp Lite OMNI900LCD

2006-11-15 Thread Bryan Bond
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

[Nut-upsuser] (no subject)

2006-11-15 Thread Mike Hill
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? Th

Re: [Nut-upsuser] CyberPower PR2200

2006-11-15 Thread Doug Reynolds
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.char

[Nut-upsuser] CyberPower PR2200

2006-11-15 Thread Jeff Tucker
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:

Re: [Nut-upsuser] Spurious messages on start

2006-11-15 Thread Arjen de Korte
> ! /sbin/upsdrvctl start >/dev/null 2>&1 && echo -n " (upsdrvctl failed)" > start-stop-daemon -S -q -p $upsd_pid -x $upsd >/dev/null 2>&1 > start-stop-daemon -S -q -p $upsmon_pid -x $upsmon >/dev/null 2>&1 Can you add '-D' as a parameter to the startup of upsmon and post the output of all t