[Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U

Wed Sep 23 13:22:25 UTC 2015

>> 
>> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) 
> 
>Which version of FreeBSD is this based on? 

I also included the Motherboard and processor so if there is anything those devices affect with this like some weird quarks only found with them. Also, the only difference between this box and the CentOS 6.7 one, is the processor is a x5650. other than that. they are the same. 

Version 10.2.0.2 - Prester (revision 1814) 
Build date Sun Aug 30 21:05:02 CEST 2015 
Platform OS FreeBSD Revision: 199506 
FreeBSD 10.2-RELEASE-p2 #0 r287260M: Fri Aug 28 18:38:18 CEST 2015 
Platform x64-embedded on Intel(R) Xeon(R) CPU E5540 @ 2.53GHz 
System Supermicro X8DTH 

> 
>> When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be. Both are running Version 2.7.3. Thank you in advance. 
> 
>> FreeBSD output: 
>> 
>> device.mfr: CPS 
>> device.type: ups 
>> driver.name: usbhid-ups 
>> driver.parameter.pollfreq: 30 
>> driver.parameter.pollinterval: 2 
>> driver.parameter.port: /dev/ugen4.2 
>> driver.parameter.synchronous: no 
>> driver.version: 2.7.3 
>> driver.version.data: CyberPower HID 0.4 
>> driver.version.internal: 0.39 
>> ups.mfr: CPS 
>> ups.productid: 0601 
>> ups.status: OB 
>> ups.vendorid: 0764 
> 
>Note also that the list of variables is much shorter than some of the other CyberPower HID devices: 
> 
> http://www.networkupstools.org/ddl/Cyber_Power_Systems/index.html 
> 
>Can you open up a root shell, kill the old `usbhid-ups` process, and run it from the command line? 
> 
> /usr/local/libexec/nut/usbhid-ups -a ups -DDD 
> 
>(Adjust the "-a ups" for the name that NAS4Free uses.) 
> 
>It will indefinitely, but we only need about the first 30 seconds. Please gzip the output before posting to the list. Also, please use reply-all, as this mailing list does not mangle the reply-to headers. 
This is the output from what you asked. The last line keeps repeating. Looks like the ups is refusing to connect. Not sure how to get it to connect at this point. Thank you again for your help so far. 

0.000000 UPS: server at localhost (master) (power value 1) 
0.000051 Using power down flag file /var/etc/killpower 
0.000138 debug level is '3' 
0.004778 Trying to connect to UPS [Blob at localhost] 
0.005103 UPS [Blob at localhost]: connect failed: Connection failure: Connection refused 
0.005116 do_notify: ntype 0x0005 (COMMBAD) 
0.005121 Communications with UPS Blob at localhost lost 
0.005326 Current power value: 1 
0.005341 Minimum power value: 1 

Broadcast Message from root at blob.frentzgzesh.info 
(/dev/pts/0) at 9:09 EDT... 

Communications with UPS Blob at localhost lost 

Executing command: notify 
5.318447 Trying to connect to UPS [Blob at localhost] 
5.318793 UPS [Blob at localhost]: connect failed: Connection failure: Connection refused 
5.318807 do_notify: ntype 0x0008 (NOCOMM) 
5.318813 UPS Blob at localhost is unavailable 
5.319048 Current power value: 1 
5.319064 Minimum power value: 1 

Broadcast Message from root at blob.frentzgzesh.info 
(/dev/pts/0) at 9:09 EDT... 

UPS Blob at localhost is unavailable 

Executing command: notify 
10.543965 Trying to connect to UPS [Blob at localhost] 
10.544324 UPS [Blob at localhost]: connect failed: Connection failure: Connection refused 
10.544337 Current power value: 1 
10.544343 Minimum power value: 1 

Here is the config from the xml file that NAS4Free uses to configure everything. 

<ups> 
<upsname>Blob</upsname> 
<shutdownmode>fsd</shutdownmode> 
<shutdowntimer>30</shutdowntimer> 
<email> 
<to>louis at frentzgzesh.info</to> 
<subject>UPS notification from %h on %d</subject> 
<enable/> 
</email> 
<mode>master</mode> 
<driver>usbhid-ups</driver> 
<port>/dev/ugen4.2</port> 
<desc/> 
<ip>localhost</ip> 
<monitoruser>root</monitoruser> 
<password>(removed by me)</password> 
<auxparam></auxparam> 
</ups> 

Joe Gzesh 
Sent from Zimbra Open Source Mail Server. Hosted at my House. 
Ask me how to set up your own Zimbra server. 

From: "Charles Lepple" <clepple at gmail.com> 
To: "Joseph Gzesh" <louis at frentzgzesh.info> 
Cc: nut-upsuser at lists.alioth.debian.org 
Sent: Tuesday, September 22, 2015 8:06:33 PM 
Subject: Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U 

On Sep 22, 2015, at 1:43 PM, Louis G. <louis at frentzgzesh.info> wrote: 
> 
> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) 

Which version of FreeBSD is this based on? 

> When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be. Both are running Version 2.7.3. Thank you in advance. 
> 
> FreeBSD output: 
> 
> device.mfr: CPS 
> device.type: ups 
> driver.name: usbhid-ups 
> driver.parameter.pollfreq: 30 
> driver.parameter.pollinterval: 2 
> driver.parameter.port: /dev/ugen4.2 
> driver.parameter.synchronous: no 
> driver.version: 2.7.3 
> driver.version.data: CyberPower HID 0.4 
> driver.version.internal: 0.39 
> ups.mfr: CPS 
> ups.productid: 0601 
> ups.status: OB 
> ups.vendorid: 0764 

Note also that the list of variables is much shorter than some of the other CyberPower HID devices: 

http://www.networkupstools.org/ddl/Cyber_Power_Systems/index.html 

Can you open up a root shell, kill the old `usbhid-ups` process, and run it from the command line? 

/usr/local/libexec/nut/usbhid-ups -a ups -DDD 

(Adjust the "-a ups" for the name that NAS4Free uses.) 

It will indefinitely, but we only need about the first 30 seconds. Please gzip the output before posting to the list. Also, please use reply-all, as this mailing list does not mangle the reply-to headers. 

-- 
Charles Lepple 
clepple at gmail 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150923/cd27a254/attachment-0001.html>