Also note that, if needed, you can have greater control over the driver's arguments via command line by starting its program directly (as opposed to editing `ups.conf` and restarting via `upsdrvctl`).
This can help with bumps of debug verbosity (more on that in github wiki) or testing any custom `addvar()` options. And you can usually run it just after `make` from the build area (maybe with `sudo` or other tricks for local device access) without `make install`. But YMMV what is easier to arrange - especially allegedly being "not a linux guy" ;) Jim On Sat, Oct 26, 2024, 12:46 Jim Klimov <[email protected]> wrote: > Sounds great! > > By `connection error` it looks like the `upsc` client had nowhere to go. > Is `upsd` started (and does it `LISTEN` on locahost or asterisk per > `upsd.conf`)? > > Jim > > On Sat, Oct 26, 2024, 08:13 William R. Elliot <[email protected]> wrote: > >> Hello again. >> >> 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] >> >> >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> Virus-free.www.avg.com >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> <#m_7956678047209404877_m_6151391202365757037_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> _______________________________________________ >> Nut-upsdev mailing list >> [email protected] >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev >> >
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
