@rpvelloso on Github suggested some changes (driver version v0.64) that should
help with the initial sync:
https://github.com/networkupstools/nut/commit/debc8e0280ea4de9a0db5ca34aa66705b285f61f
It's the solis_debug branch on Github.
Does that help? I'm concerned that it might get out of sync la
On Sep 2, 2015, at 5:54 PM, John Thurston wrote:
>
> But what about that "Bypass Paralleling Switchboard"? I suspect it is
> possible that it could be used to ignore the input from UPS-A and rely only
> on UPS-B to handle the load. If I'm only monitoring the status of the UPSs,
> how will I kn
On Sep 8, 2015, at 4:48 PM, Rob Groner wrote:
>
> 0.005927Device matches
> 0.005940failed to claim USB device: Device or resource busy
> 0.005954failed to detach kernel driver from USB device: No such file or
> directory
Rob,
this is a bit of a tough one to track down.
The "
On Tue, 8 Sep 2015, Rob Groner wrote:
Roger,
rtd@linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD
Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
USB communication driver 0.32
0.00 debug level is '3'
0.000405 upsdrv_initups...
...
0.004555 Ch
Roger,
rtd@linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD
Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
USB communication driver 0.32
0.00 debug level is '3'
0.000405 upsdrv_initups...
0.004386 Checking device (0930/6545) (002/002)
0.004431
On Tue, 8 Sep 2015, Rob Groner wrote:
I executed lsusb to verify the USB device is there, and it is. I tried
the shutdown command again with debug enabled, but it didn't seem to
reveal much more:
---
r
Roger,
Ok, I simplified it somewhat. I start all of the NUT services on the command
line after boot, to verify they are all starting correctly. They appear to be.
Doing this, I found the systemd service unit to somewhat reliably execute the
shutdown. I only tried 5 times, but it worked each
7 matches
Mail list logo