I now have large chunks of the new driver working in the foreground and wanted to see what upsc reports after starting the driver "normally".
I started checking with upsdrvctl:
bille@NUT-VM:/usr/local/ups/sbin$ ./upsdrvctl -l
Network UPS Tools upsdrvctl - UPS driver controller 2.8.2.1082.1-1083-gba804633b (development iteration after 2.8.2)
UPM
OK, good so far...it lists the single ups in ups.conf.
Go for start:
bille@NUT-VM:/usr/local/ups/sbin$ sudo ./upsdrvctl start
Network UPS Tools upsdrvctl - UPS driver controller 2.8.2.1082.1-1083-gba804633b (development iteration after 2.8.2)
Network UPS Tools 2.8.2.1082.1-1083-gba804633b (development iteration after 2.8.2) - newdriver UPS driver 0.01
Warning: This is an experimental driver.
Some features may not function correctly.
Found a UPS with serial number 2340001
WARNING: ./upsdrvctl was called directly on a system with systemd support.
Please consider using 'upsdrvsvcctl' instead, to avoid conflicts with
nut-driver service instances prepared by 'nut-driver-enumerator'!
OK, I think that looks correct (ignoring 'upsdrvsvcctl' for now). Try 'upsc':
bille@NUT-VM:/usr/local/ups/bin$ ./upsc UPM
Error: Connection failure: Connection refused
I also tried 'sudo ./upsc UPM' and got the same result. Is there enough information here for you to help me identify what part of the NUT system is not yet configured properly?
Thank you,
Bill
[not a linux guy]
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
