Nut upsuser - Aug 2015 - Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

> 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 install the unhide package then....


/var/run/devd.pid
/var/run/syslog.pid
/var/run/mountd.pid
/var/run/istgt.pid
/var/run/upslog.pid
/var/run/upsmon.pid
/var/run/powerd.pid
/var/run/samba4/nmbd.pid
/var/run/samba4/smbd.pid
/var/run/samba4/winbindd.pid
/var/run/sshd.pid
/var/run/cron.pid
/var/run/rsyncd.pid
/var/run/lighttpd.pid
/var/run/spindown.pid
/var/run/upsd.pid
/var/run/usbhid-ups-upstl1300.pid

Sent from Mail for Windows 10



From: Charles Lepple
Sent: Tuesday, August 18, 2015 4:35 PM
To: Johnny Wong
Cc: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 3:28 PM, Johnny Wong <e430benz98 at yahoo.com>
wrote:
> 
> So when the UPS is communicating with the driver... it seems to work. 
Problem is now that it keeps disconnecting.
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.
>  Any recommendation on how to keep the drivers from disconnecting using the
usb_set_altinterface?  (PS.  Is there a specific value to use?)
>From the earlier usbconfig output, I only see "bAlternateSetting =
0x0000". Adding that option (as you did just now) defaults to a parameter
of zero. I will look into this.
FYI, some history is here: https://github.com/networkupstools/nut/issues/138

-- 
Charles Lepple
clepple at gmail







---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/5e12079e/attachment.html>

On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430benz98 at 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 another usbhid-ups running ... unless its
"hidden"....  I would have to install the unhide package then....
> 
What I mean is that you can't have more than one usbhid-ups process talking
to the same UPS at one time - regardless of whether they write a PID file. In
the case of running with "-D", you would need to double-check for any
in the background (and there was a PID file named usbhid-ups-upstl1300.pid).
"ps auxww|grep [u]sbhid-ups" should show only one driver in either
case.

Still looking into the altsetting issue. I would have to shuffle a few machines
around to get a copy of 10.2 running on a box that isn't being actively used
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple at gmail

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 removing the
usb_set_altinterface from ups.conf.

It almost looks like the inferface is dropping on and off regardless 

If that makes sense its almost like someone is pulling out the USB wire and
plugging in and out

Sent from my LG G3.

-----Original Message-----
From: Charles Lepple <clepple at gmail.com>
To: Johnny Wong <e430benz98 at yahoo.com>
Cc: "nut-upsuser at lists.alioth.debian.org" <nut-upsuser at
lists.alioth.debian.org>
Sent: Tue, 18 Aug 2015 6:37 PM
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430benz98 at 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 another usbhid-ups running ... unless its
"hidden"....  I would have to install the unhide package then....
> 
What I mean is that you can't have more than one usbhid-ups process talking
to the same UPS at one time - regardless of whether they write a PID file. In
the case of running with "-D", you would need to double-check for any
in the background (and there was a PID file named usbhid-ups-upstl1300.pid).
"ps auxww|grep [u]sbhid-ups" should show only one driver in either
case.

Still looking into the altsetting issue. I would have to shuffle a few machines
around to get a copy of 10.2 running on a box that isn't being actively used
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/3f730ad4/attachment-0001.html>

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



From: Charles Lepple
Sent: Tuesday, August 18, 2015 6:37 PM
To: Johnny Wong
Cc: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430benz98 at 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 another usbhid-ups running ... unless its
"hidden"....  I would have to install the unhide package then....
> 
What I mean is that you can't have more than one usbhid-ups process talking
to the same UPS at one time - regardless of whether they write a PID file. In
the case of running with "-D", you would need to double-check for any
in the background (and there was a PID file named usbhid-ups-upstl1300.pid).
"ps auxww|grep [u]sbhid-ups" should show only one driver in either
case.

Still looking into the altsetting issue. I would have to shuffle a few machines
around to get a copy of 10.2 running on a box that isn't being actively used
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple at gmail





-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/fc513a95/attachment.html>

Here are couple of things I tried.

1) Changed the USB cable.  Same problem
2) I put an old CyberPower CP550SL w/USB&SERIAL 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 from Mail for Windows 10



From: Charles Lepple
Sent: Tuesday, August 18, 2015 6:37 PM
To: Johnny Wong
Cc: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430benz98 at 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 another usbhid-ups running ... unless its
"hidden"....  I would have to install the unhide package then....
> 
What I mean is that you can't have more than one usbhid-ups process talking
to the same UPS at one time - regardless of whether they write a PID file. In
the case of running with "-D", you would need to double-check for any
in the background (and there was a PID file named usbhid-ups-upstl1300.pid).
"ps auxww|grep [u]sbhid-ups" should show only one driver in either
case.

Still looking into the altsetting issue. I would have to shuffle a few machines
around to get a copy of 10.2 running on a box that isn't being actively used
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple at gmail





-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/c4d2b5f9/attachment.html>