On Mar 6, 2020, at 2:02 PM, Paul Newbery <[email protected]> wrote: > > I have since been trying to get them working with the NUT software, which I > can do, but I simply cannot get them to start at system start up. It can be > seen from the "Syslog Nut Extract" that upsdrvctl successfully loads the > driver, but nut-server fails to start and the driver then stops as it is no > longer required. However, upsmon continues to load successfully and proceeds > to fill up the syslog with error messages. > Mar 6 14:05:02 paul-desktop upsd[947]: fopen /var/run/nut/upsd.pid: No such file or directory Mar 6 14:05:02 paul-desktop upsd[947]: /etc/nut/upsd.conf is world readable Mar 6 14:05:02 paul-desktop upsd[947]: /etc/nut/upsd.conf is world readable Mar 6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493 Mar 6 14:05:02 paul-desktop upsd[947]: listening on ::1 port 3493 Mar 6 14:05:02 paul-desktop upsd[947]: listening on 127.0.0.1 port 3493 Mar 6 14:05:02 paul-desktop upsd[947]: no listening interface available Mar 6 14:05:02 paul-desktop upsd[947]: not listening on 192.168.1.64 port 3493
^ At this point, the 192.168.1.64 network interface may not be up. Are you intending to allow NUT to only listen on localhost and one specific network interface? Or is there only one physical network interface total? If the latter, I recommend "LISTEN 0.0.0.0" to listen on all local addresses. If the former, I would use a firewall that does filtering well before the packets touch NUT code, and that can also block packets destined to other interfaces until the one allowed interface is up. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
