This fixed everything! Everything appears to be working ok now and all clients are connected. Thank you!
Going to test everything out now. -- Todd Benivegna // t...@benivegna.com On Aug 12, 2020, 6:16 PM -0400, Charles Lepple <clep...@gmail.com>, wrote: > On Aug 12, 2020, at 5:32 PM, Todd Benivegna <t...@benivegna.com> wrote: > > > > > Those LISTEN lines were appropriate pre-systemd when NUT's startup script > > > was launched after networking was fully enabled. I would recommend > > > "LISTEN 0.0.0.0 3493" instead, and use firewall rules if you are trying > > > to exclude an interface (which is likely not the case on a Pi). > > > Ok, so replace both with that or just one of the lines? I suspected one of > > the lines may be the problem because when I took out the second line, > > nut-server service wouldn’t fail, but then clients couldn’t connect. > > Recommend replacing both. Binding to 0.0.0.0 will allow connections to/from > 127.0.0.1. The error handling is not ideal, but upsd logs messages as it > parses. You can stop the service (if systemd is still trying to restart it), > and then try "sudo upsd -D" to see what it is doing. It should respond to > Ctrl-C.
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
