Nut upsdev - Feb 2014 - Question on support for Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower on Freebsd 9.1.

Charles,

We run everything as "root"  :)

However, we are using NUT 2.6.5.

Are we missing something by running 2.6.5 rather then
2.7.1?  If so, I can build/install 2.7.1.

Thx
chris


Would On 2/4/14, 9:05 PM, Charles Lepple wrote:
> On Feb 4, 2014, at 9:05 AM, Chris Duffy wrote:
>
>> ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps)
pwr=ON
> [...]
>>   idVendor = 0x06da
>>    idProduct = 0x0005
> This VID:PID combination should be handled by blazer_usb. In NUT 2.7.1 and
later, this would be covered by nutdrv_qx as well.
>
>> I am running all the ups programs as root, i.e. "ps -aux"
shows:
>>
>> root   39901   0.0  0.0  22388  3860 ??  Is   12:57AM     0:00.00
/usr/local/bin/upslog -s UPSonic at localhost -l /var/log/ups.log -i       300
-u root
>> root   39976   0.0  0.0  22392  3804 ??  Is   12:57AM     0:00.00
/usr/local/sbin/upsmon -u root localhost
>> root   39978   0.0  0.0  22392  3900 ??  S    12:57AM     0:00.01
/usr/local/sbin/upsmon -u root localhost
> The key program to run with "-u root" is the driver.
>
> When I mentioned logs, I was thinking syslog (/var/log/messages, probably).
I hadn't considered upslog, but apparently the *BSD ports tree starts a copy
by default.
>
> For instance: /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D
>
>> The /var/log/ups.log does not have much in it either that
>> makes sense....maybe I need a utility to decode it?
>> Sample lines from the is file are:
>>
>> 20140131 103652 NA NA NA [NA] NA NA
> upslog basically condenses the output of upsc into one line per polling
interval, but this falls apart if the driver hasn't started. (The error
message from upsc is more descriptive, since it isn't trying to force it
into a bunch of columns). Once the driver is running, you will see numbers
there, corresponding to the default format string:
>
>     http://www.networkupstools.org/docs/man/upslog.html
>

-- 
Chris Duffy
Product Support
Small Tree Communications
www.small-tree.com
Direct 651-209-6509 X305
Mobil 651-303-9613
Skype:cjdwoodbury
Yahoo:chris_duffy6288
AIM/Google:cjdwoodbury at gmail.com

Charles,

I forgot.....
I have attached a tar file of
the ups/nut related config files
so you can see what I am using ....

Regards
chris

On 2/5/14, 9:12 AM, Chris Duffy wrote:
> Charles,
>
> We run everything as "root"  :)
>
> However, we are using NUT 2.6.5.
>
> Are we missing something by running 2.6.5 rather then
> 2.7.1?  If so, I can build/install 2.7.1.
>
> Thx
> chris
>
>
> Would On 2/4/14, 9:05 PM, Charles Lepple wrote:
>> On Feb 4, 2014, at 9:05 AM, Chris Duffy wrote:
>>
>>> ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW
(1.5Mbps)
>>> pwr=ON
>> [...]
>>>   idVendor = 0x06da
>>>    idProduct = 0x0005
>> This VID:PID combination should be handled by blazer_usb. In NUT 
>> 2.7.1 and later, this would be covered by nutdrv_qx as well.
>>
>>> I am running all the ups programs as root, i.e. "ps -aux"
shows:
>>>
>>> root   39901   0.0  0.0  22388  3860 ??  Is   12:57AM 0:00.00 
>>> /usr/local/bin/upslog -s UPSonic at localhost -l /var/log/ups.log 
>>> -i       300 -u root
>>> root   39976   0.0  0.0  22392  3804 ??  Is   12:57AM 0:00.00 
>>> /usr/local/sbin/upsmon -u root localhost
>>> root   39978   0.0  0.0  22392  3900 ??  S    12:57AM 0:00.01 
>>> /usr/local/sbin/upsmon -u root localhost
>> The key program to run with "-u root" is the driver.
>>
>> When I mentioned logs, I was thinking syslog (/var/log/messages, 
>> probably). I hadn't considered upslog, but apparently the *BSD
ports
>> tree starts a copy by default.
>>
>> For instance: /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D
>>
>>> The /var/log/ups.log does not have much in it either that
>>> makes sense....maybe I need a utility to decode it?
>>> Sample lines from the is file are:
>>>
>>> 20140131 103652 NA NA NA [NA] NA NA
>> upslog basically condenses the output of upsc into one line per 
>> polling interval, but this falls apart if the driver hasn't
started.
>> (The error message from upsc is more descriptive, since it isn't 
>> trying to force it into a bunch of columns). Once the driver is 
>> running, you will see numbers there, corresponding to the default 
>> format string:
>>
>>     http://www.networkupstools.org/docs/man/upslog.html
>>
>
>

-- 
Chris Duffy
Product Support
Small Tree Communications
www.small-tree.com
Direct 651-209-6509 X305
Mobil 651-303-9613
Skype:cjdwoodbury
Yahoo:chris_duffy6288
AIM/Google:cjdwoodbury at gmail.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nut-tar
Type: application/octet-stream
Size: 7680 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140205/9aae2b10/attachment-0001.obj>

On Feb 5, 2014, at 10:12 AM, Chris Duffy wrote:
> However, we are using NUT 2.6.5.
> 
> Are we missing something by running 2.6.5 rather then
> 2.7.1?  If so, I can build/install 2.7.1.
Well, 2.6.5 is from August 2012, so it's not the newest. And eventually, we
would like people to switch to the shiny new nutdrv_qx driver which is in 2.7.1.
But I'm pretty much guessing here until I see the logs from starting up the
driver. For now, let's get the log messages from the 2.6.5 driver, and
figure out whether it's something that has definitely been fixed in later
versions, or if we need to go to something post-2.7.1 from Git.

Please run this:

   /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D

and send the output back to the list.

-- 
Charles Lepple
clepple at gmail

Charles,

the out from the command below as well as the system.log file
are below your email.

It does look like a permission issue but what one?

Thx
chris


On 2/5/14, 6:43 PM, Charles Lepple wrote:
> On Feb 5, 2014, at 10:12 AM, Chris Duffy wrote:
>
>> However, we are using NUT 2.6.5.
>>
>> Are we missing something by running 2.6.5 rather then
>> 2.7.1?  If so, I can build/install 2.7.1.
> Well, 2.6.5 is from August 2012, so it's not the newest. And
eventually, we would like people to switch to the shiny new nutdrv_qx driver
which is in 2.7.1. But I'm pretty much guessing here until I see the logs
from starting up the driver. For now, let's get the log messages from the
2.6.5 driver, and figure out whether it's something that has definitely been
fixed in later versions, or if we need to go to something post-2.7.1 from Git.
>
> Please run this:
>
>     /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D
>
> and send the output back to the list.
>
Output from the above command:

    0.000000    debug level is '1'
    0.248714    Supported UPS detected with megatec protocol
    1.268575    Permissions problem: Input/output error
Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 
(2.6.5-Unversioned directory)


/var/log/system.log entries but they do not come out as a result
of the above command....they just come out in large intervals:


Feb  6 12:09:15 smalltree upsmon[3091]: UPS [UPSonic at localhost]: connect 
failed: Connection failure: Connection refused





-- 
Chris Duffy
Product Support
Small Tree Communications
www.small-tree.com
Direct 651-209-6509 X305
Mobil 651-303-9613
Skype:cjdwoodbury
Yahoo:chris_duffy6288
AIM/Google:cjdwoodbury at gmail.com