Sam Varshavchik <[email protected]> writes: >> It's really odd to lose power for 40 seconds in my experience. I wonder >> roughly where you are (looks like NA due to 120V, state?) and if you >> understand the mechanism for how it came back so fast. > > Yes, New Jersey. I'm fairly certain that it was local maintenance. The > power grid here is pretty robust and redundant. This was early > Saturday morning, I'm pretty sure it's weekend maintenance, they cut > off a portion of a grid, and then quickly cut it in somewhere else.
That makes sense. I'm in Massachusetts and often experience 2-5s from reclosers and then 40-60m from branch or squirrel not handled from recloser, when not a lot is happening. >> I would look in the logs and see if you can find that nut logged >> something about "low battery" or "forced shutdown". > > Well, that's what I'm asking. Where do I find these logs. I poked > around with journalctl, and found just startup and shutdown messages. I would look in /var/log/messages, but I use BSD :-) Seriously that sounds like a systemd/ubuntu problem more than a nut problem. > I dunno, that's what I'm asking. I don't see anything useful logged > anywhere I looked. I found three things in systemctl, nut-monitor, Does ubuntu really not have files in /var/log? > nut-server, and a "nut-driver@nutdev1", and journalctl didn't show > anything useful for these. Oh, they had something, but it was just the > stock startup messages. Nothing was actually logged, for power events. that is odd >> > driver.state: quiet >> > driver.version: 2.8.1 >> >> That's old. Update to the latest release. I know you're using Ubuntu >> and they are behind. Update anyway. > > I'm almost there, as far as motivation goes, to do that. Off-topic: I > have the same Ubuntu/Debian general complaint: for the longest time > Debian packaged ancient versions of my packages. Like decades > ancient. I should say now that a volunteer has stepped out and is > making progress; but I eventually solved that problem by figuring out > how to package my tarballs so that they can be cookie-cuttered into > installable .deb-s, similar to how rpm-aware tarballs can be compiled > into binary packages without even extracting them. I know it's a pain. I use pkgsrc, and when something I want is old I update it in pkgsrc.... I suggest doing the 15s power failure experiment with the upsc shell script loop. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
