Rysz

Thanks for getting back to me, honestly I'm at a loss as to what the problem with your UPS could be. It really does seem like nothing is working as it should (even in their own software, judging by the screenshot). NUT is trying to bring up the driver as it should, but it fails to do so when your system boots for reasons beyond my understanding - especially when considering that the configuration itself doesn't change between the system boot and you manually starting NUT. A wild guess would be that the UPS takes a long time to get ready for a USB connection once noticing that there's something active on the other end of its USB connection. Meaning that the NUT driver startup at system boot might be happening at a stage where the UPS is not ready for a connection yet. But that would be the first time that I'm seeing something like this and I'm also wondering why this wasn't a problem for you before and has become one now... what's changed except for your batteries? Honestly after all this trouble and at this stage, if it were my UPS, I would scrap that UPS because I would not be able to trust it after the mess with the batteries not holding their load, voltages all over the place and now the software parts acting up as well - the software remains a big part of the equation after all. I mean a good UPS should be a device you can trust to protect your data and not burn down your house while at it, definitely something to not have to worry about every day. Used but good condition UPS can be found for cheap and even brand new UPS from reputable brands are not out of this world expensive. Personally I'd invest in a proper Eaton UPS, they have great support as far as NUT is concerned (having sponsored and contributed developing the NUT project for many years) and I personally use them with zero problems - the 5P series being my go-to UPS for almost all applications. I don't want this to be a sales pitch but something to consider from my experience. If you must keep using your current UPS, have you tried using it with APCUPSD (the in-built "UPS Settings")? If not, it might be worth a try - just make sure to stop the NUT services first. Maybe it'll be the solution to all your problems. 🙂

Genau, und ergänzend dazu betreibt man üblicherweise den NUT Host Server auf dem Gerät, welches als letztes in der Reihenfolge heruntergefahren werden soll. Damit eben die USV und deren Informationen allen anderen Geräten bis zum Schluss zur Verfügung steht und der Host Server die USV dann gänzlich abschalten kann (wenn so gewollt).

It's now integrated here apparently:

Can you please also post the diagnostics?

Thanks for the logs, those helped me narrow down the problem some more. It seems this is a general compatibility problem of your UPS with the UPS driver. The shutdown is caused by the UPS Driver thinking your UPS is on battery and then on critical low battery, resulting in an immediate shutdown, when in fact it is calibrating and possibly cycling through those states as part of that process. Mar 26 01:48:49 Mongo upsmon[17800]: UPS [email protected] on battery Mar 26 01:48:49 Mongo nut-notify: [ups] UPS is on battery. The system will shutdown when there is 240 runtime left on the UPS battery. Mar 26 01:48:54 Mongo upsmon[17800]: UPS [email protected] battery is low Mar 26 01:48:54 Mongo upsd[17797]: Client [email protected] set FSD on UPS [ups] Mar 26 01:48:54 Mongo nut-notify: [ups] UPS [email protected] battery is low Mar 26 01:49:00 Mongo upsmon[17800]: Executing automatic power-fail shutdown Mar 26 01:49:00 Mongo upsmon[17800]: Auto logout and shutdown proceeding Mar 26 01:49:05 Mongo shutdown[15423]: shutting down for system halt As a workaround we can attempt the following, hopefully it'll solve the problem with the shutdowns. Put these two lines in your UPS.CONF file using the GUI configuration editor. Make sure to put them on line 10 and 11 so they are not overwritten by the GUI: ignorelb onlinedischarge_calibration Then "Restart NUT" to make sure that the changes are applied. Check your UPS.CONF file to confirm the lines are still there after you restarted NUT. The first line is to tell the UPS driver to ignore the low battery state and instead determine if the battery is low from the reported battery charge and runtime only, this should prevent the immediate shutdown when the battery calibration is cycling through the low battery state and the driver thinks the UPS is on low battery when it's actually calibrating. The second line tells the UPS driver to treat OL+DISCHRG as CAL and will hopefully stop the massive log spamming that is going on because your UPS seems to be in OL+DISCHRG state almost permanently (or the UPS driver seems to think so at least). This will probably result in your UPS showing as calibrating instead of being online in the dashboards most of the time, but I think it's a small price to pay for the reduced log volume. Please let me know if that worked for you!

Do you have the log from before the shutdown? We need to figure out what your UPS was doing before the server decided to shutdown. Also, please post your diagnostics.

I have just pushed an update which allows for hyphens in the UPS name (among other changes).

It's not possible to just add a MIB, they have to be coded into the UPS driver in the backend. You can open an issue here attaching your new MIB: https://github.com/networkupstools/nut/issues What is the problem with the older MIB, what information are you missing on your 9PX or doesn't work at all?

Hello, there seems to be some legacy code that's forcing the name to be alphanumeric. I'll have to check if there's a reason for that (possibly breaking something) or if we can allow it.

Sure, no problem, during battery testing the battery is usually discharged a bit for testing purposes and then charged again. That's the reason why you see OL (on line power) and DISCHRG (battery discharging) during your UPS battery testing process. Some UPS have a separate state CAL (battery calibration) for this, but many just report OL DISCHRG, OFF or OB or all of those during the testing process.

You don't need to set this flag unless the log message is bothering you. That status itself is not a problem anymore because the OFF-state related bug (which some APC models experienced) has been fixed so that previously affected UPS do not falsely shutdown (when actually doing calibration) anymore. If the log message bothers you, then you can put this flag in the ups.conf so that it reports CAL instead of OL DISCHRG. But honestly if everything works I would not bother because it's just a log message and doesn't cause any problem on its own.

Nothing. NUT will by default show all the variables it can read from the UPS, but there's nothing more that can be done to increase the amount of those variables if the UPS driver does not support reading more. I'd just remove the custom voltage settings if they are not needed anymore and I think you're good. 🙂

After compiling the package and running some further tests, it's unfortunately not possible to integrate the older backend. The netatalk v2 backend, and in particular the AppleTalk protocol which your OS might theoretically require to communicate, both depend on a legacy kernel module that's not or no longer present in Unraid. Sorry I couldn't be of more help there. 😞 But it does list Mac OS 7.5. as compatible for the newer v3 backend as well, so perhaps just not the automatic service (server) discovery. Is there any option you can connect directly via IP in the "Chooser"? Also check out this guide for your OS version: https://forum.vcfed.org/index.php?threads/accessing-os-x-shares-from-system-7-5-3.5886/ which seems to include the necessary client software for the newer v3 protocol to connect over IP. https://www.macintoshrepository.org/44248-open-transport-1-1-2 Please let me know if that worked for you!

Configuration looks good, I read up a bit on this just now and it looks like there's two versions of the netatalk backend v2 and v3 which offer different compatibility with older OSes. We're currently using the newer v3 which your OS might be too old for. I'll code in a backend switch setting so you can switch between v2 and v3 backends within the plugin in the future, so hopefully that'll work for your OS as well then. I hope to have the update ready this weekend.

Can you post a screenshot of your configuration?

Weird, it should show an error that it's not compatible in the installation window:

Thanks for the feedback everyone - glad everything seems to be running as it should. 🙂

Yeah that seems like a multifaceted problem there, perhaps your UPS battery is degraded and couldn't even hold the battery load long enough for NUT to kick in and even begin with the shutdown. From experience 2 minutes can be a very long time depending on your power draw and if your UPS battery is not able to sustain it you'll have a shutdown. That might also be the root problem with the battery voltages inside NUT, so perhaps a new battery would be worth trying and it'll also resolve your voltage situation for those voltage directives to no longer be required. Just an idea... 🙂

The configuration looks good to me. One last thing to try would be enabling "Enable USB Power Management Override" to see if that helps the situation and is related to power management on a software level. Did you make any significant changes to the UPS (battery/settings), the physical connection (different USB cable/port) or NUT (changed backend/updated from much older version) recently that could correlate with this issue? If it worked well before then it looks to me like maybe that USB port is dying, hopefully not the USB interface on the UPS itself. Beware if you reconnect to another USB port you should do "Reset Config" and "Auto Config" again because the "Auto Config" fixes it on a specific USB port. Usually is one of these reason if things worked well before and start dropping out (more likely to less likely): NUT settings recently changed around UPS settings recently changed around UPS firmware or NUT backend recently updated USB cable between Unraid machine and UPS faulty or dead USB port on Unraid machine faulty or dead USB port on UPS faulty or dead USB controller on UPS faulty or dead USB controller on Unraid machine faulty or dead Unraid version recently updated & now HW compatibility/driver issue

Sure, no problem, still can you post the NUT Debug Package? Just want to make sure your configuration is good too because that shouldn't have happened even if you didn't see the settings anymore. Did you have to do a parity check when you started the server again or how are you not sure that it didn't shutdown the system as it should have?

No it's not been removed, it's only visible in "Enable Manual Configuration Mode": "No" or "for UPS Driver" because those settings are misleading in manual configuration mode "Yes" as they won't function if you're using a different notification script directive in upsmon.conf (which some people do). If your UPS requires specific configuration lines to work with NUT (as I remember yours does) you'll have to set "Enable Manual Configuration Mode:" to "for UPS Driver" - it'll then respect your manual configuration for the UPS driver but let you configure the shutdowns and other settings at the same time. Regardless if you didn't make any changes in upsmon.conf (especially to the line: NOTIFYCMD "/usr/sbin/nut-notify") it should've shut down as before even if the settings weren't directly visible anymore. In fact I just tested it from my server with your exact same configuration and it shut down after 2 minutes just fine. Do you perhaps have logs from before the shutdown and are you sure NUT registered that your UPS is on battery correctly? Did you get any notifications that the UPS is on battery? Please post the NUT Debug Package (can be found in NUT Settings).

I've been using Seagate forever but going to switch to Toshibas going forward.

I've figured out a way to implement the feature without interacting with the Docker containers and VMs themselves. I've just pushed an update with the new setting (disabled by default), so please let me know if it works for you... 🙂

Can you please post the NUT Debug Package (can be found in NUT Settings) ?