[Nut-upsuser] Need the date included in nuts -wall msgs.

2015-08-18 Thread Gene Heskett
Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the log, and in the -wall broadcast? We apparently have a substation regulator in the process of failing, and the recycle isn't normally

[Nut-upsuser] ups.load Smart-UPS 2200

2015-08-18 Thread Marcin Michta
OS Ubuntu 14.04.1 LTS, kernel 3.13.0-44-generic NUT 2.7.1, installed from repo. UPS APC Smart-UPS 2200 Hi all, It looks like my UPS correctly work with NUT, but I don't see ups.load in upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.runtime: 3960

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Charles Lepple
On Aug 17, 2015, at 11:56 AM, Johnny Wong e430ben...@yahoo.com wrote: What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M Okay, thanks. I think this is the first report of FreeBSD 10.2, so hopefully it is not an

Re: [Nut-upsuser] Need the date included in nuts -wall msgs.

2015-08-18 Thread Gene Heskett
On Tuesday 18 August 2015 09:50:32 Charles Lepple wrote: On Aug 18, 2015, at 3:27 AM, Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
Here are all the usbconfig outputs you have requested. I have left a message with the Dev for NAS4Free to give up the ./configure for NUT portion.  I am hoping they will... usbconfig -u 0 -a 5 dump_device_desc  datanas: ~# usbconfig -u 0 -a 5 dump_device_desc ugen0.5: TRIPP LITE UPS Tripp Lite

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
Just for grins, can you try adding usb_set_altinterface to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after [upstl1300]). Here is the output with the usb_set_altinterface added to ups.conf or at least partially output because it keeps going in a

[Nut-upsuser] Liebert IntelliSlot Unity Card IS-UNITY-DP snmp UPS-MIB.upsIdentManufacturer '1.3.6.1.2.1.33.1.1.1.0' problem

2015-08-18 Thread Dmitri Stepanov
OpenBSD 5.6 nut-2.7.2 (bin package) Liebert IntelliSlot Unity Card IS-UNITY-DP ups.conf: ..   mibs = ietf   snmp_version = v1 .. The problem is that the card responds to other snmp (v1,2c,3) requests normally but not to the 1.3.6.1.2.1.33.1.1.1.0 (UPS-MIB.upsIdentManufacturer). #

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
So when the UPS is communicating with the driver... it seems to work.  Problem is now that it keeps disconnecting.  Any recommendation on how to keep the drivers from disconnecting using the usb_set_altinterface?  (PS.  Is there a specific value to use?)  Or this confirms there is an issue with

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
You were right, there was 2 process running. What I did was kill both the usbhid-ups processes and reloaded the drivers again. Which still took about 10 tries before it would see the UPS. Once it was loaded, same thing. It would disconnect and connect Sent from Mail for Windows 10

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
Here are couple of things I tried. 1) Changed the USB cable. Same problem 2) I put an old CyberPower CP550SL w/USBSERIAL and it recognize it right away via the USB port I don’t know if that will give you any insight or eliminate certain things with the Tripp Lite SMART1300LCDT or not. Sent

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Charles Lepple
On Aug 18, 2015, at 9:07 PM, Johnny Wong e430ben...@yahoo.com wrote: Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and -D prevents that. I don't see

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread e430benz98
I see what you are saying. I did use usbhid-ups without the -D and once in a awhile it will say it found a previous driver running and it was going to kill it Here is something I have been doing... If I keep issueing the command to load the drivers eventually it will load it even after

Re: [Nut-upsuser] Need the date included in nuts -wall msgs.

2015-08-18 Thread Charles Lepple
On Aug 18, 2015, at 1:22 PM, Gene Heskett ghesk...@wdtv.com wrote: On Tuesday 18 August 2015 09:50:32 Charles Lepple wrote: On Aug 18, 2015, at 3:27 AM, Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Is it possible to set a logging option in one of the config files so that when we

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and -D prevents that. I don't see another usbhid-ups running ... unless its hidden I would have to

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
well, it is CLOSER to working with the usb_set_altinterface Also the port=auto in ups.conf doesn't pick it up.  I have to set port = /dev/ugen0.5 then the driver will pick it up. the upsd is able to start... BUT  the ups connects and disconnects on a regular basis of about 1min interval

Re: [Nut-upsuser] Need the date included in nuts -wall msgs.

2015-08-18 Thread Charles Lepple
On Aug 18, 2015, at 3:27 AM, Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the log, and in the -wall broadcast? Hey Gene, The syslog entry