this post was submitted on 23 Jun 2023
7 points (100.0% liked)

homelab

6656 readers
23 users here now

founded 4 years ago
MODERATORS
[email protected]
7
Problems with NUT (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
4 comments fedilink hide all child comments
 

I recently replaced my UPS and set up NUT (Network UPS Tools) for monitoring.

Everything works fine for a short time, but after a few hours, NUT reports "error: Data stale" in the web UI. After a few more hours, the web UI just stops responding completely.

I have NUT running on a Ubuntu VM in Proxmox. My UPS is a Tripp Lite (Eaton) SU1000RTXL2UA. It's connected to my hypervisor via USB and passed through to the VM. Restarting the container fixes the problem. Any idea what could be causing this?

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago (1 children)

I'm browsing "all" and have no idea what this community is about.

Sorry you're having trouble with your NUT

[–] [email protected] 2 points 1 year ago

This is a community for individuals who are interested in running their own IT infrastructure at home. Personally, I have a server rack (like you might see in a datacenter) with a few servers installed in it. I use it for streaming video and audio to my TVs and portable devices, bulk storage, load-sharing two internet connections, monitoring security cameras, writing code, and a whole lot of other things.

"NUT" stands for "Network UPS Tools" and is a program that connects to an UPS (battery backup) and provides monitoring and remote shutdown based on power status. Unfortunately, as you say, I am having problems with my NUT at the moment.

[–] sedawk 3 points 1 year ago

Any sort of messages in syslog or dmesg?

[–] [email protected] 1 points 1 year ago

When it gets in the problem state, does the UPS respond when you use upsc to check its status in a terminal in the vm?

If so it might be taking too long to respond when it is being checked by the daemon. If so setting MAXAGE to something higher than the 15s default may help. A lot of people raise it to 25 for this symptom. But this will only help if the driver is still connecting to the UPS ok. If it's not then it may be a problem with the USB connection or the UPS.