Roger, Thank you for the info. I will look into that and set that up ASAP.
Regarding the battery age, I’m not too it’d but I’m guessing approx 3-4 years. You think it’d be worth replacing, in light of this issue? Run time still seems Ok ~45 mins, but maybe the load when it switches over to battery may be too much? -- Todd Benivegna // t...@benivegna.com On Aug 2, 2020, 9:38 AM -0400, Roger Price <ro...@rogerprice.org>, wrote: > On Sat, 1 Aug 2020, Todd Benivegna wrote: > > > Also, this is what I found in the syslog on one of the machines: > > Jul 31 18:33:29 plex upsmon[970]: UPS ups@192.168.1.70 on battery > > Jul 31 18:33:34 plex upsmon[970]: UPS ups@192.168.1.70 on line power > > Jul 31 18:34:04 plex upsmon[970]: Executing automatic power-fail shutdown > > Jul 31 18:34:04 plex upsmon[970]: Auto logout and shutdown proceeding > > Jul 31 18:34:09 plex systemd[1]: nut-monitor.service: Succeeded. > > I suspect that getting to the bottom of this will need careful tracing of all > the status changes reported by the upsd instance running in the NAS. It would > be helpful if your upsmon.conf had NOTIFYMSG entries for all possible events, > with SYSLOG options set in the corresponding NOTIFYFLAG entries. > > upsmon.conf doesn't support reporting battery charge in the notification > messages, but you can specify multiple shell commands in the SHUTDOWNCMD > entry. > E.g. `upsc ups@192.168.1.70 battery.charge` and `upsc ups@192.168.1.70 > ups.status`. This will show what the situation was at that moment. > > The question that always gets asked: how old are the batteries? > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
