[Nut-upsuser] Tripplite Smart1000LCD problem with revision > r1071
Martin Thomas
cythraul at elitemag.org
Tue Mar 4 13:40:54 UTC 2008
Hi Arjen,
Thanks for the quick reply.
On Mon, Mar 3, 2008 at 2:54 PM, Arjen de Korte <nut+users at de-korte.org> wrote:
> cythrault at gmail.com wrote:
>
> > With recent revision, it's impossible to get upsdrvctl started:
> >
> > [root at teevee nut]# /usr/local/bin/upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.3.0-1352
> > Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352)
> >
> > Warning: This is an experimental driver.
> > Some features may not function correctly.
> >
> > Using subdriver: TrippLite HID 0.2 (experimental)
> > HIDGetDataValue: Value too large for defined data type
>
> I don't see a message that it failed to start.
>
> > This began with r1072...
>
> Quite possible. Before then, this error condition wasn't handled. But I
> don't see why it should prevent the driver from starting and as far as I
> can see, the driver started properly.
Let me correct my statement and expand; my previous report was incomplete.
The drivers starts but is not connecting.
Upon exiting upsdrvctl with the output I already copied, upsd is not
able to connect to the device:
[root at teevee etc]# /usr/local/sbin/upsd -DDD
Network UPS Tools upsd 2.3.0-1353
listen_add: added 127.0.0.1:3493
listen_add: added 192.168.0.244:3493
listening on 127.0.0.1 port 3493
listening on 192.168.0.244 port 3493
Can't connect to UPS [smart1000lcd] (usbhid-ups-smart1000lcd): No such
file or directory
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
Connection from 192.168.0.99
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
write: [destfd=6] [len=27] [ERR FEATURE-NOT-CONFIGURED]
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
write: [destfd=6] [len=3] [OK]
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
write: [destfd=6] [len=3] [OK]
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
Client nutmon at 192.168.0.99 logged into UPS [smart1000lcd]
write: [destfd=6] [len=3] [OK]
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
write: [destfd=6] [len=25] [ERR DRIVER-NOT-CONNECTED]
sstate_dead: connection to driver socket for UPS [smart1000lcd] lost
> > I wanted to include a debug output but it does not seems to end:
>
> That's what it is supposed to do, it will run in the foreground until
> you stop it.
Ahhh! Thanks for the precision.
> > [root at teevee ~]# /usr/local/bin/usbhid-ups -D -a smart1000lcd
> > Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352)
> >
> > Warning: This is an experimental driver.
> > Some features may not function correctly.
>
> [...]
Indeed, I know it's experimental, I can go back to a stable tree. I'm
not complaining here, I just want to add my user experience. ;)
Sincerely,
Martin
More information about the Nut-upsuser
mailing list