./upsd -DDD -u root
Network UPS Tools upsd 2.1.0
/usr/local/ups/etc/upsd.conf is world readable
That is bad, fix it.
listen_add: added 0.0.0.0:3493
listening on 0.0.0.0 port 3493
Connected to UPS [mge-nova]: mge-nova
/usr/local/ups/etc/upsd.users is world readable
This is *really* bad,
sstate_dead: didn't hear from driver for UPS [mge-nova] for 0 seconds
Oops! For some reason you decided to set MAXAGE to 0 seconds. Please
read the appropriate section from 'man 5 upsd.conf' again. Do not set
MAXAGE to anything *lower* than the 15 second default.
I included my upsd.conf in
On 16/02/07, Arjen de Korte [EMAIL PROTECTED] wrote:
The server is reporting that it didn't hear from the server for 0 seconds,
which means that elapsed must be less than 1. So maxage must be smaller
than that, it can never be 60. Maybe the value is parsed incorrectly, so
could you try
Unfortunately it didn't seem to have any effect. I have taken a debug
of usbhid-ups starting up in case there is some info you need in
there. It's too long to include here so I put it on pastebin:
http://pastebin.com/882071
The startup of usbhid-ups seems to be OK. Could you startup upsd
On 16/02/07, Arjen de Korte [EMAIL PROTECTED] wrote:
The latter needs to be 'pollfreq', not 'pollinterval'.
Ok - changed:
root# cat ups.conf
[mge-nova]
driver=usbhid-ups
port=auto
desc=MGE Nova 600VA on Bozo
vendorid = 0463
pollfreq = 30
root#
Hi Arjen,
On 16/02/07, Arjen de Korte [EMAIL PROTECTED] wrote:
/usr/local/ups/etc/upsd.conf is world readable
That is bad, fix it.
I understand that in a production environment this would be bad, but
considering the software is not not working at this point I have
bigger fish to fry :)
fellows,
2007/2/16, Rob Wise [EMAIL PROTECTED]:
On 16/02/07, Arjen de Korte [EMAIL PROTECTED] wrote:
The latter needs to be 'pollfreq', not 'pollinterval'.
Ok - changed:
root# cat ups.conf
[mge-nova]
driver=usbhid-ups
port=auto
desc=MGE Nova 600VA on Bozo
2007/2/16, Arjen de Korte [EMAIL PROTECTED]:
My ups.conf:
[mge-nova]
driver=usbhid-ups
port=auto
desc=MGE Nova 600VA on Bozo
vendorid = 0463
pollinterval = 30
The latter needs to be 'pollfreq', not 'pollinterval'. I know this is not
documented,
Hi,
I'm working with svn trunk rev 815, testing tripplite_usb with this model. I
haven't gotten far in my testing, but thought I'd notify the list of this error
message. Is this message of any consequence, and is it worthwhile for me to
continue testing prior to resolving this? I am happy to
I'm working with svn trunk rev 815, testing tripplite_usb with this model.
I
haven't gotten far in my testing, but thought I'd notify the list of this
error
message. Is this message of any consequence, and is it worthwhile for me
to
continue testing prior to resolving this? I am happy
On Fri, Feb 16, 2007 at 04:36:12PM +0100, Arjen de Korte wrote:
Running the driver in debug mode would be helpful, to see what goes wrong.
I used the following command-line:
./tripplite_usb -u root -DD auto
Attached is the log file.
-Forest
--
Forest Bond
Computer Engineer
Logic Supply,
On 2/16/07, Forest Bond - Logic Supply [EMAIL PROTECTED] wrote:
Hi,
I'm working with svn trunk rev 815, testing tripplite_usb with this model. I
haven't gotten far in my testing, but thought I'd notify the list of this error
message. Is this message of any consequence, and is it worthwhile
Hi,
The Error reading Unit ID is normal on this model, because it does
not appear to support that particular command.
OK
The other errors look like they did not show up in the debug log
requested by Arjen - true?
On line 428:
Error reading L value: Unknown error 0
And on line 446:
Error
You are using upsd and upsdrvctl 2.0.4 together with tripplite_usb
2.0.5. These versions will not work together, since the socket format
has changed. Use everything from 2.0.5, and you should be fine
I hope.
-- Peter
Forest Bond - Logic Supply wrote:
On Fri, Feb 16, 2007 at 09:51:28PM
On Fri, Feb 16, 2007 at 05:20:45PM -0400, Peter Selinger wrote:
You are using upsd and upsdrvctl 2.0.4 together with tripplite_usb
2.0.5. These versions will not work together, since the socket format
has changed. Use everything from 2.0.5, and you should be fine
Wow. Don't know how
Charles Lepple wrote:
Can you send the output of 'upsc [EMAIL PROTECTED]'?
The '@localhost' part is optional for the version in the trunk. So
upsc name-of-ups
will behave the same as
upsc [EMAIL PROTECTED]
Might save you some typing... :-)
Best regards, Arjen
On Fri, Feb 16, 2007 at 11:03:50AM -0500, Charles Lepple wrote:
Can you send the output of 'upsc [EMAIL PROTECTED]'?
Finally
[EMAIL PROTECTED]:~# upsc [EMAIL PROTECTED]
battery.charge: 100
battery.voltage:
On 2/16/07, Arjen de Korte [EMAIL PROTECTED] wrote:
Charles Lepple wrote:
Can you send the output of 'upsc [EMAIL PROTECTED]'?
The '@localhost' part is optional for the version in the trunk. So
upsc name-of-ups
will behave the same as
upsc [EMAIL PROTECTED]
Might save you
18 matches
Mail list logo
