TrueNAS NUT server monitoring

Hello everybody,

I have problem in TrueNAS (latest version incl.) that I don’t se any stats in Reporting / UPS.

I did setup UPS Service to observe state of UPS connected to my pfSense router. pfSense has configured NUT service to publish UPS state to other network clients. UPS identifier is ‘ups’ everywhere. ‘upsc ups@my.pfSense.router’ command in TrueNAS shell gives expected results that display lot of live stats from pfSense connected UPS.

Just reporting stats for UPS being monitored by TrueNAS display really, really nothing.

Was anyone able to fix this?

Thanks a lot for some info or direction what to look for. Have great day everyone,

Bye.

It’s not something I am using but if no one else has an answer here I would post over in the TrueNAS forums.

@manoli take a look at this, it may help.

1 Like

Oh man, it works!

Thanks so much!!!

The working fix is there since 2024, it’s sad that fix-up didn’t make it to upstream yet. ixSystem just don’t care they rather leave such bug more than 2 years untouched? :face_with_raised_eyebrow:

Hi Tom,

It’s solved, but would you might posting briefly how is your UPS monitoring setup done for TrueNAS? Do you have UPS directly connected to the TrueNAS server over USB?

Or maybe have a video about it? How to protect TrueNAS to be safe from sudden power loss?

Once again, thank you and have a great day everyone.

I don’t have anything setup for my TrueNAS regarding UPS. I did a video a few years back showing how it recovers from sudden power loss and while it’s probably something I should set up, it’s very low on my to do list.

Ok, my apologies, then I go and search for that video, cause I’m quite curious how TrueNAS can recover from such things. So basically you relay on robustness of ZFS, that it’s safe enough to survive power outage just fine.

Thank you, and have a good day.

I cover the technical reasons ZFS is so resilient in this video:

1 Like

NUT on TrueNAS works well once it’s configured but the client setup on secondary machines is where people usually get tripped up — making sure the upsmon.conf points to the right master IP and the credentials match exactly. Also worth setting a low enough battery charge threshold so TrueNAS actually gets a clean shutdown before the UPS cuts power rather than just logging the event.